KR20190078787A - Message processing apparatus and method - Google Patents

Abstract

Provided are a message processing apparatus and method. According to an embodiment of the present invention, the message processing apparatus comprises: a plurality of device management modules; and a service management module for determining at least one device management module, that the service management module is in charge of, among the plurality of device management modules, selecting one transmission standby message based on a message generation time and a set time to live (TTL) when there are a plurality of transmission standby messages to be transmitted to the assigned device management module, and transmitting the selected transmission standby message to the assigned device management module.

Description

[0001] MESSAGE PROCESSING APPARATUS AND METHOD [0002]

Embodiments of the present invention relate to a message processing apparatus and method, and particularly to a retransmission and a duplicate transmission processing technique of a message.

Recently, with the generalization of mobile terminals and the development of information communication technology, there is an increasing demand for a message processing system that provides various message services. Such a message processing system can be applied to various fields such as a security service, an e-mail service, and a payment service. In the message processing system, the transmitting side and the receiving side send and receive various messages related to a service provided by the message processing system, and frequently transmit the message in order to secure the reliability of the service.

However, when the size of the service is increased and the number of instances of the transmitting / receiving side increases, the number of messages to be retransmitted also increases, and messages are repeatedly transmitted between the transmitting side and the receiving side due to message retransmission. Particularly, when there are a plurality of transmission wait messages to be retransmitted to the receiving-side instance in the past, when the receiving-side instance can not normally receive the message (for example, when the receiving-side instance is off, There is a problem in that all the messages are retransmitted and unnecessary resources are wasted.

Korean Patent Publication No. 10-2017-0087116 (July 27, 2017)

Embodiments of the present invention are intended to efficiently perform message retransmission and redundancy processing to minimize system load.

According to an exemplary embodiment, a plurality of device management modules; And a plurality of device management modules that are responsible for the plurality of device management modules, and when there is a plurality of transmission wait messages to be transmitted to the responsible device management module, And a service management module for selecting one transmission standby message based on a time to live (TTL) and transmitting the selected transmission standby message to the corresponding device management module.

The service management module may select one of the plurality of transmission wait messages, which is the oldest generation wait time message, without the current validity period being exceeded.

The service management module may determine that the device management module is normally connected to the message server when receiving the acknowledgment message for the transmission standby message from the device management module.

Wherein the service management module is configured to transmit the transmission standby message that has not expired at the present time among the remaining transmission standby messages except for the transmission standby message selected when the reception confirmation message or the connection confirmation message of the responsible device management module is received To the responsible device management module.

The service management module may sequentially transmit each of a predetermined number of the transmission wait messages, which are not yet valid, of the remaining transmission wait messages, or may transmit the transmission standby messages by grouping the transmission wait messages in units of a predetermined size.

If the service management module includes a plurality of threads for transmitting and receiving a message, the thread transmitting each of the transmission wait messages activates a setting of a database indicating whether the transmission wait message is transmitted, When receiving the acknowledgment message for at least a part of the transmission standby message or the connection confirmation message of the responsible device management module, the other thread, excluding the transmission standby message, confirms that each of the transmission standby messages is currently being transmitted It is possible to prevent each of the transmission wait messages from being duplicated.

Wherein the service management module determines whether the received message is already processed by using the ID of the received message when receiving the received message from the device management module, It can be determined whether or not a previous message ID exists in the received message.

The service management module determines whether the previous message of the received message has been processed by referring to the database if the previous message ID is found in the received message, It may transmit a check message for checking the state of the previous message to the device management module.

According to another exemplary embodiment, there is provided a message processing method performed by a service management module connected to a plurality of device management modules through a network, the method comprising: Determining a module; If there is a plurality of transmission wait messages to be transmitted to the responsible device management module, the processing unit selects one transmission wait message based on the generation time of the transmission wait message and the set time-to-live (TTL) step; And transmitting, at the processing unit, the selected transmission wait message to the responsible device management module.

The selecting of the one transmission standby message may select one of the plurality of transmission standby messages, the oldest one of which is the oldest generation time without exceeding the current validity period.

Wherein the message processing method further comprises the step of, when the processing unit receives from the device management module a reception acknowledgment message for the transmission standby message, transmitting the selected transmission standby message to the responsible device management module, And determining that the message server is normally connected to the message server.

The message processing method may further include the step of, after the step of transmitting the selected transmission wait message to the responsible device management module, if the reception confirmation message or the connection confirmation message of the corresponding charged device management module is received, And transmitting a transmission wait message, which is not yet valid, to the responsible device management module among the remaining transmission wait messages except for the message.

Wherein the step of transmitting each of the transmission standby messages to the corresponding device management module comprises the steps of sequentially transmitting each of the remaining transmission standby messages and a predetermined number of transmission standby messages not exceeding the valid period, Size can be bundled and transmitted.

Wherein when the service management module includes a plurality of threads for transmitting and receiving a message, transmitting each of the transmission wait messages to the corresponding device management module comprises: Activating a setting of a database indicating whether a standby message is transmitted; And a thread other than the thread receives the acknowledgment message for at least a part of the transmission wait message or the connection acknowledgment message for the responsible device management module, Thereby preventing the transmission wait messages from being repeatedly transmitted.

The message processing method may further include the steps of: determining whether the received message is already processed using the ID of the received message when the processing unit receives the received message from the device management module; And determining whether a previous message ID exists in the received message when the processing unit determines that the received message is not a processed message.

The message processing method may further include a step of determining whether or not the previous message ID exists in the received message, if the processing unit determines that the previous message ID exists in the received message, Determining whether processing of a previous message of the message has been completed; And transmitting the check message for checking the status of the previous message to the device management module when the processing unit determines that the process of the previous message of the received message is not completed.

According to another exemplary embodiment, a service management module connected to a plurality of device management modules via a network, the determining module determining one or more responsible device management modules of the plurality of device management modules, And selecting one transmission wait message based on a generation time of the transmission wait message and a set time-to-live (TTL) when a plurality of transmission wait messages to be transmitted to the corresponding device management module exist, And a processing unit for transmitting the selected transmission wait message to the responsible device management module.

According to embodiments of the present invention, when there are a plurality of transmission standby messages scheduled to be retransmitted (that is, pending), not all of the transmission standby messages are transmitted, but one transmission standby message The transmission standby message may be selected and the selected transmission standby message may be transmitted first so that connectivity of the receiving module may be checked with less load. In addition, according to the embodiments of the present invention, it is possible to more efficiently perform the repetitive processing of the received message and the sequential processing according to the previous message ID in cooperation with the database.

1 is a block diagram showing a detailed configuration of a message processing apparatus according to an embodiment of the present invention;
2 illustrates an example of a service management module and an application server according to an embodiment of the present invention.
3 illustrates an example of a device management module and a device according to an embodiment of the present invention.
4 is a block diagram illustrating a detailed configuration of a service management module according to an embodiment of the present invention.
5 is a diagram illustrating an example of a message generated in a generation unit according to an embodiment of the present invention
6 is a flowchart illustrating a process of determining a device management module in charge in a determination unit according to an exemplary embodiment of the present invention.
FIG. 7 is a flowchart illustrating a process of processing a transmission wait message according to an embodiment of the present invention.
8 is a flowchart for explaining a processing procedure of a transmission wait message according to an embodiment of the present invention.
9 is a flowchart for explaining a processing procedure of a received message performed by the service management module according to an embodiment of the present invention.
10 is a flowchart illustrating a process of processing a received message performed in the device management module according to an embodiment of the present invention.
11 is a block diagram illustrating and illustrating a computing environment including a computing device suitable for use in the exemplary embodiments.

Hereinafter, specific embodiments of the present invention will be described with reference to the drawings. The following detailed description is provided to provide a comprehensive understanding of the methods, apparatus, and / or systems described herein. However, this is merely an example and the present invention is not limited thereto.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail. The following terms are defined in consideration of the functions of the present invention, and may be changed according to the intention or custom of the user, the operator, and the like. Therefore, the definition should be based on the contents throughout this specification. The terms used in the detailed description are intended only to describe embodiments of the invention and should in no way be limiting. Unless specifically stated otherwise, the singular form of a term includes plural forms of meaning. In this description, the expressions "comprising" or "comprising" are intended to indicate certain features, numbers, steps, operations, elements, parts or combinations thereof, Should not be construed to preclude the presence or possibility of other features, numbers, steps, operations, elements, portions or combinations thereof.

1 is a block diagram showing a detailed configuration of a message processing apparatus 100 according to an embodiment of the present invention. 1, the message processing apparatus 100 according to an exemplary embodiment of the present invention includes a service management module 102, a device management module 104, a message server 106, and a third party message server 108. [ . The message processing apparatus 100 is a system for processing message transmission / reception between a plurality of device management modules 104 and a plurality of service management modules 102. Hereinafter, the service management module 102 generates a message And transmits the message to the device management module 104 and receives an acknowledgment message for the message from the device management module 104. [ However, the present invention is not limited thereto, and the device management module 104 may generate a message, transmit the message to the service management module 102, and receive an acknowledgment message for the message from the service management module 102. The service management module 102 and the device management module 104 may be referred to as a message processing module, one of which is referred to as a first message processing module, and the other of which is referred to as a second message processing module. Hereinafter, the detailed configuration of the message processing apparatus 100 will be described in detail.

The service management module 102 is an application server (not shown) side component, and transmits and receives various messages related to the application service between the application server and the message server 106. In embodiments of the present invention, the application server is a server for providing application services to a device (not shown). The application service may be, for example, a security related service such as a camera control of a device, a microphone control, a recording function control, or the like, but this is merely an example, and the application service is not particularly limited. In addition, the message may be, for example, a control message for executing the above-described application service in the device, an acknowledgment message for the control message (i.e., an ACK message), and the like.

The service management module 102 may provide reliability to the application server by sending and receiving messages between the application server and the message server 106. [ Specifically, the service management module 102 generates a message related to the application service according to the message generation request of the application server, stores the message in a database (not shown), and transmits the message to the device management module 104 ). At this time, the message creation request may include recipient information of the message (for example, identification information of the device management module 104), identification information of an application service related to the message, and the like. The service management module 102 may generate a message ID according to the message creation request, and may generate a message corresponding to the message ID. Here, the message includes at least one of a message ID, a source address, a destination address, via information, an ID of a previously transmitted message (hereinafter, referred to as a "previous message ID" (TTL: Time To Live), a creation time, identification information of an application service, and the like. In addition, the service management module 102 may receive a request for generating a message having a transmission sequence from an application server, and may sequentially transmit a message (hereinafter referred to as an "Quot;) can be generated.

The service management module 102 may check the ID of the previous message of the message (i.e., the previous message ID) by referring to the database in response to the request for generating the order guarantee message, and may generate the message ID of the message. Then, the service management module 102 may generate a message including the message ID and the previous message ID.

Here, the previous message means a message to be processed (e.g., transmitted or received) immediately before the message. The service management module 102 may determine the last recorded message ID among the message IDs recorded in the database each time the message is generated. At this time, the message ID can be recorded (or stored) in the database by being distinguished for each device and each application (or each application client). The service management module 102 may store the previous message ID in a header of the message. If the previous message does not exist, the service management module 102 may store its own message ID in the header of the message.

For example, when the service management module 102 wants to transmit a message relating to the A application to the b device, the service management module 102 refers to the database and determines that the last recorded message ID, -1 ". Accordingly, the service management module 102 can generate its own message ID " A-b-2 ", and transmit a message including the message ID and the previous message ID to the b-device. The device management module 104 of the device b may then determine whether the processing of the previous message of the message is completed using the previous message ID included in the received message. If it is determined that the process of the previous message of the received message is not completed, the device management module 104 may transmit a check message for checking the status of the previous message to the service management module 102. In the above example, when a message having the message ID "Ab-2" is transmitted to the b-device, the device management module 104 confirms the previous message ID "Ab-1" included in the message, It is possible to determine whether or not the processing for the previous message corresponding to the message has been completed. If it is determined that the process of the previous message has not been completed yet, the device management module 104 may transmit a check message for checking the status of the previous message to the service management module 102. The check message may include, for example, an ID of the previous message, a status check and retransmission request of the previous message, a status check of an application related to the previous message, identification information of a device transmitting the check message, . The service management module 102 may receive the check message from the device management module 104 and may transmit a response to the check message to the device management module 104.

In addition, the service management module 102 may retransmit or delete the message according to whether it receives an acknowledgment message (i.e., an ACK message) for the message from the device management module 104 within a predetermined time. As an example, the service management module 102 may resend the message if it does not receive an acknowledgment message for the message within the set time. As another example, the service management module 102 may delete the message stored in the database when receiving the acknowledgment message for the message within the set time. Hereinafter, a message to be retransmitted (i.e., pending) is referred to as a " transmission standby message "

A plurality of service management modules 102 may exist for load balancing and each service management module 102 may have a different ID (i.e., an instance ID) . In addition, the service management module 102, which processes the same application service, belongs to the same group and can have the same group ID. In addition, the service management module 102 and the application server may be located in the first network. In the present embodiments, the first network may be, for example, an intranet of a particular organization or enterprise.

The service management module 102 determines one or more responsible charge management modules of the plurality of device management modules 104 by using the ID of each of the device management modules 104 and the total number of the service management modules 102 , And can only retransmit the transmission wait message to its responsible device management module. At this time, the service management module 102 performs a modulus operation on the hash values of the IDs of the device management modules 104 to the total number of the service management modules 102, and performs a modular operation And determine the responsible device management module by referring to the modular operation value and its own identification number.

As an example, assuming that there are three service management modules 102, the service management module # 0 processes the transfer wait messages for the device management modules 3, 6 and 9, and the service management module # And the service management module # 2 may process the transfer wait message for the device management modules 2, 5, At this time, when there are a plurality of transmission standby messages for each chargeable device management module managed by the service management module 102, the service management module 102 transmits the plurality of transmission standby messages to the corresponding chargeable device management module do. However, when the responsible device management module can not normally receive the transmission wait message (for example, the terminal in which the device management module or the device management module is installed is in an off state or their network connection is not normally established) Unnecessary resources may be wasted if a plurality of transmission wait messages for the responsible device management module are all transmitted. In this case, even if the responsible device management module switches to a state in which the transmission standby message can be normally received, the reception acknowledgment of the already transmitted transmission standby message is not performed in time, have. Accordingly, in the present embodiment, when there are a plurality of transmission wait messages to be transmitted to the device management module 104 in order to solve such a problem, the service management module 102 determines the generation time and the validity period of the transmission wait message Only one transmission standby message is selected and the selected transmission standby message is transmitted to the device management module 104 first.

As an example, when there are 100 transmission waiting messages to be transmitted to the device management module 3, the service management module # 0 transmits the transmission outstanding messages to the device management module 3 based on the generation time of the transmission outstanding messages and the valid period of the transmission outstanding messages A single message waiting to be transmitted can be selected. Specifically, the service management module 102 may select one of the transmission wait messages, which is the oldest generation time without exceeding the current valid period. In the above example, the service management module # 0 selects the transmission wait message # 3 having the oldest generation time without exceeding the current validity period (for example, until 2017.05.10) among the 100 transmission wait messages, Only the waiting message # 3 can be transmitted (i.e., retransmitted) to the device management module 3. The reason why the transmission standby message having the oldest generation time is transmitted first is to match the transmission sequence, that is, the sequence number of the transmission standby message, when the remaining transmission standby messages are transmitted in the future.

If the service management module 102 receives an acknowledgment message from the device management module 104 (or receives a connection confirmation message from the message management server 104) from the message server 106, The service management module 102 may determine that the device management module 104 is normally connected to the message server 106 (that is, the remaining transmission wait message is also ready to be received).

That is, according to the embodiments of the present invention, when there are a plurality of transmission standby messages scheduled to be retransmitted (that is, pending), not all of the transmission standby messages are transmitted, It is possible to check the connectivity of the device management module 104 with less load by transmitting only the transmission standby message selected by selecting one transmission standby message.

In addition, when the service management module 102 receives an acknowledgment message for the transfer standby message from the device management module 104, the service management module 102 stores the transfer standby message except for the selected transfer standby message To the device management module 104, each of the transmission wait messages that have not yet expired. In the above example, when the service management module # 0 receives the acknowledgment message for the transmission standby message # 3 from the device management module 3, among the remaining transmission standby messages except the transmission standby message # 3, the service management module # Each of the transfer waiting messages may be transmitted to the device management module 3. [

At this time, the service management module 102 may sequentially transmit a predetermined number of transmission wait messages, which are not valid yet, among the remaining transmission wait messages, or may transmit the transmission standby messages in units of a predetermined size. As an example, the service management module 102 may perform bulk transmission of the transmission standby messages that have not been validated at the present time among the remaining transmission standby messages in a predetermined number of units (for example, 100), that is, a bulk message ). ≪ / RTI > As another example, the service management module 102 may group the transmission wait messages, which are not yet valid, among the remaining transmission wait messages in a predetermined size unit (for example, 5 MB units). In this case, the device management module 104 may separate each of the transmission standby messages and transmit an ACK message for each transmission standby message to the service management module 102. The device management module 104 may also transmit the ACK message to the service management module 102 in units of a set size.

In addition, the service management module 102 may have a plurality of threads for sending and receiving messages. In this case, each thread may send one or more send wait messages and receive acknowledgment messages therefrom. At this time, each thread can set whether or not to transmit a message to the database when the message is transmitted in order to prevent the transmission standby message from being transmitted in duplicate. Specifically, the thread transmitting the transmission standby message can activate the setting of the database indicating whether the transmission standby message is transmitted (that is, setting that the current transmission standby message is being transmitted). If a thread other than the thread transmitting the thread, i.e., the transmission wait message, receives an acknowledgment message (or a connection acknowledgment message of the device management module 104) for at least a part of the transmission wait message, It can be confirmed that each of the transmission wait messages is currently being transmitted. Accordingly, the transmission wait messages are not transmitted repeatedly.

As an example, when the thread # 1 of the service management module # 0 transmits # 1 to # 10 of the transmission standby messages # 1 to # 100 to the device management module 3, the thread # 2 of the service management module # 2, the thread # 2 can confirm that each of the transmission standby messages is currently being transmitted by referring to the database. Accordingly, the transmission of the transmission standby messages # 11 to # As shown in FIG. In this case, the thread # 1 can normally transmit the transfer wait messages # 11 to # 20 to the device management module 3.

The device management module 104, as a device-side component, transmits and receives various messages related to the application service between the application client (not shown) installed in the device and the message server 106. In embodiments of the present invention, the device may be a terminal carried by the user, for example, a mobile terminal such as a smart phone, a notebook, a tablet PC, or the like. Further, the application client is a module installed in the device and causing the device to execute the application service provided by the application server.

The device management module 104 receives a message associated with the application service from the service management module 102 via the message server 106 and transmits an acknowledgment message (i.e., an ACK message) To the service management module 102. When receiving a message from the service management module 102, the device management module 104 determines whether or not the message is already processed. If the message is determined not to be a processed message, (That is, whether or not a previous message ID is present in the message). If it is determined that the message is the above-described order guarantee message, the device management module 104 refers to the database to determine whether processing of the previous message of the message is completed, It may transmit a check message for checking the state of the previous message to the service management module 102. In addition, the device management module 104 may perform additional functions such as cancellation of message transmission, management of authentication information for security, and the like.

At least one such device management module 104 may exist for each device, and each device management module 104 may have a different ID. The device can be assigned the ID of the device management module 104 from the message server 106 in the process of activating the device management module 104 for the first time. In addition, the device in which the device management module 104 and the device management module 104 are installed may be located in the second network. In the present embodiments, the second network may be an outside area of the first network, for example, the Internet.

The message server 106 is a server that relays (or bi-directionally transmits) a message related to an application service between the service management module 102 and the device management module 104. At this time, the message server 106 may be located in a demilitarized zone (DMZ) between the first network and the second network. A DMZ is a subnetwork located between a first network and a second network, and a firewall may exist between the first network and the DMZ.

The message server 106 may include various channel managers for message relaying, and may route the messages through the channel manager.

The third party message server 108 may be a message server of another organization or enterprise, for example a message server (or push server) of Google Cloud Messaging (GCM), Apple Push Notification Service (APNS). The message server 106 may send and receive messages associated with application services to and from the third party message server 108 via an internal channel manager.

Figure 2 is an illustration of a service management module 102 and an application server 200 according to one embodiment of the present invention.

Referring to FIG. 2, the service management module 102 according to an embodiment of the present invention may exist for a plurality of (for example, 100) load balancing and may call a function through a library (not shown) Way communication with the application server 200 in the form of a message. To this end, the service management module 102 may include an interface (not shown) for bidirectional communication with the application server 200. As described above, the service management module 102 generates a message related to the application service according to a request of the application server 200, stores the message in the database 150, (104). The database 150 may be coupled to each service management module 102 in the first network.

At this time, the message includes a message ID, a source address, a destination address, via information, an ID of a previously transmitted message (i.e., a previous message ID), a valid time period (TTL: Time To Live, a creation time, identification information of an application service, and the like. Here, the sender address may include the ID of the service management module 102 that transmits the message, and the receiver address may include the ID of the device management module 104, which is the destination of the message. The message server 106 may route the message to the device management module 104 using the sender information, recipient information, transit information, and the like included in the message.

FIG. 3 is an illustration of a device management module 104 and device 300 in accordance with an embodiment of the present invention.

Referring to FIG. 3, the device management module 104 according to an embodiment of the present invention is installed in the device 300 and transmits and receives messages related to the application service to each application client 302. The device management module 104-1 can bidirectionally communicate with the application client 302 in the form of calling a function through a library (not shown). To this end, the device management module 104-1 may include an interface (not shown) for bi-directional communication with the application client 302. [

The device management module 104 also receives a message associated with the application service from the service management module 102 via the message server 106 and transmits an acknowledgment message for the message via the message server 106 Message to the service management module 102.

According to an embodiment of the present invention, the application server 200 side component, that is, the service management module 102 may be configured as a multi-instance for load balancing, and the application server 200 may configure the multi- 300) side component, that is, the device management module 104, as shown in FIG. However, even if the service management module 102 is configured as a multi-instance, when a message to be retransmitted or deleted is concentrated in the specific service management module 102, a load is concentrated only on the service management module 102, Can be degraded. In addition, each service management module 102 may repeatedly transmit the same message, thereby frequently generating an unnecessary load. Accordingly, in the embodiments of the present invention, regardless of whether a message transmission is requested to a service management module 102, the message re-transmission and deletion processing for the specific device management module 104 is performed only by the specific service management module 102 So that duplicate transmission of messages can be prevented and load can be distributed. This will be described later in detail with reference to FIG.

4 is a block diagram illustrating a detailed configuration of a service management module 102 according to an embodiment of the present invention. 4, the message processing module according to an embodiment of the present invention includes a generating unit 402, a determining unit 404, and a processing unit 406. [

The generation unit 402 generates a message related to the application service as it receives a message generation request from the application server. At this time, the message creation request may include recipient information of the message, identification information of an application service related to the message, and the like. The generating unit 402 may generate a message ID according to the message creation request, and may generate a message corresponding to the message ID. For example, the generating unit 402 may generate the message ID by combining the identification information of the device to which the message is to be transmitted, the identification information of the application related to the message, and the like, and generate a corresponding message.

Referring to FIG. 5, the message may include a message ID, a sender address, a recipient address, passerby information, an ID of a previously transmitted message, a validity period (TTL), a generation time, . The sender address, the receiver address, the passerby information, the identification information of the application service related to the message, and the like can be included in the message generation request. The generation unit 402 refers to the message generation request, . In addition, the message generation request may include information on whether a message to be generated is an order guarantee message. If the message is an order assurance message, the creator 402 can refer to the database 150 to identify the previous message ID (i.e., the previous message ID) of the message. For example, the generation unit 402 may determine the last recorded message ID of the message ID recorded in the database as the previous message ID, and store the previous message ID in the header of the message. At this time, if there is no previous message (i.e., there is no previous message ID recorded in the database), the generating unit 402 may store its own message ID in the header of the message. In addition, the validity period of the message can be determined according to a set policy, and the generation time of the message can be automatically generated when a message is generated. An example of the message thus generated is shown in FIG.

The determination unit 404 determines one or more responsible device management modules that the plurality of device management modules 104 are responsible for using the IDs of the device management modules 104 and the total number of the service management modules 102 .

First, the determination unit 404 may obtain the hash value for each ID of the device management module 104 and the total number of the service management modules 102, by referring to the database 150. The hash value of each of the device management modules 104 or the ID of each of the device management modules 104 may be stored in the database 150. The decision unit 404 may refer to the database 150, The hash value for each ID of the device management module 104 can be directly obtained by acquiring the ID of each device management module 104 and then hashing it or referring to the database 150. [ Each service management module 102 may record its own identification number in the database 150 and the determination unit 404 checks the total number of the service management modules 102 by referring to the database 150 . As an example, the determination unit 404 can check the total number of the service management module 102 by referring to the identification number of the service management module 102 last recorded in the database 150. [

Next, the determination unit 404 performs a modulus operation on the hash values of the IDs of the device management modules 104 to the total number of the service management modules 102, The modular operation value can be calculated. A modular operation is an operation to obtain the remainder by dividing two values. In the modular operation expressed by a mod b (or a% b), the remainder value when a is divided by b is output. The hash value of each of the device management modules 104 is different from the hash value of each of the device management modules 104. Therefore, The device management modules 104 may be uniformly grouped by the total number of the service management modules at a random probability. As an example, when the number of the service management module 102 and the number of the device management modules 104 is 100 and 400,000, respectively, the determination unit 404 determines 400,000 device management modules 104 through the modular operation Grouping can be grouped into 100 groups (i.e., groups corresponding to the modular operation values 0, 1, 2 ... 99 respectively).

Next, the determination unit 404 can determine the responsible device management module by referring to the modular operation value and its identification number. Specifically, the determining unit 404 compares the moduler operation value with its own identification number, finds a moduler operation value corresponding to (or coinciding with) its own identification number in the moduler operation value, A device management module having an ID of a device management module (i.e., an ID of a device management module used to acquire the modular operation value) may be determined by the device management module in charge. In this manner, each service management module 102 can determine the respective chargeable device management modules through the modular operation, and accordingly, the chargeable device management modules for each service management module 102 can obtain uniformity Lt; / RTI >

Hereinafter, a process of determining a chargeable device management module in the decision unit 404 will be described with reference to FIG.

Here, it is assumed that the number of the service management module 102 and the number of the device management module 104 are three and nine, respectively. It is assumed that the identification numbers of the respective service management modules 102 are # 0, # 1 and # 2, and the hash values for the IDs of the device management modules 104 are 1, 2, 3 ... 9 .

As described above, the determination unit 404 of each service management module 102 performs a modular operation on the hash values of the IDs of the device management modules to the total number of the service management modules, And determine the responsible device management module by referring to the modular operation value and its own identification number. Here, the determination unit 404 of each service management module 102 can calculate the modular operation values as shown in Table 1 below.

Device management module Modular operation value Device management module 1 One Device Management Module 2 2 Device Management Module 3 0 Device Management Module 4 One Device Management Module 5 2 Device Management Module 6 0 Device Management Module 7 One Device Management Module 8 2 Device Management Module 9 0

Then, the determination unit 404 of each service management module 102 finds a modulo operation value corresponding to its own identification number among the modulo operation values, and determines the ID of the device management module associated with the modulo operation value (that is, The ID of the device management module used to acquire the operation value) can be determined by the device management module in charge. In the above example, the service management module # 0 determines the device management module 3, the device management module 6, and the device management module 9 associated with the modular operation value 0 as the responsible device management module, and the device management module 3, the device management module 6, Only the message retransmission and deletion processing for the management module 9 can be performed. The service management module # 1 determines the device management module 1, the device management module 4, and the device management module 7 associated with the modular operation value 1 as the responsible device management module. The device management module 1, the device management module 4, 7 only for the message retransmission and deletion processing. The service management module # 2 determines the device management module 2, the device management module 5, and the device management module 8 associated with the modular operation value 2 as the responsible device management module. The device management module 2, the device management module 5, 8 only for message retransmission and deletion processing.

4, the processing unit 406 retransmits or deletes the message sent to the responsible device management module of the service management module 102. [ As described above, when the service management module 102 does not receive the acknowledgment message for the message within the set time, the service management module 102 can retransmit the message. When receiving the acknowledgment message for the message within the set time, And delete the message stored in the memory 150. In performing the message retransmission and deletion processing, the processing unit 406 performs only the message retransmission and deletion processing for the responsible device management module in charge of itself and retransmits the message to the other device management module And deletion processing is not performed.

In addition, the processing unit 406 can determine whether to retransmit or delete the message every set period (for example, two minutes). At this time, the period may be different for each service management module 102. The processing unit 406 may retransmit or delete the messages for each chargeable device management module one by one for each cycle.

At this time, if there are a plurality of transmission standby messages to be transmitted to the device management module 104, the processing unit 406 selects one transmission standby message based on the generation time and the valid period of the transmission standby message, To the device management module 104. In this case, Specifically, the processing unit 406 can select one transmission wait message having the oldest generation time without passing the present validity period among the transmission standby messages. If the service management module 102 receives an acknowledgment message from the device management module 104 (or receives a connection confirmation message from the message management server 104) from the message server 106, The processing unit 406 may determine that the device management module 104 is normally connected to the message server 106 (that is, the remaining transmission wait message is also ready to be received).

The service management module 102 receives an acknowledgment message from the device management module 104 (or receives a connection confirmation message from the message management server 104) from the message server 106, The processing unit 406 may transmit to the device management module 104 each of the remaining transmission wait messages other than the selected one of the transmission standby messages, At this time, the processing unit 406 may sequentially transmit each of the predetermined number of transmission standby messages that have not been valid for the remaining transmission standby messages, or may transmit the transmission standby messages in units of a predetermined size.

In addition, when the service management module 102 has a plurality of threads for sending and receiving a message, a thread transmitting a transmission wait message can write (or set) to the database that the current transmission wait message is being transmitted have. If a thread other than the thread transmitting the thread, i.e., the transmission wait message, receives an acknowledgment message (or a connection acknowledgment message of the device management module 104) for at least a part of the transmission wait message, It can be confirmed that each of the transmission wait messages is currently being transmitted. Accordingly, the transmission wait messages are not transmitted repeatedly.

The processing unit 406 can also receive messages from the device management module 104 and process them. Hereinafter, for convenience of explanation, a message received from another module will be referred to as a " received message ".

First, the processing unit 406 can determine whether the received message is already processed by using the ID of the received message. Specifically, the processing unit 406 may determine whether the received message is a processed message according to whether the ID of the received message is recorded in the message log table of the database 150. [ As an example, when the ID of the received message is recorded in the message log table of the database 150, the processing unit 406 determines that the received message is already processed and does not proceed with the next process. As another example, if the ID of the received message is not recorded in the message log table of the database 150, the processing unit 406 determines that the received message is not a processed message (i.e., determines that the received message is a new message) can do.

If it is determined that the received message is not a processed message, the processing unit 406 determines whether a previous message ID exists in the received message (i.e., whether or not the received message is an ordered guarantee message) .

If the previous message ID does not exist in the received message, the processing unit 406 may transmit the received message to the application server.

If there is a previous message ID in the received message, the processor 406 may refer to the database 150 to determine whether or not the previous message of the received message has been processed. At this time, if it is determined that the processing of the previous message of the received message is completed, the processing unit 406 can deliver the received message to the application server. On the other hand, if it is determined that the process of the previous message of the received message is not completed, the processing unit 406 stores the received message in the database 150, and transmits a check message for status check of the previous message to the device To the management module 104.

Although the process of generating, retransmitting, and receiving a message has been described with reference to the service management module 102 for the sake of convenience, the process of generating, retransmitting, and receiving the message is the same or similar to that of the device management module 104 Can be applied. For example, the device management module 104 may generate a message according to a message creation request of the application client and transmit the message to the service management module 102. At this time, the information included in the message is the same as that shown in FIG. In addition, the device management module 104 selects one of the plurality of transmission waiting messages to be transmitted to the service management module 102, which is the oldest generation time without exceeding the valid period, The service management module 102 may first check whether the service management module 102 is connected or not. When receiving the reception message from the service management module 102, the device management module 104 determines whether or not the received message is already processed. If the received message is determined to be not a processed message It may determine whether a previous message ID exists in the received message and determine whether to generate a check message.

7 is a flowchart illustrating a process of a transmission wait message according to an embodiment of the present invention. In the following flow charts shown in Figs. 7 to 10, the method is described by dividing into a plurality of steps, but at least some of the steps may be performed in reverse order, combined with other steps, performed together, omitted, Or one or more steps not shown may be added.

In step S102, the service management module 102 determines one or more responsible device management modules that the plurality of device management modules 104 are responsible for.

In step S104, the service management module 102 determines whether or not the ID of the responsible device management module exists in a plurality of transmission wait messages. If it is determined in step S104 that the ID of the responsible device management module does not exist in the plurality of transmission wait messages, the service management module 102 terminates the process.

If it is determined in step S104 that the ID of the responsible device management module exists in the transmission standby message, the service management module 102 transmits the transmission standby message having the oldest creation time among the transmission standby messages corresponding to the responsible device management module Search.

In step S108, it is determined whether there is a transmission wait message with the oldest generation time among the transmission wait messages corresponding to the responsible device management module. If there is no transmission standby message corresponding to the responsible device management module as a result of the determination in step S108, the service management module 102 determines whether there is an id of another responsible device management module (Step S104).

If it is determined in step S110 that there is a transmission standby message corresponding to the responsible device management module as a result of the determination in step S108, the service management module 102 determines whether or not the transmission standby message, . If it is determined in step S108 that the oldest transmission wait message has passed the current validity period, the service management module 102 may search for the next oldest transmission wait message.

If it is determined in step S112 that the oldest transmission wait message does not exceed the current validity period, the service management module 102 transmits the oldest transmission wait message to the corresponding in-charge device management module 104 .

8 is a flowchart illustrating a process of a transmission wait message according to an embodiment of the present invention.

In step S202, a thread of the service management module 102 receives an acknowledgment message for the transmission standby message or a connection confirmation message of the device management module 104 transmitted in FIG.

In step S204, the thread checks whether the current transmission wait message is being transmitted through the database 150. [ If it is determined in step S204 that the current transmission wait message is being transmitted, the thread may terminate the message transmission / reception process without transmitting the transmission standby message.

If it is determined in step S204 that the current transmission standby message is not being transmitted, the thread activates the setting of the database indicating whether the transmission standby message is transmitted (that is, the current transmission standby message is being transmitted Setting).

In step S208, the thread retrieves a transmission wait message corresponding to the device management module in charge of the service management module 102. [

In step S210, the thread determines whether there is a transfer wait message corresponding to the device management module in charge. If it is determined in step S210 that there is no transmission standby message corresponding to the responsible device management module, the thread can terminate the message transmission / reception process as it is.

If it is determined in step S212 that there is a transfer wait message corresponding to the responsible device management module, the thread determines whether the transfer wait message has passed the validity period. If it is determined in step S212 that the waiting-for-transmission message has passed the validity period, the thread can search for another transmission waiting message corresponding to the responsible device management module.

In step S214, if it is determined in step S212 that the wait-for-transmission message does not exceed the validity period, the thread transmits the wait-for-each-not-send message to the in-charge device management module. At this time, the thread may sequentially transmit each of the set number of transmission wait messages or may transmit each of the transmission wait messages in units of a predetermined size.

9 is a flowchart illustrating a process of a received message performed by the service management module 102 according to an embodiment of the present invention.

In step S302, the service management module 102 receives the reception message from the device management module 104. [

In step S304, the service management module 102 determines whether the received message is a processed message using the ID of the received message. Specifically, the service management module 102 may determine whether the received message is a processed message according to whether the ID of the received message is recorded in the message log table of the database 150. [ If it is determined in step S304 that the received message is already processed, the service management module 102 may terminate the process.

If it is determined in step S306 that the received message is not a processed message, the service management module 102 determines whether a previous message ID exists in the received message.

If it is determined in step S308 that the previous message ID does not exist in the received message, the service management module 102 transmits the received message to the application server.

In step S310, the service management module 102 transmits an acknowledgment message (ACK message) to the device management module 104 for the received message.

In step S312, the service management module 102 records in the database 150 the log information of the received message and whether the processing is completed.

In step S314, the service management module 102 determines whether the received message is received earlier than other messages in that order. If it is determined in step S314 that the received message is not received earlier than other messages, the service management module 102 terminates the process.

If it is determined in step S314 that the received message is received earlier than other messages in step S314, the service management module 102 temporarily stores the received message in the database 150, And delivers the received message to the application server after being received.

If it is determined in step S318 that the previous message ID exists in the received message, the service management module 102 determines whether the previous message of the received message has been processed. If it is determined in step S318 that the processing of the previous message of the received message is completed, the service management module 102 delivers the received message to the application server.

If it is determined in step S320 that the processing of the previous message of the received message is not completed, the service management module 102 stores the received message in the database 150 in step S320.

In step S322, the service management module 102 transmits an acknowledgment message (ACK message) to the device management module 104 for the received message.

In step S324, the service management module 102 transmits a check message for checking the state of the previous message to the device management module 104. [

FIG. 10 is a flowchart illustrating a process of a received message performed by the device management module 104 according to an embodiment of the present invention.

In step S402, the device management module 104 receives a reception message from the service management module 102. [

In step S404, the device management module 104 transmits an acknowledgment message (ACK message) to the service management module 102 for the received message.

In step S406, the device management module 104 determines whether the received message is a processed message using the ID of the received message. The process of determining whether the received message is already processed is the same as that in step S304 of FIG.

If it is determined in step S408 that the received message is not a processed message, the device management module 104 stores the received message in the database 150. In step S408,

In step S410, the device management module 104 determines whether a previous message ID is present in the received message.

If it is determined in step S412 that the previous message ID does not exist in the received message, the device management module 104 transmits the received message to the application client.

In step S414, the device management module 104 records in the database 150 the log information of the received message and whether the processing is completed.

In step S416, the device management module 104 determines whether the received message is received earlier than other messages in that order. If it is determined in step S416 that the received message is not received earlier than other messages in the order, the device management module 104 ends the process.

If it is determined in step S418 that the received message is received earlier than other messages in step S416, the device management module 104 temporarily stores the received message in the database 150, And delivers the received message to the application client after it is received.

On the other hand, if it is determined in step S420 that the previous message ID exists in the received message, the device management module 104 determines whether the previous message of the received message has been processed. If it is determined in step S420 that the processing of the previous message of the received message is completed, the device management module 104 transfers the received message to the application client.

If it is determined in step S422 that the processing of the previous message of the received message is not completed as a result of the determination in step S410, the device management module 104 transmits a check message for checking the status of the previous message to the service management module 102 do.

11 is a block diagram illustrating and illustrating a computing environment including a computing device suitable for use in the exemplary embodiments. In the illustrated embodiment, each of the components may have different functions and capabilities than those described below, and may include additional components in addition to those described below.

The illustrated computing environment 10 includes a computing device 12. In one embodiment, computing device 12 may be one or more components included in message processing device 100, or message processing device 100.

The computing device 12 includes at least one processor 14, a computer readable storage medium 16, The processor 14 may cause the computing device 12 to operate in accordance with the exemplary embodiment discussed above. For example, processor 14 may execute one or more programs stored on computer readable storage medium 16. The one or more programs may include one or more computer-executable instructions, which when executed by the processor 14 cause the computing device 12 to perform operations in accordance with the illustrative embodiment .

The computer-readable storage medium 16 is configured to store computer-executable instructions or program code, program data, and / or other suitable forms of information. The program 20 stored in the computer-readable storage medium 16 includes a set of instructions executable by the processor 14. In one embodiment, the computer-readable storage medium 16 may be any type of storage medium such as a memory (volatile memory such as random access memory, non-volatile memory, or any suitable combination thereof), one or more magnetic disk storage devices, Memory devices, or any other form of storage medium that can be accessed by the computing device 12 and store the desired information, or any suitable combination thereof.

Communication bus 18 interconnects various other components of computing device 12, including processor 14, computer readable storage medium 16.

The computing device 12 may also include one or more input / output interfaces 22 and one or more network communication interfaces 26 that provide an interface for one or more input / output devices 24. The input / output interface 22 and the network communication interface 26 are connected to the communication bus 18. The input / output device 24 may be connected to other components of the computing device 12 via the input / output interface 22. The exemplary input and output device 24 may be any type of device, such as a pointing device (such as a mouse or trackpad), a keyboard, a touch input device (such as a touch pad or touch screen), a voice or sound input device, An input device, and / or an output device such as a display device, a printer, a speaker, and / or a network card. The exemplary input and output device 24 may be included within the computing device 12 as a component of the computing device 12 and may be coupled to the computing device 12 as a separate device distinct from the computing device 12 It is possible.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, I will understand. Therefore, the scope of the present invention should not be limited to the above-described embodiments, but should be determined by equivalents to the appended claims, as well as the appended claims.

10: Computing environment
12: computing device
14: Processor
16: Computer readable storage medium
18: Communication bus
20: Program
22: I / O interface
24: input / output device
26: Network communication interface
100: Message processing device
102: service management module
104: Device management module
106: message server
108: Third party message server
150: Database
200: Application server
300: device
302: Application client
402: DB access unit
404:
406:

Claims (17)

A plurality of device management modules; And
The device management module determines at least one responsible device management module of the plurality of device management modules, and when there is a plurality of transmission wait messages to be transmitted to the responsible device management module, And a service management module for selecting one transmission standby message based on time to live (TTL) and transmitting the selected transmission standby message to the corresponding device management module.
The method according to claim 1,
Wherein the service management module selects one of the plurality of transmission wait messages, the one of the plurality of transmission wait messages being the oldest generation time without exceeding the current valid period.
The method according to claim 1,
Wherein the service management module determines that the device management module is normally connected to the message server when receiving an acknowledgment message for the transmission standby message from the device management module.
The method of claim 3,
Wherein the service management module is configured to transmit the transmission standby message that has not expired at the present time among the remaining transmission standby messages except for the transmission standby message selected when the reception confirmation message or the connection confirmation message of the responsible device management module is received To the responsible device management module.
The method of claim 4,
Wherein the service management module sequentially transmits each of a predetermined number of transmission standby messages that have not reached the valid period of the remaining transmission standby messages or bundles the transmission standby messages in units of a predetermined size.
The method of claim 4,
When the service management module includes a plurality of threads for transmitting and receiving a message,
The thread transmitting the transmission standby message activates the setting of the database indicating whether the transmission standby message is transmitted,
If the thread other than the thread receives the acknowledgment message for at least a part of the transmission wait message or the connection acknowledgment message for the responsible device management module, it is determined that each transmission wait message is currently being transmitted Thereby preventing the transmission wait messages from being duplicated.
The method according to claim 1,
Wherein the service management module determines whether the received message is already processed by using the ID of the received message when receiving the received message from the device management module, And judges whether or not a previous message ID exists in the received message if it is determined that the previous message ID exists.
The method of claim 7,
The service management module determines whether the previous message of the received message has been processed by referring to the database if the previous message ID is found in the received message, And transmits a check message for status check of the previous message to the device management module when it is determined that the process for the previous message is not completed.
1. A message processing method performed by a service management module connected to a plurality of device management modules via a network,
Determining at least one chargeable device management module in charge of the plurality of device management modules,
If there is a plurality of transmission wait messages to be transmitted to the responsible device management module, the processing unit selects one transmission wait message based on the generation time of the transmission wait message and the set time-to-live (TTL) step; And
And transmitting, at the processing unit, the selected transmission wait message to the responsible device management module.
The method of claim 9,
Wherein the selecting of the one transmission wait message selects one transmission wait message having the oldest generation time without exceeding the current validity period among the plurality of transmission standby messages.
The method of claim 9,
After transmitting the selected transmission wait message to the responsible device management module,
Further comprising the step of the processor determining that the device management module is normally connected to the message server when receiving an acknowledgment message for the transmission standby message from the device management module.
The method of claim 11,
After transmitting the selected transmission wait message to the responsible device management module,
When the reception confirmation message or the connection confirmation message of the responsible device management module is received, in the processing unit, among the remaining transmission standby messages except for the selected transmission standby message, each of the transmission standby messages, And sending the message to the device management module.
The method of claim 12,
Wherein the step of transmitting each of the transmission standby messages to the corresponding device management module comprises the steps of sequentially transmitting each of the remaining transmission standby messages and a predetermined number of transmission standby messages not exceeding the valid period, A method for processing a message, the method comprising:
The method of claim 12,
When the service management module includes a plurality of threads for transmitting and receiving a message,
Wherein the step of transmitting each of the transmission wait messages to the responsible device management module comprises:
Activating, in a thread for transmitting each of the transmission wait messages, a setting of a database indicating whether or not the transmission wait message is transmitted; And
If the thread other than the thread receives the acknowledgment message for at least a part of the transmission wait message or the connection acknowledgment message for the responsible device management module, it is determined that each transmission wait message is currently being transmitted And preventing each of the transmission wait messages from being duplicated upon acknowledgment.
The method of claim 9,
Determining whether the received message is a processed message using the ID of the received message when the processing unit receives the received message from the device management module; And
Further comprising the step of determining whether a previous message ID is present in the received message if the processing unit determines that the received message is not a processed message.
16. The method of claim 15,
After determining whether the previous message ID is present in the received message,
Determining whether the processing of the previous message of the received message is completed with reference to the database when the processing unit determines that the previous message ID exists in the received message; And
Further comprising the step of, when the processing unit determines that processing of the previous message of the received message is not completed, transmitting a check message for status check of the previous message to the device management module.
A service management module connected to a plurality of device management modules via a network,
A determination unit that determines one or more responsible device management modules of the plurality of device management modules that are responsible for the plurality of device management modules; And
When a plurality of transmission wait messages to be transmitted to the responsible device management module exist, selects one transmission wait message based on the generation time of the transmission wait message and the set time-to-live (TTL) And a processing unit for transmitting the selected transmission wait message to the corresponding device management module.

Images