KR102025375B1 - Apparatus and method for data distribution service, data distribution service system - Google Patents

Abstract

The present invention relates to an apparatus and method for a data distribution service, and to a data distribution service system, the communication unit communicating with a second device in a second domain different from the first domain to which the device belongs, and at least one configuring the second domain. Assigning an internal identifier of the first domain for a second participant of, transmitting a discovery message for at least one first participant constituting the first domain to the second device, wherein the at least one first participant And a controller configured to control the communication unit to communicate with the second device in order to mediate a packet transmitted and received between the at least one second participant, wherein the discovery message is generated by the second device. An apparatus and its data used for assigning an internal identifier of the second domain for a participant It relates to a data distribution service system of method for distributed services, including such a device.

Description

Apparatus and method for data distribution service, data distribution service system}

The present invention relates to an apparatus and method for data distribution service, and a data distribution service system. More particularly, the present invention relates to an apparatus and method for data distribution service that enables a participant discovery between data distribution service devices distributed in multiple domains. A distributed service system.

Data Distribution Service (DDS) is a standard specification of middleware for data-centric publish / subscribe communication for a distributed environment, and has been standardized by an object management group (OMG). DDS is largely composed of data sharing domain, Domain and domain participant (or participant). In one domain, there are multiple publishers and subscribers for each data, and they exchange samples of a topic, which is a pre-defined data type. In DDS, data is distributed among individuals as if they were published or subscribed to a newspaper.

Such DDS middleware provides an API as a service layer existing between an application program and an operating system, and an application program can easily communicate with another entity through this. DDS middleware can be largely divided into a layer using a Data-Centric Publish-Subscribe (DCPS) layer and the Real-Time Publish Subscribe (RTPS) protocol.

The DCPS layer is a middleware interface with a specification of publish / subscribe for a distributed environment, and may provide a standardized interface to a data-driven publish-subscribe programming model for distributed environments. The layer using the RTPS protocol is a layer in which actual data is published / subscribed, and may provide a function of determining domain formation and type of data to be used, and dynamically discovering remote participants participating in the domain. On the other hand, the DCPS layer can set the QoS, in this case can perform a data communication having reliable (Reliable) or unreliable (Unreliable) according to the set QoS.

In the RTPS protocol, a search for a participant, such as Participant Discovery and a writer or reader, exists within a participant to find domain-participating entities that communicate. Perform discovery, that is, endpoint discovery.

On the other hand, if the number of DDS participants exceeds a certain size, a single domain alone cannot accommodate all DDS participants. That is, since one domain cannot provide more than a certain number of addresses, the DDS system must be composed of multiple domains. 1 is a diagram showing a general configuration of a DDS system composed of multiple domains. Referring to FIG. 1, a plurality of domains 1, 2, 3, each of which includes at least one participant 1a, 2a, 3a, is shown.

However, the conventional DDS system does not provide a means for enabling participant search for participants belonging to different domains. Therefore, there is a problem that DDS communication is not properly performed between participants distributed in multiple domains.

The present invention has been made to solve the above problems, an apparatus and method for a data distribution service, and a data distribution service system for discovering a participant distributed in different domains and performing DDS communication through a device operating as a broker. It is about.

An apparatus for data distribution service according to the present invention for solving the above-described problems, communication unit for communicating with a second device of a second domain different from the first domain to which the device belongs and at least one constituting the second domain Assign an internal identifier of the first domain for a second participant, send a discovery message for at least one first participant constituting the first domain to the second device, the at least one first participant and And a control unit for controlling the communication unit to communicate with the second device in order to mediate packets transmitted and received between the at least one second participant, wherein the discovery message is provided by the second device by the at least one first participant. It is used to assign the internal identifier of the second domain for.

The internal identifier may include at least one of an IP address and a port number corresponding to the first domain.

The controller may be further configured to allocate an internal identifier for the second device and to transmit an alive message including identification information of the device to the second device, wherein the alive message is determined by the second device. And to assign an internal identifier of the second domain for the second domain.

The apparatus may further include a storage configured to store information, and the controller may be configured to, when the response message including the identification information of the second apparatus is received from the second apparatus in response to the alive message. The identification information of the device is stored in the storage unit as mapping information in association with the assigned internal identifier.

The control unit may transmit the packet to the second device in response to the internal identifier of the packet when the at least one first participant receives a packet for an internal identifier allocated for the second participant. The second device delivers the packet to a second participant identified based on the internal identifier of the packet.

In addition, the method for the data distribution service of the device constituting the first domain according to the present invention for solving the above-described problem, the second domain of the second domain different from the first domain to configure the first domain Transmitting a discovery message for at least one first participant; if a discovery message for at least one second participant constituting the second domain is received from the second device, the discovery message for the at least one second participant Allocating an internal identifier of the first domain and communicating with the second device to mediate packets sent and received between the at least one first participant and the at least one second participant based on the internal identifier Wherein the discovery message is sent to the second device, wherein the second device is for the at least one first participant. It characterized in that is used to allocate the internal group identifier of the second domain.

The internal identifier may include at least one of an IP address and a port number corresponding to the first domain.

In addition, the method further comprises: prior to sending the discovery message, allocating an internal identifier for the second device and sending an alive message comprising identification information of the device to the second device. Wherein the alive message is sent to the second device to assign an internal identifier of the second domain for the device.

The communicating may include, if the packet for the internal identifier assigned for the second participant is received from the at least one first participant, forwarding the packet to the second device corresponding to the internal identifier of the packet. And transmitting the packet to the second participant identified based on the internal identifier of the packet.

In addition, the data distribution service system according to the present invention for solving the above problems is characterized in that it comprises a device for a data distribution service according to any one of the above.

Apparatus, method, and data distribution service system for data distribution service according to the present invention enables to effectively search for participants belonging to different domains through a device acting as a broker in a multi-domain DDS system.

In addition, the apparatus, method, and data distribution service system for the data distribution service according to the present invention enables DDS communication to be properly performed in a multi-domain environment.

1 is a diagram showing a general configuration of a DDS system composed of multiple domains.
2 is a diagram illustrating a DDS system composed of multiple domains according to the present invention.
3 is a flowchart illustrating a search operation between broker devices in the DDS system according to the present invention.
4 is a diagram illustrating a packet structure of a message according to the present invention.
5 is a flowchart illustrating a participant search operation in the DDS system according to the present invention.
6 is a flowchart illustrating a method of performing DDS communication in a DDS system according to the present invention.
7 is a block diagram showing the structure of an apparatus for DDS according to the present invention.

In the following description of embodiments of the present disclosure, when it is determined that a detailed description of a related well-known configuration or function may obscure the gist of the present disclosure, the detailed description may be omitted.

As used herein, "includes," "can include." And the like refer to the existence of the corresponding function, operation, component, etc. disclosed, and do not limit one or more additional functions, operations, components, and the like. Also, in this specification, "includes." Or "have." And the like are intended to indicate that there is a feature, number, step, action, component, part, or combination thereof described in the specification, and that one or more other features or numbers, step, action, component, part, or It should be understood that they do not preclude the presence or possibility of adding these in advance.

As used herein, the singular forms "a", "an" and "the" include plural forms unless the context clearly indicates otherwise.

Hereinafter, with reference to the accompanying drawings will be described the present invention.

2 is a diagram illustrating a DDS system composed of multiple domains according to the present invention.

2, the DDS system according to the present invention is composed of a plurality of domains (10, 20). Although only two domains are shown in the embodiment of FIG. 2, the number of domains is not limited.

Each domain 10, 20 may be configured to connect to one router 11, 21 to form a local network. Each domain 10, 20 may communicate with other domains 10, 20 via internal routers 11, 21.

Each domain 10, 20 consists of a number of participants 12, 22. Participants 12 and 22 existing within domains 10 and 20 operate as RTPS communication objects and may be referred to as nodes. Each participant (12, 22) is a desktop computer, notebook computer, Ultra Mobile PC (UMPC), workstation, net-book, Personal Digital Assistants (PDA), portable computer, web tablet ), Mobile phones, smart phones, e-books, portable multimedia players, portable game consoles, navigation devices, set-top boxes, various One of electronic devices, various electronic devices constituting a computer network, and the like may be various types of terminal devices. In the embodiment of FIG. 2, only one participant 12, 22 is shown in each domain 10, 20, although a greater number of participants may exist in domain 10, 20.

Each participant 12, 22 may have one or more publishers or subscribers. The publisher may include one or more writers (or datawriters, publication entities) to convey their information, and the subscriber may include one or more readers (or readers) to receive the publisher's information. , Datareaders, and subscription objects).

The publisher and subscriber applications create topics that represent the subject of specific data and exchange information with each other by registering them as topics of interest to writers and readers. Since publishers and subscribers with different topics of interest do not exchange topic data, there is no interference between them. In other words, the DDS system is a serverless peer-to-peer structure where only participants with the same topic of interest in the domain communicate. The data corresponding to the topic of interest is transmitted as a DDS data packet through the writer and the DDS network, and the reader checks the topic data included in the received DDS data packet and delivers it to the application program.

In order to perform the above-described operation, each participant 12, 22 in each domain 10, 20 performs a search for finding another participant participating in the domain 10, 20 to which it belongs. This will be described in detail as follows.

Each participant 12, 22 sends a discovery message (or discovery message) in a unicast or multicast manner, informing its other participants in the domain 10, 20. This process is called participant search. The discovery message is a global unique identifier (GUID) assigned to the participant (12, 22) sending the discovery message, the protocol version of the participant (12, 22), vendor identifier, unicast and multicast locator (IP). Information such as address and port number) and how to track participants. Here, the GUID is assigned to identify each participant 12, 22 within the domain 10, 20, and the other participant transmits the corresponding discovery message or DDS data packet from the GUID of the discovery message or DDS data packet. It can be identified that the other participant is a specific participant who exists in the same domain (10, 20) as himself. In this way, the participants 12 and 22 may discover other participants belonging to the same domain 10 by communicating and exchanging discovery messages, respectively.

When the participant search is completed, each participant 12 and 22 performs an end point search for confirming and exchanging QoS information of a writer or a leader, which is a communication object that actually performs topic data transmission within the participant.

In a typical DDS system, participant search is configured to be possible only within the same domain (10, 20). That is, in the general DDS system, the participant 12 belonging to the first domain 10 may not search for the participant 22 belonging to the second domain. In addition, the participant 22 belonging to the second domain 20 may not search for the participant 12 belonging to the first domain. This allows participants 12 and 22 to send and receive discovery messages only within their own domains 10 and 20. This prevents efficient DDS communication in a large DDS system composed of multiple domains.

In order to solve the above problem, in various embodiments of the present disclosure, each of the domains 10 and 20 includes devices 13 and 23 that operate as brokers. The devices 13 and 23 are devices for the DDS, hereinafter referred to as broker devices 13 and 23 for convenience.

The broker devices 13 and 23 may transmit information about the participants 12 and 22 in the domains 10 and 20 to which they belong to the broker devices 13 and 23 of the other domains 10 and 20. In addition, the broker devices 13 and 23 that have received the information about the participants 12 and 22 in the other domains 10 and 20 allocate an internal port number for the corresponding participants 12 and 22, and the internal participant 12 , 22) and the DDS communication between the participants 12 and 22. As a result, the broker device 13, 23 can enable DDS communication as if the participants 12, 22 in the other domains 10, 20 are present in the internal domains 10, 20.

Hereinafter, a method for enabling the DDS communication and searching for participants distributed in different domains through the broker devices 13 and 23 will be described in more detail.

3 is a flowchart illustrating a search operation between broker devices in the DDS system according to the present invention.

In the embodiment of FIG. 2, the first broker apparatus 13 is disposed in the first domain 10, and the second broker apparatus 23 is disposed in the second domain 20. The first broker apparatus 13 and the second broker apparatus 23 may communicate through the first and second routers 11 and 21 existing in the first domain 10 and the second domain 20, respectively. .

The first broker apparatus 13 and the second broker apparatus 23 are assigned IP addresses and port numbers corresponding to the domains 10 and 20 to which they belong. At this time, the first broker device 13 and the second broker device 23 may be assigned the same port number of a predetermined value. In the embodiment of FIG. 2, the first broker apparatus 13 is assigned an IP address of 192.168.0.2 and a port number of 8301, and the second broker apparatus 23 has an IP address of 192.168.2.1 and a port number of 8301. Is assigned. Also, in various embodiments of the present disclosure, GUIDs may be allocated to the first broker apparatus 13 and the second broker apparatus 23 similarly to the participants 12 and 22.

Similarly, the first router 11 and the second router 21 are also assigned an IP address. In the embodiment of FIG. 2, an IP address of 192.168.0.1 is assigned to the first router 11 and an IP address of 192.168.2.1 is assigned to the second router 21. In one embodiment, the first router 11 and the second router 21 may be further assigned an external network address for communicating with the external network. In the example of FIG. 2, the first router 11 is assigned an external network address of 129.254.1.2, and the second router 21 is assigned an external network address of 129.254.1.4.

In various embodiments of the present disclosure, the first broker device 13 and the second broker device 23 may perform a search for finding each other.

Referring to FIG. 3, the first broker apparatus 13 may allocate a port number for receiving a message and / or a packet from another domain. In detail, the first broker apparatus 13 may allocate a port number for the broker apparatus of another domain, for example, the second broker apparatus 23 of the second domain 20 (301). In the embodiment of FIG. 2, the first broker apparatus 13 allocates 57321 as a port number for the second broker apparatus 23. The assigned port number may be set as a receiving port for receiving a message and / or a packet from the second broker device 23.

Thereafter, the first broker device 13 may transmit an alive message to the second broker device 23 through the first router 11 and the second router 21 of the second domain 20. (302). At this time, the first broker apparatus 13 recognizes the external network address of the second router 21 in order to transmit the alive message. In addition, as described above, the first broker apparatus 13 may recognize that the second broker apparatus 23 is assigned the same port number as itself. Accordingly, in the embodiment of FIG. 2, the first broker device 13 transmits an alive message to the destination address 192.254.1.4:8301.

In various embodiments of the present disclosure, the alive message may have a packet structure as shown in FIG. 4. Referring to FIG. 4, the packet structure may include a PREFIX field and a Struct socketaddr field. The PREFIX field may include domain information, identification information of the broker devices 13 and 23, for example, a GUID, and the like. The Struct socketaddr field may include bind information such as IP addresses and packet numbers of the broker devices 13 and 23. In addition, the alive message may include identification information allocated for the broker devices 13 and 23 to receive the alive message, for example, a packet number. Alive message is a term adopted to distinguish a discovery message from a participant 12 and 22. In various embodiments, the alive message may be referred to as a discovery message, a keep-alive message, a hello message, a heartbeat message, or the like. .

The alive message is forwarded by the second router 21 to the second broker device 23 having the port number 8301.

The second broker apparatus 23 may identify the first broker apparatus 13 from the received alive message and allocate a port number for the first broker apparatus 13 (303). The second broker device 23 may identify the first broker device 13 based on information extracted from the live message, for example, a port number. In the embodiment of FIG. 2, the second broker apparatus 23 may identify the first broker apparatus 13 using the port number 57321.

The second broker device 23 may assign a port number for the identified first broker device 13. In the embodiment of FIG. 2, the second broker device 23 allocates 68213 as a port number for the first broker device 13. The assigned port number may be set as a reception port for receiving a packet such as a message and / or data from the first broker device 13.

The second broker apparatus 23 is information about the identified first broker apparatus 13, and includes domain information (which may include router information), GUID, IP address, and packet number of the first broker apparatus 13. Etc. can be stored and managed. According to the implementation, the second broker apparatus 23 may manage the mapping information by mapping the port number allocated by the second broker apparatus 23 and the information of the first broker apparatus 13. In the embodiment of FIG. 2, the port number 68213 of the second broker apparatus 23 may be associated with the port number 57321 of the first broker apparatus.

Thereafter, the second broker device 23 may transmit a response message ACK to the first broker device 13 through the second router 21 and the first router 11 of the first domain 10. 304. To this end, the second broker apparatus 23 similarly recognizes the external network address of the first router 11. In addition, the second broker apparatus 23 may recognize the port number 57321 of the first broker apparatus 13 identified from the alive message. Accordingly, in the embodiment of FIG. 2, the second broker device 23 transmits a response message to the destination address 192.254.1.2:27321.

In various embodiments of the present disclosure, the response message may have a packet structure as shown in FIG. 4. In another embodiment, the response message may have a different packet structure than the live message. According to various embodiments of the present disclosure, the response message is information indicating that the second broker apparatus 23 correctly received the alive message of the first broker apparatus 13 and identification information of the second broker apparatus 23. For example, it may include a GUID, an IP address, a packet number, and the like.

According to various embodiments of the present disclosure, the second broker apparatus 23 checks the integrity of the alive message received from the first broker apparatus 13, and if it is determined that the message is not received correctly, a negative acknowledgment message (NACK). Can be transmitted. In this case, the live message may be reexchanged between the first broker device 13 and the second broker device 23.

The first broker device 13 may identify the second broker device 23 from the received response message (305). The first broker apparatus 13 may identify the second broker apparatus 23 based on information extracted from the response message, for example, a port number. In the embodiment of FIG. 2, the first broker device 13 may identify the second broker device 23 using the port number 68213.

The first broker apparatus 13 is information about the identified second broker apparatus 23, and includes domain information (which may include router information), GUID, IP address, and packet number of the second broker apparatus 23. Etc. can be stored and managed. According to the implementation, the first broker device 13 may store the port number allocated by itself and the information of the second broker device 23 as mapping information. In the embodiment of FIG. 2, the port number 57321 of the first broker device 13 and the port number 68213 of the second broker device 23 may be associated with each other.

After the above-described discovery process is completed, the first broker apparatus 13 and the second broker apparatus 23 may confirm the existence of each other by exchanging an alive message according to a preset period (306, 307). At this time, since the first broker device 13 and the second broker device 23 recognize each other's port number, the Alive message may be directly transmitted to the other party's port number. In the embodiment of FIG. 2, the first broker device 13 sends an alive message to the destination address 129.254.1.4:68213 for the second broker device 23, and the second broker device 23 sends the first broker device. Send an alive message to destination address 129.254.1.2:57321 for (13). The exchange interval of the alive message may be determined based on network performance, network load, and the like.

Hereinafter, the first participant 12 and the second participant 22 of the first domain 10 and the second domain 20 may search for a participant through the first broker device 13 and the second broker device 23. It will be described in detail how to perform.

5 is a flowchart illustrating a participant search operation in the DDS system according to the present invention.

2, the first participant 12 is disposed in the first domain 10, and the second participant 22 is disposed in the second domain 20. The first participant 12 and the second participant 22 are assigned IP addresses and port numbers provided by the domains 10 and 20 to which they belong. At this time, the first participant 12 and the second participant 22 may be assigned a port number of a value preset by the RTPS protocol. 2, the first participant 12 is assigned an IP address of 192.168.0.3 and a port number of 7400, and the second participant 22 is assigned an IP address of 192.168.2.3 and a port number of 7400. have. In addition, the first participant 12 and the second participant 22 are assigned a GUID.

In various embodiments of the present invention, the first participant 12 and the second participant 22 perform a search for other participants in the domain according to a common RTPS protocol.

First, the first participant 12 may transmit a discovery message in the first domain 10 in a unicast or multicast manner (501). The discovery message may include information about the GUID, IP address, port number, etc. of the first participant 12.

The first broker device 13 operating in the first domain 10 may receive a discovery message transmitted from the first participant 12. The first broker device 13 may identify 502 the first participant 12 from the received discovery message. The first broker apparatus 13 may identify the first broker apparatus 13 based on information extracted from the discovery message, for example, a port number. The first broker device 13 may store and manage information regarding the port number of the first participant 12.

Subsequently, the first broker device 13 passes through the first router 11 and the second router 21 of the second domain 20 to the second broker device 23 and to the first participant 12. The discovery message may be sent (503). The discovery message transmitted and received between the broker devices may have the same packet structure as the discovery message defined in the RTPS protocol or may have a packet structure defined separately. The discovery message is identification information for the first participant 12 and may include, for example, domain information, GUID, IP address, packet number, and the like.

The second broker device 23 may identify the first participant 12 from the received discovery message and assign an IP address and a port number for the first participant 12 (504). The second broker device 23 may identify the first participant 12 based on information extracted from the discovery message, for example, a port number. In the embodiment of FIG. 2, the second broker device 23 may identify the first participant 12 using the port number 7400.

The second broker device 23 may assign a port number for the identified first participant 12. In the embodiment of FIG. 2, the second broker device 23 assigns 88888 as the port number for the first participant 12. Here, the port number may be set as a receiving port for receiving a packet transmitted from the participants of the second domain 20 for the first participant 12.

In one embodiment, the second broker device 23 may further assign an IP address for the identified first participant 12. The first domain 10 and the second domain 20 may have different ranges of IP addresses that can be used as internal IP addresses. Thus, IP addresses within the range of IP addresses used by the first domain 10 may not be correctly identified by brokers and participants present in the second domain 20. Accordingly, the second broker device 23 may allocate an IP address corresponding to the second domain 20 for the first participant 12 existing in the first domain 10. In the embodiment of FIG. 2, the second broker device 23 may allocate an IP address of 192.168.2.5 for the first participant 12.

The second broker device 23 is information about the identified first participant 12, and may include domain information of the first participant 12 (including information about a broker device of the corresponding domain). You can store and manage the GUID, IP address, and port number. The second broker device 23 may store information about the first participant 12 in association with an IP address and a port number allocated for the first participant 12 as mapping information. In the example of FIG. 2, for the first participant 12, the port number 7400 in the first domain 10, the IP address 192.168.2.5 and the port number 88888 allocated by the second broker device 23 may be associated. have.

According to an embodiment, the second broker device 23 may transmit a response message to the first broker device 13 in response to the discovery message (505). The response message may include a port number, etc. allocated by the second broker device 23 for the first participant 12. In this case, the first broker device 13 may include information about the first participant 12 in the first domain 10 and a port number allocated by the second broker device 23 for the first participant 12. Can be stored in conjunction.

Thereafter, the second broker apparatus 23 may transmit 506 the RTPS discovery message for the first participant 12 in the second domain 20 in a unicast or multicast manner. The discovery message may include an IP address, a port number, a GUID of the first participant 12, etc. allocated by the second broker device 23 for the first participant 12.

The discovery message transmitted by the second broker device 23 may be received by the second participant 22 operating in the second domain 20. Since the discovery message includes a valid IP address, a port number, etc. in the second domain 20, the second participant 22 may effectively identify the first participant 12 (507). By identifying the first participant 12, the second participant 22 recognizes as if the first participant 12 is a participant in the second domain 20, and transmits a packet for the first participant 12. Or may receive a packet transmitted from the first participant 12.

Similarly, the second participant 22 may also send a discovery message in the second domain 20 in a unicast or multicast fashion (508). Receiving the discovery message, the second broker device 23 identifies the second participant 22 and stores a port number for the second participant 22 (509), and then sends the second broker device 13 to the first broker device 13. The discovery message for the participant 22 may be sent (510).

The first broker apparatus 13 may allocate a corresponding IP address and a port number of the first domain 10 for the second participant 22 (511). In the embodiment of FIG. 2, the first broker device 13 assigns port number 99999 for the second participant 22. The first broker apparatus 13 may transmit a response message to the second broker apparatus 23 (512), and may transmit a discovery message for the second participant 22 in the first domain 10 (513). . The first participant 12 in the first domain 10 may receive a discovery message sent by the first broker device 13 and may effectively identify the second participant 22 (514).

Since the detailed content of the method for searching for the participant for the second participant 22 is the same as the search method for the first participant 12, a detailed description thereof is omitted.

Hereinafter, after searching for the participant described above, a method in which the first participant 12 and the second participant 22 located in different domains substantially perform DDS communication will be described in detail.

6 is a flowchart illustrating a method of performing DDS communication in a DDS system according to the present invention. The DDS communication method described below may be applied to DDS communication for a message packet for endpoint discovery performed after the participant discovery illustrated in FIG. 5 or a data packet transmitted and received between the participants after the search is completed.

Referring to FIG. 6, the first participant 12 transmits a packet in the first domain 10 (601). The packet may be transmitted in a unicast or multicast manner, and in the case of a data packet, may be sent for a subscriber to a topic of the data packet. In one embodiment, the packet may be a packet for the second participant 22 in the second domain 20. That is, in the embodiment of FIG. 2, the packet is a packet in which the port number of the destination address is set to 99999.

The first broker device 13 operating in the first domain 10 may receive a packet transmitted from the first participant 12. The first broker apparatus 13 may identify the destination of the packet (602). In detail, the first broker apparatus 13 may determine whether the packet is a packet to be transmitted to another domain based on the port number where the packet is received. The port number at which the packet is received may correspond to the destination address of the packet.

The first broker apparatus 13 may search the pre-stored mapping information for the port number where the packet is received and determine whether the corresponding port number is associated with information of another domain. When the corresponding port number is associated with information of another domain, the first broker device 13 may identify information on the domain to which the packet is to be transmitted and information about the broker device to which the packet is to be transmitted, from the mapping information.

In the embodiment of FIG. 2, the first broker apparatus 13 is a packet to be transmitted to the second domain 20, that is, to the second broker apparatus 23, for the packet received at the port number 99999. Can be identified. In an embodiment, when the mapping information includes the participant information of the second domain 20 associated with the port number 99999, the first broker apparatus 13 may determine that the packet is the port number 7400 of the second domain 20. It can be further identified that the packet to be transmitted to the second participant 22 using the. The identification of the port number and the participant in the second domain 20 may be performed by the second broker device 23 operating in the second domain 20. In this case, the first broker apparatus 13 may only identify that the packet is a packet to be transmitted to the second domain 20.

The first broker apparatus 13 may transmit a packet to the second broker apparatus 23 of the second domain 20 based on the identification result (603).

In one embodiment, the first broker device 13 may deliver the packet as it is without changing the destination address of the packet. In this case, in the embodiment of FIG. 2, the destination port number of the packet is set to 99999. In another embodiment, the first broker apparatus 13 may forward the packet by resetting the destination address of the packet to the port number in the identified second domain 20. In this case, in the embodiment of FIG. 2, the destination port number of the packet is set to 7400.

The packet transmitted from the first broker apparatus 13 to the second broker apparatus 23 is a port number allocated by the second broker apparatus 23 for the first broker apparatus 13 as described above, that is, FIG. 2. In the embodiment of the above is received at the second broker device 23 through 68213.

The second broker apparatus 23 may identify the participant in the second domain 20 to which the packet should be sent, based on the destination address of the packet (604).

As the packet is received through the port number allocated for the first broker device 13, the second broker device 23 may identify that the packet is received from the first domain 10. The second broker device 23 may determine to which participant in the second domain 20 the packet should be delivered.

According to an embodiment, when the received packet includes a port number in the first domain 10, the second broker device 23 may search for the first port number in pre-stored mapping information. When the port information is found in the pre-stored mapping information, the second broker device 23 may determine the port number of the second domain 20 associated with the corresponding port number. In the embodiment of FIG. 2, the second broker apparatus 23 transmits the packet to the second participant 22 using the port number 7400 of the second domain 20 with respect to the packet in which the port number of the destination address is set to 99999. It can be identified that the packet should be.

In another embodiment, when the received packet includes a port number in the second domain 20, the second broker device 23 may identify a participant to which the packet is to be transmitted. In the embodiment of FIG. 2, the second broker apparatus 23 may identify that the packet is to be transmitted to the second participant 22 with respect to the packet in which the port number of the destination address is set to 7400.

The second broker apparatus 23 may transmit a packet to the participants in the domain based on the identification result (605). In the embodiment of FIG. 2, the second broker device 23 may deliver a packet to the second participant 22.

As described above, in the present invention, the DDS communication between the participants located in different domains is provided by the broker devices 13 and 23 provided in the respective domains 10 and 20 and configured to communicate via the routers 11 and 12. Makes this possible.

7 is a block diagram showing the structure of an apparatus for DDS according to the present invention. The apparatus 700 for the DDS may be the above-described broker apparatus.

Referring to FIG. 7, the apparatus 700 may include a communication unit 710, a controller 720, and a storage unit 730.

The communication unit 710 communicates with the outside using a wired or wireless communication technology. In detail, the communication unit 710 may communicate with at least one participant existing in the same domain as the device 700 or another device existing in a different domain. According to various embodiments of the present disclosure, the communication unit 710 may exchange an alive message and a response message with another device existing in another domain. In addition, the communication unit 710 may deliver a packet received from a participant in a domain to a device in another domain, or may deliver a packet received from a device in another domain to a participant in a domain. Communication with other domains can be mediated through routers.

The controller 720 controls each component of the apparatus 700 to perform the DDS communication method according to the present invention. In detail, the controller 720 may allocate a port for another device existing in another domain, and receive a message and / or a packet from another device through the assigned port. In addition, the controller 720 transmits information such as its GUID, IP address, port number, etc. to another device existing in another domain, so that the other device can allocate a port for itself.

In addition, the controller 720 stores and manages identification information, for example, a port number, of at least one participant existing in a domain to which the controller 720 belongs. The controller 720 transmits identification information of at least one participant existing in the domain to which the participant belongs to the device of the other domain, so that the device of the other domain can allocate a port for the participant. The controller 720 may allocate and store identification information, for example, a port, for at least one participant in another domain received from a device in another domain.

When the packet is received at a port allocated for a participant in another domain, the controller 720 identifies a device of a domain to which the participant belongs, that is, a domain to which the participant belongs, and delivers the packet to the identified device, thereby identifying the identified device. This allows packets to be sent to participants in other domains. In addition, when a packet is received from a device in another domain, the controller 720 may identify a participant of an internal domain to which the packet is to be delivered, based on a destination port number of the packet, and deliver the packet to the identified participant.

More detailed control operations of the controller 720 are as described with reference to FIGS. 2 to 6.

The storage unit 730 may store information, data, an operating system, a program, software, an application, and the like necessary for the operation of the device 700. According to various embodiments of the present disclosure, the storage unit 730 may store and manage the port number as information for at least one participant in the domain under the control of the controller 720. In addition, the storage unit 730 may store the port number and the port number, IP address, and the like separately allocated for the internal domain by the controller 720 as information about brokers and at least one participant in another domain, as linkage mapping information. have.

Those skilled in the art will appreciate that various modifications and variations can be made without departing from the essential features of the present invention. In addition, the embodiments disclosed in the specification and the drawings merely present specific examples to easily explain and easily understand the contents of the present invention, and are not intended to limit the scope of the present invention. Therefore, the scope of the present invention should be construed that all changes or modifications derived based on the technical spirit of the present invention are included in the scope of the present invention in addition to the embodiments disclosed herein.

700: device
710: communication unit
720: control unit
730: storage unit

Claims (10)

An apparatus for data distribution service,
A communication unit communicating with a second device of a second domain different from the first domain to which the device belongs; And
Allocating an internal identifier of the first domain for at least one second participant constituting the second domain and using the internal identifier to the at least one first participant constituting the first domain Send a second discovery message for a second participant, send a first discovery message for the at least one first participant to the second device, and use the internal identifier to provide the at least one first participant and the A control unit for controlling the communication unit to communicate with the second device to mediate packets transmitted and received between at least one second participant,
The first search message,
And wherein the second device is used to assign an internal identifier of the second domain for the at least one first participant. The method of claim 1, wherein the internal identifier,
And at least one of an IP address and a port number corresponding to the first domain. The method of claim 1, wherein the control unit,
Allocate an internal identifier for the second device, and send an alive message containing the identification information of the device to the second device,
The alive message,
And wherein the second device is sent to assign an internal identifier of the second domain for the device. The method of claim 3,
Further comprising a storage for storing information,
The control unit,
When the response message including the identification information of the second device is received in response to the alive message from the second device, the identification information of the second device is mapped to the storage unit as mapping information in association with the assigned internal identifier. Device for storing. The method of claim 1, wherein the control unit,
When a packet for an internal identifier assigned for any second participant is received from the at least one first participant, the packet is transmitted to the second device in correspondence to the internal identifier of the packet,
The second device,
And deliver the packet to a second participant identified based on the internal identifier of the packet. A method for data distribution service of a device constituting a first domain, the method comprising:
Transmitting a first discovery message for at least one first participant constituting the first domain to a second device of a second domain different from the first domain;
Allocating an internal identifier of the first domain for the at least one second participant when the discovery message for the at least one second participant constituting the second domain is received from the second device;
Sending a second discovery message for the at least one second participant to the at least one first participant using the internal identifier; And
Communicating with the second device to mediate packets transmitted and received between the at least one first participant and the at least one second participant using the internal identifier,
The first discovery message transmitted to the second device,
And the second device is used to assign an internal identifier of the second domain for the at least one first participant. The method of claim 6, wherein the internal identifier,
And at least one of an IP address and a port number corresponding to the first domain. The method of claim 6, wherein before transmitting the first discovery message,
Assigning an internal identifier for the second device; And
The method may further include transmitting an alive message including the identification information of the device to the second device.
The alive message,
And wherein the second device is sent to assign an internal identifier of the second domain for the device. The method of claim 6, wherein the communicating step,
If a packet for an internal identifier assigned for any second participant is received from the at least one first participant, transmitting the packet to the second device corresponding to the internal identifier of the packet,
The second device,
Delivering the packet to a second participant identified based on the internal identifier of the packet. A data distribution service system comprising the apparatus according to any one of claims 1 to 5.

Images