KR102119456B1 - Distributed Broker Coordinator System and Method in a Distributed Cloud Environment - Google Patents

Abstract

A coordinator system is disclosed. The coordinator system receives a broker mapping information request from a client, and a coordinator server server that allocates a broker mapping operation according to the broker mapping information request, and a plurality of distributed broker leaders receiving broker mapping operations from the coordinator server and a processing server that selects an optimal distributed broker leader from among (broker leaders)-a set of distributed broker leaders selected from a plurality of distributed brokers and maps the client.

Description

Distributed broker coordinator system and method in a distributed cloud environment

The present invention relates to a coordinator system and method in a distributed cloud environment, and more particularly, to a system and method for coordinating and distributing a message broker in a cloud environment.

MQTT (Message Queuing Telemetry Transport) is a technology that uses a broker to send and receive messages in a publish/subscribe manner, and operates on a TCP/IP protocol with minimal protocol overhead. MQTT is a long message queue. When a specific topic and message are published, it is moved to the MQTT broker, and in the MQTT broker, a subscriber corresponding to the topic specified by the publication. ). Therefore, each client can communicate with each other wherever the Internet is connected only by matching a specific topic even if they do not know each other's IP information. In addition, when a client publishes a message to a specific topic, 1:N communication is possible by sending a message to all clients on the network that subscribe to the topic. To this end, in the existing cloud computing environment, a message broker is placed in the cloud. Communication has been carried out.

However, the existing model has the following problems.

Iv) Publish/Subscribe model performs 1:N communication, so even if one message is transmitted, n times network traffic occurs. Therefore, in a cloud system that manages billions of IoT devices and millions of clients, it is necessary to distribute the load generated in the cloud.

Ii) Many systems are passively configured for configuration and maintenance, and there is no technology to dynamically configure them.

Iii) For effective overlay configuration of brokers, scalability is not guaranteed and latency exists.

In other words, since the messaging service of the existing cloud environment communicates through a broker in the central cloud to ensure messaging between all clients, the above-described problem occurs, and particularly, the network load occurring in the central cloud as the number of clients increases. Increases.

Republic of Korea Registered Patent No. 1877188 Republic of Korea Patent Publication No. 2017-0058201

An object of the present invention is to provide a system and a method for preventing traffic from occurring even while performing 1:N communication in a Publish/Subscribe model.

The coordinator system according to an embodiment of the present invention receives a broker mapping information request from a client, and a coordinator server server that allocates a broker mapping operation according to the broker mapping information request, and a broker mapping operation from the coordinator server. A processing server that maps to the client by selecting an optimal distributed broker leader from among a plurality of distributed broker leaders assigned-one set of distributed broker leaders selected from a plurality of distributed brokers. It can contain.

Here, the processing server may select the distributed broker leader closest to the client from among the plurality of distributed broker leaders as the optimal distributed broker leader.

Here, the coordinator server can operate based on a layered data model having a directory format.

Here, the coordinator server may transmit broker mapping information including information about the optimal distributed broker leader to the client.

Here, the distributed broker publishes a publish/subscribe table that includes publish/subscribe (Pub/Sub) information between the clients and a topic routing table that includes information about topics subscribed to by the client. / Subscription module, and a bridging manager module that exchanges data by connecting the coordinator server and the distributed broker.

Here, it may further include a processing server reader that delivers the task assigned from the coordinator server to the processing server in a topic format.

Here, the optimal distributed broker leader receives the first broker connection information request from the client, and the closest distribution to the client in the broker group including the optimal distributed broker leader according to the first broker connection information request A first optimal distributed broker that is a broker may be selected, and first broker connection information including information on the first optimal distributed broker may be transmitted to the client.

Here, when the client's connection request to the first optimal distributed broker fails, the optimal distributed broker reader receives a request for second broker connection information from the client, and the second broker connection The second optimal distributed broker, which is the closest distributed broker to the client, is selected from among the remaining distributed brokers except the first optimal distributed broker in which the connection request has failed in the broker group including the optimal distributed broker leader according to the information request. In addition, second broker connection information including information on the second optimal distributed broker may be transmitted to the client.

As a coordinator method performed by a coordinator system according to an embodiment of the present invention, the client requests broker mapping information from a coordinator server, and the coordinator server allocates a broker leader mapping task to a processing server Step, the processing server is assigned a broker leader mapping operation, and selects the best distributed broker leader among a plurality of distributed broker leaders-a set of distributed broker leaders selected from among multiple distributed brokers. And transmitting broker mapping information including information about the optimal distributed broker reader to the client, the client requesting first broker connection information from the optimal distributed broker reader, and the optimal distributed broker A leader selects a first optimal distributed broker from a broker group including the optimal distributed broker leader according to the request for the first broker connection information, and a first broker connection including information about the first optimal distributed broker And transmitting information to the client, and connecting the client to the first optimal distributed broker.

Here, when a connection request to the first optimal distributed broker fails in a step of connecting to the first optimal distributed broker, the client sends second broker connection information to the optimal distributed broker reader. Requesting step, the optimal distributed broker leader among the remaining distributed brokers except for the first optimal distributed broker whose connection request has failed in the broker group including the optimal distributed broker leader according to the second broker connection information request Selecting a second optimal distributed broker, transmitting second broker connection information including information about the second optimal distributed broker to the client, and the client connected to the second optimal distributed broker It may further include a step.

Here, in the step of allocating the broker reader mapping operation, if there is a processing server leader elected to perform a role of transferring data between the coordinator server and the remaining processing servers among a plurality of processing servers, the processing server leader To the broker leader mapping task.

Here, the step of allocating the broker reader mapping operation may further include the step of forwarding the task assigned by the processing server leader from the coordinator server to a processing server of any one of the plurality of processing servers in a topic format. have.

Here, the first optimal distribution broker receiving a message on a specific topic (Pub) from a publishing (Pub) client, and sending the message to a subscribing (Sub) client subscribing to the specific topic It may further include.

Here, the optimal distributed broker leader is the distributed broker closest to the client among the plurality of distributed broker leaders, and the first optimal distributed broker is connected to the client in a broker group including the optimal distributed broker leader. It may be the nearest distributed broker.

According to an embodiment of the present invention, by distributing a distributed message broker in a distributed cloud environment, it is possible to apply in a large-scale distributed cloud environment by enabling N:N communication rather than 1:N.

In addition, it can have scalability of distributed brokers and guarantee low latency.

In addition, when controlling various devices in a distributed IoT environment, performance can be improved to manage data.

1 schematically illustrates a distributed broker system according to an embodiment of the present invention.
2 is a block diagram of a distributed broker system according to an embodiment of the present invention.
3 shows an example of a layered data model of the coordinator system.
4 is a flowchart of a coordinator method according to an embodiment of the present invention.
5 is a flowchart of a coordinator method when a connection request to a distributed broker fails.

Specific structural or functional descriptions of the embodiments according to the concept of the present invention disclosed in this specification are exemplified only for the purpose of illustrating the embodiments according to the concept of the present invention, and the embodiments according to the concept of the present invention These can be implemented in various forms and are not limited to the embodiments described herein.

Embodiments according to the concept of the present invention can be applied to various changes and have various forms, so the embodiments will be illustrated in the drawings and described in detail herein. However, this is not intended to limit the embodiments according to the concept of the present invention to specific disclosure forms, and includes modifications, equivalents, or substitutes included in the spirit and scope of the present invention.

Terms such as first or second may be used to describe various components, but the components should not be limited by the terms. The above terms are only for the purpose of distinguishing one component from other components, for example, without departing from the scope of rights according to the concept of the present invention, the first component may be referred to as the second component, Similarly, the second component may also be referred to as the first component.

When an element is said to be "connected" or "connected" to another component, it is understood that other components may be directly connected to or connected to the other component, but there may be other components in between. It should be. On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that no other component exists in the middle. Expressions describing the relationship between the components, for example, "between" and "immediately between" or "directly adjacent to" should be interpreted similarly.

The terminology used herein is only used to describe specific embodiments and is not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this specification, the terms "include" or "have" are intended to designate the presence of a feature, number, step, action, component, part, or combination thereof as described, one or more other features or numbers, It should be understood that the presence or addition possibilities of steps, actions, components, parts or combinations thereof are not excluded in advance.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person skilled in the art to which the present invention pertains. Terms, such as those defined in a commonly used dictionary, should be interpreted as having meanings consistent with meanings in the context of related technologies, and should not be interpreted as ideal or excessively formal meanings unless explicitly defined herein. Does not.

1 schematically illustrates a distributed broker system according to an embodiment of the present invention.

Referring to FIG. 1, a distributed broker system 1 according to an embodiment of the present invention includes a plurality of distributed brokers 20 and a coordinator system arranged for providing messaging services to clients 10a to 10j in a cloud environment ( 30). In other words, while the messaging service of the existing cloud environment communicates through a broker in the central cloud to ensure messaging between all clients, in the case of the present invention, distributed brokers 20 are arranged to occur in a broker in the central cloud Network load.

The distributed brokers 20 can be applied and deployed in various distributed computing models. For example, as shown in FIG. 1, it is located between cloud clusters 21a to 21b and cloud clusters 21a to 21b and clients 10a to 10j that are physically distributed in different regions. It can be applied and deployed in a distributed computing model composed of physically distributed fog clusters 22a to 22c.

In order to properly map the distributed brokers 20 to the clients 10a to 10j, the present invention uses a coordination service. Here, the coordination service may mean software or an application for distributed coordination, for example, a zookeeper. The coordination service provides various services for coordination, such as synchronization, configuration management, grouping, and naming. Since the coordination service is replicated in a group including a plurality of servers, which may also be referred to as an ensemble, the clients 10a to 10j can use the coordination service by connecting to any server in the ensemble.

Meanwhile, the ensemble may select any one server as a leader through a selection algorithm. Accordingly, the ensemble consists of a leader and a follower that is a set of servers excluding the leader. If the request from the clients 10a to 10j fails, a new leader may be elected through agreement of followers.

The coordination service described above is provided by the coordinator system 30. The coordinator system 30 serves to coordinate the distributed brokers 20 according to the work request from the clients 10a to 10j. Here, the coordinator may mean mapping the distributed brokers 20 to the clients 10a to 10j appropriately. In addition, if a problem occurs in the coordination service provided by the coordinator system 30, it may cause a failure of the entire system, so the coordinator system 30 uses a layered data model and leads the leaders of the distributed brokers 20. Election prevents the entire system from failing. The detailed description of the coordinator system 30 will be described later.

2 is a block diagram of a distributed broker system according to an embodiment of the present invention.

2, the distributed broker system 1 according to an embodiment of the present invention includes a distributed broker 20 and a coordinator system 30.

The distribution broker 20 serves as an intermediary so that messages can be exchanged between clients 10a and 10b in a publish/subscribe manner, and in particular, in the case of the present invention, the coordinator system 30 for load balancing A plurality of distributed brokers 20 are disposed between the clients 10a and 10b. The distribution broker 20 delivers a message to the subscribing clients 10a and 10b subscribing to the designated topic when any client 10a or 10b issues a message for a specific topic.

To this end, the distributed broker 20 publishes/subscribes tables including publish/subscribe information between clients 10a and 10b, and publishes a topic routing table containing information about subscribed topics. /Subscription module 210 may be included. The publish/subscribe module 210 stores data for clients 10a and 10b who subscribe to each topic in the publish/subscribe table and topic routing table and topic data for routing, and uses the publish/subscribe model Perform message routing according to.

Here, the distribution broker 20 may include a bridging manager module 230. The bridging manager module 230 connects the distributed broker 20 with the coordinator server 310 to exchange data. That is, data stored in the publish/subscribe table 210 and the topic routing table of the publish/subscribe module 210 is transmitted to the coordinator server 310 or broker mapping information is received from the coordinator server 310.

On the other hand, in the distributed broker system 1, a plurality of the above-described distributed brokers 20 are replicated and distributed in each layer and each domain in the distributed computing model. Distributed distributed distributed brokers 20 may form ensembles according to each layer and each domain, and each ensemble may include a distributed broker leader elected from among multiple distributed brokers 20 belonging to the ensemble. Can be. Through the elected distributed broker leader, clients 10a and 10b can read and write data. Since the distributed broker leader exists for each ensemble, at least one distributed broker leader may exist according to the distributed computing model. When the distributed broker reader receives a request for broker connection information from the clients (10a, 10b), the distributed broker (20) located closest to the clients (10a, 10b) in the broker group containing the distributed broker leader is the optimal distributed broker. Elected, broker connection information including information on the optimal distributed broker 20 may be transmitted to the clients 10a and 10b.

The coordinator system 30 serves to coordinate the distributed brokers 20 according to the work request from the clients 10a and 10b as described above, and includes a coordinator server 310 and a processing server 330 for this purpose. do.

The coordinator server 310 receives the broker mapping information request from the clients 10a and 10b, and allocates a broker mapping job to the processing server 330 according to the broker mapping information request. In addition, the broker mapping information including information on the optimal distributed broker leader selected according to the broker mapping operation is transmitted to the clients 10a and 10b.

The coordinator server 310 may operate based on a layered data model having a directory format. The advantage of using a directory format is that it is easy to store data in a hierarchical structure. The layered data model may be, for example, a tree-structured node.

Referring to FIG. 3, which shows an example of a layered data model of the coordinator system 30, the coordinator server 310 stores data in each node according to a directory (/) format and reads data stored in each node. Or write function. For example, data of clients 10a and 10b are stored in the Participants node, data of the processing server 330 is stored in the ProcessingServers node, and data of distributed brokers 20 are stored in the Fog_Domain or Cloud_Domain nodes. In addition, topic data stored in each of the distributed brokers 20 may be stored in the Topics node to coordinate the distributed brokers 20.

The processing server 330 receives the broker mapping job from the coordinator server 310 at the request of the clients 10a and 10b, and then selects the optimal distributed broker leader from among a plurality of distributed broker leaders to the clients 10a and 10b. Map. Here, the optimal distributed broker leader may mean a distributed broker leader located closest to clients 10a and 10b that request broker mapping information among a plurality of distributed broker leaders.

According to an embodiment, the coordinator system 30 may include a plurality of processing servers 330. In this case, any one of the plurality of processing servers 330, the processing server 330 is elected as a leader and serves to transfer data between the coordinator server 310 and the remaining processing servers 330. More specifically, the processing server leader delivers the tasks allocated from the coordinator server 310 to the processing server 330 in a topic format, thereby distributing the load and reducing latency.

Here, the coordinator system 30 may further include a coordination database 250 for storing a layered data model.

4 is a flowchart of a coordinator method according to an embodiment of the present invention. Hereinafter, detailed descriptions of parts overlapping with those described above will be omitted.

4, the coordinator method according to an embodiment of the present invention comprises the steps of requesting broker mapping information (S110), allocating a broker reader mapping operation (S115), and selecting an optimal distributed broker leader ( S120), transmitting broker mapping information to the client (S125), requesting broker connection information (S130), selecting an optimal distributed broker (S135), transmitting broker connection information to the client (S140) ) And an optimal distributed broker connection step (S145 ).

For distributed broker coordination, in step S110, the client requests broker mapping information from the coordinator server. At the same time as requesting the broker mapping information, the coordinator server can detect the connection of the client, create a layered data model, and register an event listener. For example, when the coordinator server operates based on the main keeper service, the layered data model may be a z node.

When the coordinator server receives the broker mapping information request, in step S115, the coordinator server allocates a broker reader mapping operation to the processing server.

On the other hand, if there are a plurality of processing servers according to an embodiment, and there is a processing server leader elected to perform a role of transferring data between the coordinator server and the remaining processing servers among the processing servers, step S115 is the processing server leader. Can be performed against. That is, the coordinator server allocates the broker leader mapping job to the processing server leader.

In step S120, the processing server assigned to the broker leader mapping operation performs broker leader mapping to select the optimal distributed broker leader.

On the other hand, if the processing server leader is assigned a broker leader mapping job according to an embodiment, the processing server leader delivers the job allocated from the coordinator server to a processing server in one of a plurality of processing servers in a topic format (S121). Step) may be further included. Accordingly, the processing server receiving the job from the processing server leader selects the optimal distributed broker leader (step S122).

In step S125, the processing server transmits broker mapping information including information about the optimal distributed broker leader selected through step S120 to the client.

The client that receives the broker mapping information requests broker connection information to the optimal distributed broker reader according to the broker mapping information through step S130.

In step S135, the optimal distributed broker leader receiving the broker connection information from the client selects the optimal distributed broker from the broker group including the optimal distributed broker leader according to the broker connection information. Here, the optimal distributed broker may mean a distributed broker located closest to a client in a broker group including the optimal distributed broker leader.

The optimal distributed broker reader transmits broker connection information including information about the selected optimal distributed broker to the client (step S140), and the client connects to the optimal distributed broker according to the received broker connection information (S145) step).

Once connected to the optimal distributed broker, the client can deliver the message through the connected distributed broker. For example, when a client sends a message to a broker, the optimal distributed broker connected to the client receives a message for a specific topic from a Pub client, and sends the message to a Sub client that subscribes to the specific topic. I can send it.

Optimal dispersion Request a connection to the broker On failure

5 is a flowchart of a coordinator method when a connection request to a distributed broker fails.

Referring to FIG. 5, when the client's connection request to the optimal distributed broker selected according to the above-described distributed broker coordinator method fails, steps S145 to S165 are included to connect another distributed broker to the client.

In step S145, an optimal distributed broker connection is attempted. In step S150, it is determined whether to connect. If it is determined that the connection has failed, in step S155, the client re-requests broker connection information to the optimal distributed broker reader.

In step S160, the optimum distributed broker leader that has received the re-request is re-established among the remaining distributed brokers except the optimal distributed broker whose connection request has failed in the broker group including the optimal distributed broker leader according to the broker connection information re-request. Re-elects the best distributed broker at times, and sends broker connection information including information on the re-elected optimal distributed broker to the client.

Finally, in step S165, the client is connected to the optimal distributed broker that has been re-elected. Therefore, in the present invention, even if the connection request fails, there is an advantage in that data loss can be eliminated through the coordinator and fail over/fail back is possible.

The device described above may be implemented with hardware components, software components, and/or combinations of hardware components and software components. For example, the devices and components described in the embodiments include, for example, processors, controllers, arithmetic logic units (ALUs), digital signal processors (micro signal processors), microcomputers, field programmable arrays (FPAs), It may be implemented using one or more general purpose computers or special purpose computers, such as a programmable logic unit (PLU), microprocessor, or any other device capable of executing and responding to instructions. The processing device may run an operating system (OS) and one or more software applications running on the operating system. In addition, the processing device may access, store, manipulate, process, and generate data in response to the execution of the software. For convenience of understanding, a processing device may be described as one being used, but a person having ordinary skill in the art, the processing device may include a plurality of processing elements and/or a plurality of types of processing elements. It can be seen that may include. For example, the processing device may include a plurality of processors or a processor and a controller. In addition, other processing configurations, such as parallel processors, are possible.

The software may include a computer program, code, instruction, or a combination of one or more of these, and configure the processing device to operate as desired, or process independently or collectively You can command the device. Software and/or data may be interpreted by a processing device, or to provide instructions or data to a processing device, of any type of machine, component, physical device, virtual equipment, computer storage medium or device. , Or may be permanently or temporarily embodied in the transmitted signal wave. The software may be distributed over networked computer systems and stored or executed in a distributed manner. Software and data may be stored in one or more computer-readable recording media.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, or the like alone or in combination. The program instructions recorded in the medium may be specially designed and configured for the embodiments or may be known and usable by those skilled in computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs, DVDs, and magnetic media such as floptical disks. -Hardware devices specifically configured to store and execute program instructions such as magneto-optical media, and ROM, RAM, flash memory, and the like. Examples of program instructions include high-level language code that can be executed by a computer using an interpreter, etc., as well as machine language codes produced by a compiler. The hardware device described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

Although the embodiments have been described by the limited drawings as described above, a person skilled in the art can make various modifications and variations from the above description. For example, the described techniques are performed in a different order than the described method, and/or the components of the described system, structure, device, circuit, etc. are combined or combined in a different form from the described method, or other components Alternatively, even if replaced or substituted by equivalents, appropriate results can be achieved.

Therefore, other implementations, other embodiments, and equivalents to the claims are also within the scope of the following claims.

1: distributed broker system
10: client
20: distributed broker
210: publish/subscribe module 230: bridging manager module
30: coordinator system
310: coordinator server 330: processing server
350: Coordination database

Claims (14)

A coordinator server server that receives a broker mapping information request from a client and allocates a broker mapping operation according to the broker mapping information request; And
Selecting the best distributed broker leader among a plurality of distributed broker leaders-one distributed broker leader selected from a plurality of distributed brokers-by assigning a broker mapping task from the coordinator server to map to the client A coordinator system comprising a processing server.
According to claim 1,
The processing server is a coordinator system that selects a distributed broker leader closest to the client from among the plurality of distributed broker leaders as the optimal distributed broker leader.
delete According to claim 1,
The coordinator server transmits broker mapping information including information about the optimal distributed broker reader to the client.
According to claim 1,
The distributed broker
A publish/subscribe module including a publish/subscribe table including publish/subscribe (Pub/Sub) information between the clients and a topic routing table containing information on topics subscribed to by the client; And
And a bridging manager module that connects the coordinator server and the distributed broker to exchange data.
According to claim 1,
A coordinator system further comprising a processing server reader that delivers the tasks assigned from the coordinator server to the processing server in a topic format.
According to claim 1,
The optimal distributed broker leader receives a first broker connection information request from the client, and a distribution that is closest to the client from a plurality of distributed brokers selected by the distributed broker leader according to the first broker connection information request A coordinator system that elects a first optimal distributed broker that is a broker, and transmits first broker connection information including information about the first optimal distributed broker to the client.
The method of claim 7,
When the client's connection request to the first optimal distributed broker fails, the optimal distributed broker reader receives a second broker connection information request from the client, and requests the second broker connection information request. Accordingly, among a plurality of distributed brokers from which a distributed broker leader has been elected, a second optimal distributed broker, which is a distributed broker closest to the client, is selected from among the remaining distributed brokers except for the first optimal distributed broker whose connection request has failed. And a second broker connection information including information on the second optimal distributed broker to the client.
A coordinator method performed by a coordinator system,
A client requesting broker mapping information from a coordinator server;
The coordinator server assigning a broker leader mapping job to a processing server;
The processing server is assigned the broker leader mapping operation, and selects the optimal distributed broker leader among a plurality of distributed broker leaders-any one distributed broker leader selected from among multiple distributed brokers, and the optimal Transmitting broker mapping information including information on a distributed broker reader to the client;
Requesting, by the client, first broker connection information from the optimal distributed broker reader;
The optimal distributed broker leader selects the first optimal distributed broker from a plurality of distributed brokers selected by the distributed broker leader according to the first broker connection information request, and includes information about the first optimal distributed broker Transmitting the first broker connection information to the client; And
And the client connecting to the first optimal distributed broker.
The method of claim 9,
When the connection request to the first optimal distributed broker fails in the step of connecting to the first optimal distributed broker,
Requesting, by the client, second broker connection information from the optimal distributed broker reader;
The optimal distributed broker leader is the second optimal among the remaining distributed brokers except for the first optimal distributed broker in which the connection request has failed in a plurality of distributed brokers from which the distributed broker leader has been elected according to the second broker connection information request. Selecting a distributed broker, and transmitting second broker connection information including information about the second optimal distributed broker to the client; And
And the client connecting to the second optimal distributed broker.
The method of claim 9,
The step of allocating the broker leader mapping operation is to include the broker in the processing server leader when there is a processing server leader elected to serve to transfer data between the coordinator server and the remaining processing servers among a plurality of processing servers. Coordinator method to assign leader mapping tasks.
The method of claim 11,
The step of allocating the broker leader mapping operation is
And transmitting, by the processing server leader, a task allocated from the coordinator server to a processing server of any one of the plurality of processing servers in a topic format.
The method of claim 9,
Receiving, by the first optimal distribution broker, a message for a specific topic from a publishing client; And
And sending the message to a subscription client subscribing to the specific topic.
The method of claim 9,
The optimal distributed broker leader is a distributed broker located closest to the client among the plurality of distributed broker leaders,
The first optimal distributed broker is a distributed broker closest to the client in a broker group including the optimal distributed broker leader.

Images