KR102033500B1 - Packing Routing method by Edge Cloud in Distributed Cloud System - Google Patents

Abstract

In the distributed cloud system according to the present invention, an edge cloud includes a packet sniffer that receives a publish message from a sending client and performs packet sniffing on the publish message. ; A packet analyzer for determining whether to perform a service requested by the publish message and a type of a topic of the requested service based on the sniffed packet; And a service router configured to perform different routing of the packet based on whether the service can be performed and the type of the topic, so that unnecessary network delay time due to geographical distance between a client and a server is reduced. Problems that occur can be solved.

Description

Packet routing method by edge cloud in distributed cloud system

The present invention relates to a packet routing method by an edge cloud in a distributed cloud system. More specifically, it relates to a distributed publish / subscribe model and method for fast response time.

The Publish / Subscribe (Pub / Sub) model is a technology that enables N: N communication, rather than 1: 1 communication, like the existing communication environment. Since there is a message broker that brokers messages, clients can connect only to the broker and send and receive messages even if they do not know each other's information.

However, in the existing messaging service, a message request from a client performs communication between users through a central cloud server through a wireless access point (AP), a base station, or the like. This causes a problem that causes non-deterministic network latency of the packet network path according to the geographical distance between the client and the server.

Therefore, the present invention is to solve the above-described problem, it is an object of the present invention to solve the response time delay problem occurring in the existing Pub / Sub model through the distributed Pub / Sub model.

In addition, another object of the present invention is to solve the unnecessary network delay caused by the geographical distance between the client and the server.

In the distributed cloud system according to the present invention for solving the above-mentioned problem, an edge cloud receives a publish message from a sending client and performs packet sniffing on the publish message. A packet sniffer; A packet analyzer for determining whether to perform a service requested by the publish message and a type of a topic of the requested service based on the sniffed packet; And a service router configured to perform different routing of the packet based on whether the service can be performed and the type of the topic, so that unnecessary network delay time due to geographical distance between a client and a server is reduced. Problems that occur can be solved.

 In one embodiment, if the packet analyzer determines that the same service as the requested service cannot be provided in the edge cloud, the packet is not accessible to the core cloud and the packet is accessible to the sending client terminal. Control to be routed to a second edge cloud within an adjacent region. In addition, if it is determined that the same service as the requested service may be provided in the edge cloud, the packet analyzer may further determine whether the topic of the service is a global topic or an edge topic.

In one embodiment, if the topic of the service is the global topic, the service router sends the packet to the global client node through the core cloud, and if the topic of the service is the edge topic, the service router sends the packet. It may be characterized by transmitting to the edge client node.

In one embodiment, if the packet analyzer determines that the topic of the service is the edge topic, the service router may forward the packet to a messaging service module so that the messaging service module performs a messaging service.

In one embodiment, the packet sniffer identifies a destination IP, port, and service ID in the packet, and the packet analyzer identifies the identified destination IP, port, and service ID in the service table of the edge cloud. In comparison with the edge service ID, it may be determined whether the requested service can be performed.

In an embodiment, the edge client node may be determined by a type of service subscribed to by the user of the edge client node, an authority granted by the transmitting client, and an authority granted by the edge cloud.

In an embodiment, when a service subscribed to by a user of the edge client node is a service of a higher grade than a general service, and the user is authorized to use an edge cloud service for specific content classified by the sending client, The specific content may be delivered to the edge client node through the edge cloud without passing through the core cloud.

In a distributed cloud system according to another aspect of the present invention, a packet routing method using an edge cloud includes receiving a publish message from a sending client to perform packet sniffing on the publish message. A packet sniffing process to perform; A packet analysis process of determining whether a service requested by the publish message and a type of a topic of the requested service are determined based on the sniffed packet; And a service router process for performing different routing for the packet based on whether the service can be performed and the type of the topic.

In one embodiment, in the packet analysis process, if it is determined that the same service as the requested service cannot be provided in the edge cloud, the packet is accessed by the transmitting client terminal without routing the packet to the core cloud. Can be controlled and routed to a second edge cloud within an adjacent area. In addition, if it is determined that the same service as the requested service can be provided in the edge cloud, the packet analysis process may further determine whether the topic of the service is a global topic or an edge topic.

In one embodiment, if the topic of the service is the global topic, the service router sends the packet to the global client node through the core cloud, and if the topic of the service is the edge topic, the service router sends the packet. It may be characterized by transmitting to the edge client node.

According to an embodiment of the present disclosure, if the topic of the service is determined as the edge topic in the packet analysis process, the service router may further include a messaging service process of performing a messaging service for the packet.

In one embodiment, in the packet sniffing process, a destination IP, a port, and a service ID are identified in the packet, and in the packet analysis process, the identified destination IP, port, and service ID are included in the service table of the edge cloud. It is possible to determine whether the requested service can be performed by comparing with the IP, port, edge service ID of the.

In a distributed cloud system according to another aspect of the present invention, a packet routing method using a core cloud includes a first type of packet from an edge cloud that receives a publish message from a sending client. A first packet processing procedure for receiving and processing a request, wherein the service requested by the publish message is not executable by the edge cloud; A second packet processing procedure for receiving and processing a second type of packet from the edge client—the service requested by the publish message may be performed by the edge cloud, but the topic of the requested service is global Is a topic; And a service routing process of performing different routing on the first type of packet and the second type of packet.

In one embodiment, if the topic of the requested service for the first type of packet is the global topic, in the service routing process, the packet of the first type is sent to a global client node and the If the topic is the edge topic, the first type of packet may be transmitted to an edge client node.

In an embodiment, for the second type of packet, in the service routing process, the second type of packet may be transmitted to the global client node.

In one embodiment, for the first type of packet and the second type of packet, if the topic of the service is the edge topic, perform a messaging service for the first type of packet and the second type of packet. It may further include a messaging service process.

In one embodiment, if the sending client node is adjacent to a second edge cloud and the second edge cloud can perform the service requested by the publish message, then the sending client node causes a subsequent second publish. The time message may be controlled to be transmitted to the second edge cloud.

According to another aspect of the present invention, a distributed cloud system receives a publish message from a sending client, performs packet sniffing on the publish message, and based on the sniffed packet, An edge cloud that determines whether a service requested by the publish message can be performed and a type of a topic of the requested service; And a core cloud that receives the packet from the edge cloud if the packet analyzer determines that the same service as the requested service cannot be provided in the edge cloud.

In one embodiment, if it is determined that the same service as the requested service can be provided in the edge cloud, the edge cloud further determines whether the topic of the service is a global topic or an edge topic, and the topic of the service is The edge cloud transmits the packet to a global client node through the core cloud if the global topic is the global topic, and the edge cloud transmits the packet to an edge client node if the topic of the service is the edge topic. can do.

In one embodiment, if the topic of the service is determined to be the edge topic, the edge cloud forwards the packet to a first messaging service module in the edge cloud to allow the first messaging service module to perform a messaging service, If the topic of the service is determined to be the global topic, the core cloud may forward the packet to a second messaging service module in the core cloud to allow the second messaging service module to perform a messaging service.

Distributed cloud system according to the present invention, there is an advantage that can solve the problem of unnecessary network delay caused by the geographical distance between the client and the server due to the messaging system provided in the existing central cloud server.

In addition, the distributed cloud system according to the present invention has the advantage that it is possible to provide a faster messaging service between clients by placing a messaging service in the edge cloud environment, such as wireless AP, base station.

In addition, the distributed cloud system according to the present invention has an advantage that the real-time performance of the messaging service can be further improved because the messaging is performed in a location close to the client.

1 illustrates a conventional Pub / Sub model and a Pub / Sub model according to the present invention.
2 shows a conceptual diagram of a distributed Pub / Sub model according to the present invention.
3 is a detailed block diagram of a distributed cloud system including an edge cloud and a core cloud in a distributed cloud system according to the present invention.
4 is a conceptual diagram illustrating a packet routing method by an edge cloud in a service distributed cloud system according to the present invention.
5 is a conceptual diagram of service mapping between a core cloud and an edge cloud using a service table according to the present invention.
6 shows a packet routing method and a flowchart according to the distributed cloud system according to the present invention.
7 shows a flowchart of a packet routing method by a core cloud according to another aspect of the present invention.

The above-described features and effects of the present invention will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, and thus, those skilled in the art to which the present invention pertains may easily implement the technical idea of the present invention. Could be. As the inventive concept allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the text. However, this is not intended to limit the present invention to a specific disclosure, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.

In describing each drawing, like reference numerals are used for like elements.

Terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.

For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component. The term “and / or” includes any combination of a plurality of related items or any item of a plurality of related items.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art.

Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art, and are not construed in ideal or excessively formal meanings unless expressly defined in this application. Should not.

The suffixes "module", "block", and "unit" for components used in the following description are given or mixed in consideration of ease of specification, and do not have distinct meanings or roles by themselves. .

Hereinafter, with reference to the accompanying drawings, preferred embodiments of the present invention will be described to be easily carried out by those of ordinary skill in the art. In the following description of the embodiments of the present invention, when it is determined that the detailed description of the related known functions or known configurations may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

Hereinafter, a packet routing method by an edge cloud and / or a core cloud and an edge cloud and / or a core cloud in a distributed cloud system according to the present invention will be described. In this regard, Figure 1 shows a conventional Pub / Sub model and Pub / Sub model according to the present invention. In Fig. 1, the above figure shows the existing Pub / Sub model and the figure below shows the proposed Pub / Sub model. As shown in FIG. 1, the distributed cloud system 1000 includes a client 100, a core cloud 200, and an edge cloud 300. Meanwhile, the client 100 includes a publisher corresponding to the transmitting client (terminal) 110 and a subscriber corresponding to the receiving client (terminal) 120.

As shown in FIG. 1, in the proposed model, the edge cloud adds a computing environment to a network node between a client and a cloud server, thereby providing the same messaging services provided by the existing cloud in the edge cloud. can do.

On the other hand, the existing Pub / Sub model uses a messaging service of a central cloud server to exchange messages between clients. Typically, message packets sent by a publisher go through a number of network nodes before reaching the cloud server. In this case, a non-deterministic network delay occurs due to a routing scheme for transmitting packets between network nodes.

On the other hand, in the Pub / Sub model proposed in the present invention, the wireless AP, the base station, and the like, which are located close to the user, become the edge cloud and provide the same messaging service that is provided in the existing cloud environment. This reduces unnecessary network movements and provides users with faster response time messaging services. A conceptual diagram of a distributed Pub / Sub model, which is a method for enabling this, is described in detail below.

-Distributed Pub / Sub Model Concept

In this regard, Figure 2 shows a conceptual diagram of a distributed Pub / Sub model according to the present invention. That is, the distributed Pub / Sub model is configured in a distributed cloud environment as shown in FIG. The publisher 110 delivers the message packet to the core cloud to deliver the message. In the edge cloud 300, which is an intermediate stage of a network node in which a packet is delivered, SA (Service Awareness) performs sniffing and analysis of packets to determine whether the packet is a packet for using a messaging service. . If it is confirmed as a messaging packet, the packet is delivered to a messaging service in the edge cloud 300 to provide a messaging service. If it is not a messaging packet, the cloud service is performed by delivering the packet to the core cloud 200 as using an existing cloud service.

In order to perform messaging in the above-mentioned edge cloud 300, a messaging topic is divided into two layers. Meanwhile, an edge topic for providing a client-to-client messaging service connected to the same edge cloud 300, that is, a messaging service to the edge client node 120a, and a global network for performing messaging with another edge cloud 120b. It is divided into topics (Global Topic). This allows the service provider to selectively provide services to clients in accordance with local messaging service offerings, or full messaging service offerings.

Hereinafter, a distributed cloud system including an edge cloud and a core cloud in the distributed cloud system according to the present invention will be described in detail. In this regard, Figure 3 shows a detailed block diagram of a distributed cloud system including an edge cloud, a core cloud in a distributed cloud system according to the present invention.

3 shows a detailed block diagram of a distributed cloud system according to a distributed Pub / Sub structure. As shown in FIG. 3, the distributed cloud system 1000 includes a client 100, a core cloud 200, and an edge cloud 300.

The core cloud 200 may include a service image manager 210 for managing an image of a messaging service, a service deployer 220 for distributing a messaging service, and a synchronizer for synchronizing information between clouds ( Synchronizer, 230). Here, the synchronization of information between clouds may be synchronization of information of clients between clouds. In addition, the core cloud 200 may further include a resource manager 240 that manages the resource state of the edge cloud 300.

The edge cloud 300 includes a service awareness module 300a and a messaging service module 300b. The service recognition module 300a may include a packet sniffer 310 for detecting a packet of a client, a packet analyzer 320 for analyzing a request packet of a client, and a service for performing a response of the requested packet. A service table manager (330) for determining whether or not, and a service router (340) for inducing packet processing to the response service to the requested packet. In addition, the messaging service module 300b includes a messaging broker 350 and a client manager 360.

Specifically, the detailed components of the edge cloud 300 in the distributed cloud system 1000 will be described in detail as follows. The packet sniffer 310 is configured to receive a publish message from a sending client and perform packet sniffing on the publish message. In addition, the packet analyzer 320 is configured to determine whether to perform the service requested by the publish message and the type of the topic of the requested service, based on the sniffed packet. In addition, the service router 330 is configured to perform different routing for the packet based on whether the service can be performed and the type of the topic.

In this case, the packet routing method may be performed as follows according to whether the edge cloud 300 provides a service and a topic type. If the packet analyzer 320 determines that the same service as the requested service cannot be provided in the edge cloud 300, the service router 340 transmits the packet to the core cloud 200. Alternatively, the edge cloud 300 does not route the packet to the core cloud, but controls the packet to be routed to a second edge cloud (not shown) accessible by the transmitting client terminal 100 and within an adjacent area. You may.

On the other hand, if it is determined that the same service as the requested service can be provided in the edge cloud 300, the packet analyzer 320 may further determine whether the topic of the service is a global topic or an edge topic. .

In this regard, if the topic of the service is the global topic, the service router 320 transmits the packet to the global client node through the core cloud 200. On the other hand, if the topic of the service is the edge topic, the service router 240 transmits the packet to the edge client node without passing through the core cloud 200. In this case, when the packet analyzer 320 determines that the topic of the service is the edge topic, the service router 340 forwards the packet to the messaging service module 300b so that the messaging service module 300b receives the messaging service. Can be done.

On the other hand, each module described above may perform faster service response by directly processing in the edge cloud 300, without passing the request packet of the client to the core cloud 200 through interaction with each other.

On the other hand, Figure 4 shows a conceptual diagram of a packet routing method by the edge cloud in a service distributed cloud system according to the present invention.

-Service Awareness

In this regard, a service awareness method for quickly processing a client's service request in an edge cloud is illustrated in FIG. 4. That is, it may be assumed that a publisher and a subscriber exchange messages in the same edge cloud 300. The publisher publishes the message to the core cloud 200 as a method of using an existing messaging service.

In detail, the edge cloud 300 receives a publish message from the transmitting client 110 and performs packet sniffing on the publish message. In addition, the edge cloud 300 determines whether the service requested by the publish message can be performed and the type of the topic of the requested service, based on the sniffed packet.

Meanwhile, if the packet analyzer 310 determines that the same service as the requested service cannot be provided in the edge cloud 300, the core cloud 200 receives the packet from the edge cloud 300.

Meanwhile, if it is determined that the same service as the requested service can be provided in the edge cloud 300, the edge cloud 300 may further determine whether the topic of the service is a global topic or an edge topic. In this case, if the topic of the service is the global topic, the edge cloud 300 transmits the packet to the global client node through the core cloud 200. On the other hand, if the topic of the service is the edge topic, the edge cloud 300 sends the packet to an edge client node.

Meanwhile, when the topic of the service is determined as the edge topic, the edge cloud 300 delivers the packet to the first messaging service module in the edge cloud 300 so that the first messaging service module performs a messaging service. You can do that. On the other hand, if the topic of the service is determined to be the global topic, the core cloud 200 delivers the packet to a second messaging service module in the core cloud 200 so that the second messaging service module provides a messaging service. Can be done.

 Meanwhile, referring to the service table in FIG. 3, the service table manager 330 will be described in detail as to how to perform service recognition. In this regard, Figure 5 shows a conceptual diagram of the service mapping between the core cloud and the edge cloud using the service table according to the present invention. Meanwhile, the service sniffing and routing process through packet sniffing and packet analysis will be described in detail with reference to FIGS. 3 to 5 as follows.

1) First, the service recognition module 300a of the edge cloud 300 performs packet sniffing to catch information about packets passing through the edge cloud 300. In this regard, the packet sniffer 310 identifies (identifies) the destination IP, port, and service ID in the request packet of the transmitting client terminal 110.

2) Next, the packet analyzer 320 compares the identified destination IP, port, and service ID with the IP, port, and edge service ID of the service table of the edge cloud 300 to perform the requested service. Determine if it is possible. That is, in relation to the requested service, it is checked whether the same service can be provided in the edge cloud 300.

3) When the edge cloud 300 can provide the same service in step 2), the routing rule through the service router 340 to provide the messaging service to the subscriber (that is, the edge client node) immediately ( modify the routing rules. On the other hand, distinguishing whether it is a global client node or an edge client node can be distinguished by the following rules. That is, the edge client node may be determined by the type of service subscribed to by the user of the edge client node, the authority granted by the transmitting client 110, and the authority granted by the edge cloud 300. That is, when a user subscribes to an edge cloud service provider to use a premium service using an edge client, the edge cloud may be used as an edge client node using the edge cloud service. Alternatively, the edge cloud may be used according to the type of the packet and content published by the transmitting client, and the edge cloud may be used when the corresponding content is authorized. Alternatively, when the edge cloud 300 is authorized to use the edge cloud for the packet and the content, the edge cloud may be used.

In this regard, a service subscribed to by a user of the edge client node is a higher level of service than a general service, and the user is authorized to use the edge cloud service for specific content classified by the transmitting client 110. In this case, the specific content may be delivered to the edge client node through the edge cloud 300 without passing through the core cloud 200.

Meanwhile, if there is a conflict between the type of service subscribed to by the user of the above-mentioned edge client node, the authority granted by the transmitting client 110, and the authority granted by the edge cloud 300, the priority may be solved according to priority. . In other words, even if the subscriber subscribes to the core cloud service and the content published by the publisher grants the right to use the core cloud service, the edge cloud may not be authorized and thus the core cloud may not be used. For example, in the case of congestion due to processing packets for a plurality of client terminals in the current core cloud, the service for other publishers / subscribers may be temporarily delayed.

4) On the other hand, if the same service does not exist in the edge cloud 300, it performs a messaging service by delivering a packet to the core cloud 200 as using an existing messaging service.

In the above, each block in the distributed cloud system has been described in detail. Hereinafter, a method of packet routing for each component in the distributed cloud system and a signaling flow thereof will be described. On the other hand, the content described in the above-described distributed cloud system and the content to be described in the following packet routing method may be used in combination with each other.

In this regard, Figure 6 shows a packet routing method and a flowchart according to the distributed cloud system according to the present invention. Meanwhile, in the existing Pub / Sub model, it was simply operated by publishing and subscribing to the messaging service of the core cloud. The proposed distributed Pub / Sub model can provide a messaging service in a location close to the user by utilizing the above-described Service Awareness method (Fig. 4). Accordingly, FIG. 6 shows a proposed packet routing method and a signal flow diagram.

When a client node publishes a message, the request packet passes through an edge client that is a network node. At this time, the edge client service acknowledgment module detects information on the destination IP, port, service ID, and topic requested by the client through packet sniffing. In addition, service verification is performed to determine whether the same service as the requested service can be provided in the current edge cloud through a service table. At this time, if the same service does not exist, the packet is sent to the originally requested destination, and if the same service exists, it is determined whether the topic for which messaging is requested is a global topic or an edge topic. If it is an edge topic, the packet is delivered to the messaging service of the current edge cloud to perform the messaging service. If it is a global topic, the packet must be delivered to the core cloud because it must be provided as a messaging service of the core cloud. Through this process, the messaging request packets received from the edge cloud and the core cloud are respectively processed to deliver messaging to the global client node 120a or the edge client node 120b.

In the meantime, the above-described contents are described for each process in terms of a packet routing method using an edge cloud in a distributed cloud system. Referring to FIG. 6, the edge cloud performs a packet sniffing process S100, a packet analysis process S200, and a service router process S300.

In the packet sniffing process (S100), a publish message is received from a transmitting client to perform packet sniffing on the publish message. In addition, in the packet analysis process (S200), based on the sniffed packet, it is determined whether the service requested by the publish message can be performed and the type of topic of the requested service. In addition, in the service router process (S300), based on whether the service can be performed and the type of the topic, different routing for the packet is performed.

On the other hand, if it is determined in the packet analysis process (S200) that the same service as the requested service cannot be provided in the edge cloud, the packet is transmitted to the core cloud. In this case, the edge cloud may not provide the service, but it may be determined that the edge cloud may be provided by a second edge cloud which is another edge cloud. In such a case, the edge cloud may control the packet to be routed to the second edge cloud that is accessible to the sending client and is within an adjacent area without routing the packet to the core cloud. Specifically, the edge cloud may control the routing of the packet directly to the second edge cloud or the transmitting client terminal to transmit the packet or a subsequent packet to the second edge cloud.

On the other hand, if it is determined that the same service as the requested service can be provided in the edge cloud, the packet analysis process (S200) further determines whether the topic of the service is a global topic or an edge topic.

On the other hand, if the topic of the service is the global topic, the service router transmits the packet to the global client node through the core cloud. On the other hand, if the topic of the service is the edge topic, the service router sends the packet to an edge client node.

On the other hand, if the topic of the service is determined as the edge topic in the packet analysis process (S200), the service router process may further include a messaging service process (S250) for performing a messaging service for the packet.

Meanwhile, in the packet sniffing process (S100), a destination IP, a port, and a service ID are identified in the packet, and in the packet analyzing process (S200), the identified destination IP, port, and service ID are stored in the edge cloud. It is possible to determine whether the requested service can be performed by comparing the IP, port, and edge service ID of the service table of the UE.

Meanwhile, a packet routing method by the core cloud according to another aspect of the present invention will be described in detail as follows. In this regard, FIG. 7 shows a flowchart of a packet routing method by a core cloud according to another aspect of the present invention. Referring to FIG. 7, the packet routing method using the core cloud includes a first packet processing S100 ′, a second packet processing S200 ′, and a service routing process S300 ′.

In a first packet processing process S100 ′, a first type of packet is received and processed from an edge cloud that receives a publish message from a transmitting client. In this case, for the first type of packet, the service requested by the publish message is not routable by the edge cloud. Further, in the second packet processing process S200 ′, a second type of packet is received from the edge client and processed. In this case, for the second type of packet, the service requested by the publish message is routable by the edge cloud, but the topic of the requested service is a global topic. Further, in the service routing process S300 ′, different routings for the first type of packet and the second type of packet may be performed.

On the other hand, if the topic of the requested service for the packet of the first type is the global topic, in the service routing process (S300 ′), the packet of the first type may be transmitted to a global client node. On the other hand, if the topic of the requested service is the edge topic, the first type of packet may be sent to an edge client node.

On the other hand, for the second type of packet, in the service routing process (S300 '), the second type of packet is transmitted to the global client node.

On the other hand, for the first type of packet and the second type of packet, a messaging service that performs a messaging service for the first type of packet and the second type of packet if the topic of the service is the global topic. The method may further include a step S250 ′. Meanwhile, in the core cloud, if the transmitting client node is adjacent to a second edge cloud, and the second edge cloud can perform the service requested by the publish message. Control the sending client node to send a subsequent second publish message to the second edge cloud. In other words, if the edge cloud cannot handle the service, but it is determined that another adjacent edge cloud can handle the service, the core cloud may instruct the core cloud to modify the routing for subsequent packets.

The distributed cloud system according to at least one embodiment of the present invention described above may be utilized for disaster situation propagation requiring real time messaging. It can also be used in AR / VR (Augmented Reality / Virtual Reality) fields where fast response time must be guaranteed.

On the other hand, the expected effect of the distributed cloud system according to at least one embodiment of the present invention can contribute to safety by providing a message to people with low delay time in the field of disaster safety where real-time situation propagation, such as earthquake, tsunami, language is important.

On the other hand, the distributed cloud system according to at least one embodiment of the present invention in the field of applying a distributed cloud to the wireless AP, base station, etc. by using 5G, Network Function Virtualization (NFV), Software Defined Networking (SDN) technology It is expected to be commercialized throughout the messaging area that guarantees fast response speed.

The distributed cloud system according to at least one embodiment of the present invention has the advantage that the messaging system provided by the existing central cloud server can solve the problem of unnecessary network delay caused by the geographical distance between the client and the server.

In addition, the distributed cloud system according to at least one embodiment of the present invention has an advantage of providing a faster messaging service between clients by disposing a messaging service in an edge cloud environment such as a wireless AP and a base station.

In addition, the distributed cloud system according to at least one embodiment of the present invention has an advantage that the real-time performance of the messaging service can be further improved since the messaging is performed at a location close to the client.

According to the software implementation, each component as well as the procedures and functions described herein may be implemented as separate software modules. Each of the software modules may perform one or more functions and operations described herein. Software code may be implemented in software applications written in a suitable programming language. The software code may be stored in a memory and executed by a controller or a processor.

Claims (20)

In the edge cloud in a distributed cloud system,
A packet sniffer for receiving a publish message from a sending client and performing packet sniffing on the publish message;
A packet analyzer that determines, based on the sniffed packet, whether a service requested by the publish message can be performed and a type of a topic of the requested service; And
A service router configured to perform different routing for the packet based on whether the service can be performed and the type of the topic;
If the packet analyzer determines that the same service as the requested service cannot be provided in the edge cloud, the packet is not routed to the core cloud connected with the edge cloud, and the packet is accessible to the transmitting client terminal and is adjacent to the packet. To route to a second edge cloud within the zone,
If it is determined that the same service as the requested service can be provided by the edge cloud, the packet analyzer further determines whether the topic of the service is a global topic or an edge topic. delete According to claim 1,
If the topic of the service is the global topic, the service router sends the packet to the global client node through the core cloud,
If the topic of the service is the edge topic, the service router sends the packet to an edge client node. According to claim 1,
If the packet analyzer determines that the topic of the service is the edge topic, the service router forwards the packet to a messaging service module to cause the messaging service module to perform a messaging service. According to claim 1,
The packet sniffer identifies a destination IP, port, and service ID in the packet, and the packet analyzer compares the identified destination IP, port, and service ID with the IP, port, edge service ID of the service table of the edge cloud. By comparison, determining whether the requested service is feasible. The method of claim 3, wherein
And wherein the edge client node is determined by the type of service subscribed to by the user of the edge client node, the rights granted by the sending client, and the rights granted by the edge cloud. The method of claim 6,
When the service subscribed to by the user of the edge client node is a service of a higher grade than a general service, and the user authorizes the user to use the edge cloud service for the specific content classified by the sending client, the specific content is determined as the service. An edge cloud, characterized in that delivered to the edge client node through the edge cloud without passing through a core cloud. In the packet routing method by the edge cloud in a distributed cloud system,
A packet sniffing process of receiving a publish message from a sending client and performing packet sniffing on the publish message;
A packet analysis process of determining whether a service requested by the publish message can be performed and a type of a topic of the requested service based on the sniffed packet; And
And a service router process of performing different routing for the packet based on whether the service can be performed and the type of the topic.
In the packet analysis process, if it is determined that the same service as the requested service cannot be provided in the edge cloud, the packet is accessible to the transmitting client terminal without routing the packet to a core cloud connected to the edge cloud. And routed to a second edge cloud in an adjacent area,
If it is determined that the same service as the requested service can be provided in the edge cloud, it is further determined whether the topic of the service is a global topic or an edge topic in the packet analysis process. delete The method of claim 8,
If the topic of the service is the global topic, the service router sends the packet to the global client node through the core cloud,
If the topic of the service is the edge topic, then the service router sends the packet to an edge client node. The method of claim 8,
If it is determined that the topic of the service is the edge topic in the packet analysis process, further comprising a messaging service process for performing a messaging service for the packet in the service router process. The method of claim 8,
In the packet sniffing process, a destination IP, a port, and a service ID are identified in the packet, and in the packet analysis process, the identified destination IP, port, and service ID are determined as IP, port, And comparing the edge service ID to determine whether the requested service can be performed. In the packet routing method by the core cloud in a distributed cloud system,
A first packet processing procedure for receiving and processing a first type of packet from an edge cloud that receives a publish message from a sending client, wherein the service requested by the publish message is sent to the edge cloud; Not routable by ―;
A second packet processing procedure for receiving and processing a second type of packet from the edge cloud—the service requested by the publish message is routable by the edge cloud, but the topic of the requested service is global Is a topic; And
A service routing process of performing different routing for the first type of packet and the second type of packet,
If the topic of the requested service for the first type of packet is the global topic, then in the service routing process, the packet of the first type is sent to a global client node, and the topic of the requested service is the same edge cloud. If the topic is an edge-to-client messaging service connected to the first type of packet, then the first type of packet is sent to an edge client node. delete The method of claim 13,
For the second type of packet, in the service routing process, the second type of packet is transmitted to the global client node. The method of claim 13,
For the first type of packet and the second type of packet, if the topic of the service is the edge topic, performing a messaging service process for performing a messaging service for the first type of packet and the second type of packet; Further comprising a packet routing method. The method of claim 13,
If the sending client node is adjacent to a second edge cloud, and the second edge cloud can perform the service requested by the publish message, then the sending client node sends the subsequent second publish message to the second edge message. 2, characterized in that the control to transmit to the edge cloud, the packet routing method. In a distributed cloud system,
Receive a publish message from a sending client to perform packet sniffing on the publish message, and based on the sniffed packet, whether the service requested by the publish message can be performed And an edge cloud for determining the type of topic of the requested service; And
If the packet analyzer that determines the type of topic of the requested service determines that the same service as the requested service cannot be provided in the edge cloud, includes a core cloud that receives the packet from the edge cloud,
If it is determined that the same service as the requested service can be provided by the edge cloud, the edge cloud further determines whether the topic of the service is a global topic or an edge topic,
If the topic of the service is the global topic, the edge cloud sends the packet through the core cloud to a global client node,
If the topic of the service is the edge topic, the edge cloud sends the packet to an edge client node. delete The method of claim 18,
If the topic of the service is determined to be the edge topic, the edge cloud forwards the packet to a first messaging service module in the edge cloud to allow the first messaging service module to perform a messaging service,
And if the topic of the service is determined to be the global topic, then the core cloud forwards the packet to a second messaging service module in the core cloud so that the second messaging service module performs a messaging service.

Images