KR20220075985A - System ndn-based communication supporting mobility of publisher and method for the same - Google Patents

Abstract

The present invention relates to a named data networking (NDN)-based communication system, which publishes content, and at least one publisher node that generates and provides topic information including the topic of the content and publication information including the data of the content; , at least one subscriber node that generates and transmits subscription request data for the content and receives data of the content published by the publisher node, and at least one topic rendezvous node that stores and manages the topic information; At least one general rendezvous node that transmits the topic information received from the at least one publisher node to the topic rendezvous node, stores and manages the publication information, and provides data of the content to the at least one subscriber node includes

Description

NDN-based communication system and method to support publisher's mobility

The present invention relates to an NDN (Named Data Network)-based communication system, and more particularly, to an NDN-based communication system having a distributed broker structure.

Currently, the scale of data services on the Internet is rapidly increasing. Meanwhile, the current Internet operates by using an IP address. Data requestors, i.e. consumers, can only request and receive data using an IP address. In such an Internet network, if there is at least one user on the network requesting basically the same data, it is necessary to repeatedly transmit data as many as the number of users, which is inefficient in terms of repeated data transmission.

In order to solve this problem, recently, research and development of a network structure centered on information rather than an IP-based network structure is being actively conducted. The information-centric network (networking) in the present disclosure includes a content-based/centric network, an information-based/centric network, a Content Centric Network (CCN), an Information Centric Network (ICN), and a Named Data Network (NDN).

Networks that support information-centric technologies introduce the concept of an information provider (publisher, producer) who generates data on behalf of a sender, and an information consumer (consumer) who receives and consumes data, so networks use information names instead of IP addresses to route can be performed. Routers can store specific data when needed and distribute the data to nearby new consumers who need it.

In an information-centric network, when an information consumer sends an interest packet with the requested data name in the header, the node corresponding to the information provider that caches or owns the data or caches the data through data name-based forwarding It can respond as a packet. In this case, the data packet may be delivered to the data requester along the path through which the interest packet is generated.

The information-centric network has a strength in that it can support the mobility of the terminal compared to the address-based IP network. As an example, a data provider (producer) is a fixed server, and when a data requester (consumer) moves, the requestor can use the information-centric network by simply retransmitting an interest packet whenever the access network changes. Mobility of the requestor node (terminal) can be naturally supported by the exchange method of the interest packet/data packet. However, when the access network is changed due to the movement of the data producer, the mobility of the producer node (terminal) is not supported.

Meanwhile, in the Pub/sub service based on NDN, information consumers become subscribers and producers become publishers. Even in the NDN-based Pub/sub service structure, the mobility of the subscriber node can be supported due to the characteristics of the NDN, but the mobility of the publisher node is not supported.

However, if the number of mobile terminals increases, the publisher node can also move, so it is necessary to support the mobility of the publisher node even in an NDN-based distributed Pub/Sub system structure.

An object of the present disclosure is to provide an NDN-based communication system and method supporting the mobility of a publisher node.

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those of ordinary skill in the art to which the present invention belongs from the description below. will be able

According to an aspect of the present disclosure, a named data networking (NDN) based communication system may be provided. The system publishes the content, and at least one publisher node generates and provides topic information including the topic of the content and publication information including the data of the content, and generates and transmits subscription request data for the content and at least one subscriber node receiving data of the content published by the publisher node, at least one topic rendezvous node storing and managing the topic information, and the topic information received from the at least one publisher node may include at least one general rendezvous node that transmits to the topic rendezvous node, stores and manages the publication information, and provides data of the content to the at least one subscriber node.

According to another aspect of the present disclosure, an NDN-based data subscription method may be provided. The method is a method for processing data in a named data networking (NDN)-based communication system, wherein at least one publisher node generates topic information including a topic of content and publication information including data of the content, and , the process of publishing the content using the topic information and publication information, at least one general rendezvous node receiving the topic information from the at least one publisher node, and transmitting the topic information to the topic rendezvous node a process, wherein the at least one topic rendezvous node stores and manages the topic information, and the at least one general rendezvous node receives and stores the publication information from the at least one publisher node; A process in which at least one subscriber node generates and transmits a subscription request for the content, and the at least one general rendezvous node provides data of the content corresponding to the subscription request to the at least one subscriber node process may be included.

The features briefly summarized above with respect to the present disclosure are merely exemplary aspects of the detailed description of the present disclosure that follows, and do not limit the scope of the present disclosure.

According to the present disclosure, it is possible to detect the movement of the publisher node and store content or data without the need for the publisher node to periodically transmit a separate control message in order to support the publisher's mobility.

In addition, according to the present disclosure, it is possible to detect and manage the occurrence of a load in the system due to frequent movement of the publisher node.

In addition, by transmitting a control message limitedly only when the movement of the publisher node is detected, there is an effect that it is possible to significantly reduce the network load for managing the movement of the publisher node.

The effects obtainable in the present invention are not limited to the above-mentioned effects, and other effects not mentioned may be clearly understood by those of ordinary skill in the art to which the present invention belongs from the following description. will be.

1 is a diagram illustrating an NDN-based communication system supporting the mobility of a publisher according to an embodiment of the present disclosure.
2A and 2B are diagrams illustrating an NDN-based communication system supporting the mobility of a publisher according to an embodiment of the present disclosure.
3A and 3B are diagrams illustrating data managed by a TRN and a DRN in an NDN-based communication system supporting the mobility of a publisher according to an embodiment of the present disclosure.
4 is a diagram illustrating an operation of an NDN-based communication system supporting the mobility of a publisher according to an embodiment of the present disclosure.
5 is a flowchart illustrating an operation of an RN provided in an NDN-based communication system according to an embodiment of the present disclosure.
6 is a block diagram illustrating an apparatus for executing an NDN-based communication system and method according to an embodiment of the present disclosure.

Hereinafter, with reference to the accompanying drawings, embodiments of the present invention will be described in detail so that those of ordinary skill in the art to which the present invention pertains can easily implement them. However, the present invention may be embodied in several different forms and is not limited to the embodiments described herein.

In describing an embodiment of the present invention, if it is determined that a detailed description of a well-known configuration or function may obscure the gist of the present invention, a detailed description thereof will be omitted. And, in the drawings, parts not related to the description of the present invention are omitted, and similar reference numerals are attached to similar parts.

In the present invention, when a component is "connected", "coupled" or "connected" to another component, it is not only a direct connection relationship, but also an indirect connection relationship in which another component exists in the middle. may also include. In addition, when a component is said to "include" or "have" another component, it means that another component may be further included without excluding other components unless otherwise stated. .

In the present invention, terms such as 1st, 2nd, etc. are used only for the purpose of distinguishing one component from other components, and unless otherwise specified, do not limit the order or importance between the components. Therefore, within the scope of the present invention, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment is referred to as a first component in another embodiment. can also be called

In the present invention, the components that are distinguished from each other are for clearly explaining each characteristic, and do not necessarily mean that the components are separated. That is, a plurality of components may be integrated to form one hardware or software unit, or one component may be distributed to form a plurality of hardware or software units. Accordingly, even if not specifically mentioned, such integrated or dispersed embodiments are also included in the scope of the present invention.

In the present invention, components described in various embodiments do not necessarily mean essential components, and some may be optional components. Accordingly, an embodiment composed of a subset of the components described in one embodiment is also included in the scope of the present invention. In addition, embodiments including other components in addition to components described in various embodiments are also included in the scope of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, an apparatus and a method in an embodiment of the present invention will be described with reference to the accompanying drawings. It will be described in detail focusing on the parts necessary to understand the operation and operation according to the present invention.

1 is a diagram illustrating an NDN-based communication system supporting the mobility of a publisher according to an embodiment of the present disclosure.

Referring to FIG. 1 , the NDN-based communication system 1 according to an embodiment of the present disclosure includes at least one subscriber node 11-1, 11-2, ... 11-n, and at least one publisher. nodes 13-1, 13-2, ... 13-n, and rendezvous nodes 15-1, 15-2, ..., 15-n. In addition, at least one subscriber node (11-1, 11-2, ... 11-n) and at least one publisher node (13-1, 13-2, . .. 13-n), and the rendezvous nodes 15-1, 15-2, ..., 15-n may be connected through NDN (Named Data Networking) networking 17, and at least one subscriber node ( 11-1, 11-2, ... 11-n), at least one publisher node (13-1, 13-2, ... 13-n), and a rendezvous node (15-1, 15-2, Data transmission between ..., 15-n) can be processed based on the NDN protocol.

At least one publisher node (13-1, 13-2, ... 13-n) is a node that generates and provides content, and at least one subscriber node (11-1, 11-2, ... 11-) n) may be a node using the above-described content.

In particular, the NDN-based communication system 1 according to an embodiment of the present disclosure may be configured in a distributed broker manner. Accordingly, the system 1 may include a plurality of distributed rendezvous nodes 15-1, 15-2, ..., 15-n. The rendezvous nodes 15-1, 15-2, ..., 15-n include at least one subscriber node 11-1, 11-2, ... 11-n and at least one publisher node 13. -1, 13-2, ... 13-n) can be stored and managed. Further, the plurality of rendezvous nodes 15-1, 15-2, ..., 15-n uses the stored data, and at least one subscriber node 11-1, 11-2, ... 11- n) and at least one publisher node (13-1, 13-2, ... 13-n) can efficiently process data transmission and reception.

2A and 2B are diagrams illustrating an NDN-based communication system supporting the mobility of a publisher according to an embodiment of the present disclosure.

First, referring to FIG. 2A , the publisher node 23 may transmit event data to a rendezvous node (RN) 25 whenever an event occurs for a specific topic.

In particular, in order to support the mobility of the publisher node 23 , the publisher node 23 may perform a publication start operation 230a of content (or data) and a publication subscription operation 230b separately. Specifically, in the publication initiation operation 230a, the publisher node 23 may advertise the name of the content (or data) that is being published. And, in the publication subscription operation 230b, the publisher node 23 may transmit content (or data).

In consideration of the foregoing, the rendezvous node 25 may store and manage data received from the publisher node 23 . In detail, the rendezvous node 25 may store and manage the name of the content (or data) received in the publication start operation and the content (or data) received in the publication subscription operation by distinguishing them. Specifically, the rendezvous node 25 may include a Topic Rendezvous Node (TRN) 250a (refer to FIG. 2B ) and a Data Rendezvous Node (DRN) 250b. The TRN 250a may be an entity that manages a name for the received content (or data), a name (eg, a topic) for the received content (or data), and a publisher of the content (or data) The identifier of the rendezvous node 25 to which the node 23 is connected can be stored and managed. The DRN 250b may be an entity that receives and stores content (or data), and may store and manage content (or data) and metadata for managing it. For example, data managed by the TRN 250a may be exemplified as shown in FIG. 3A , and data managed by the DRN 250b may be exemplified as shown in FIG. 3B . Topics can be organized into hierarchical topic names with publish and subscribe messages. The hierarchically configured topic names may be separated using a predetermined delimiter (eg, "/"), and the TRN 250a may configure the nodes of the tree as a separated name component. In this case, the TRN 250a may use a hash technique or the like when constructing a tree node. As described above, by configuring a topic tree by classifying topic names for each level, it is possible to quickly search for topic names.

4 is a diagram illustrating an operation of an NDN-based communication system supporting the mobility of a publisher according to an embodiment of the present disclosure, and illustrates an operation of a publisher node moving in the NDN-based communication system.

First, the first publisher node 41 may be connected through NDN (Named Data Networking) networking at the first location 410, and is connected to the first RN 45-1 to publish content (or data). can Specifically, the first publisher node 41 may provide a name (eg, a topic) for content (or data) through a publication initiation operation (Pub Adv) (S401). Then, the first publisher node 41 may transmit the content (or data) to the first RN 45-1 through a publication subscription operation (Pub Data) (S402)

On the other hand, the first RN 45-1 is an RN (eg, the 6th RN 45-6) that manages a name (eg, topic) for content (or data), and a name for content (or data) ( For example, a topic (Topic) may be delivered (S403), and the sixth RN 45-6 may store and manage a name (eg, a topic) for content (or data) (S404).

Meanwhile, the first publisher node 41 may be moved to the second location 420 ( S405 ). At this time, the first publisher node 41 may be connected to the system through NDN networking at the moved second location 420 , and at this time, an RN different from the first RN 45-1, for example, the second RN 45-2 ) can be connected to While the first publisher node 41 is connected to the second RN 45-2 at the second location 420, the first publisher node 41 issues event data when an event for content (or data) occurs. can do. In this case, the first publisher node 41 may transmit event data to the second RN 45-2, and the event data may be transmitted to the second RN 45-2 through a publication subscription operation (Pub Data) ( S406). The second RN 45-2 does not store information on the content (or data) issued by the first publisher node 41, and is in a state in which it is requested to store new content (or data). Accordingly, the second RN 45-2 may recognize that a publisher node that has stored data in another RN moves and requests publication of content (or data).

On the other hand, after receiving the event data from the first publisher node 41, the 2nd RN 45-2 is an RN that stores and manages the topic, that is, the 6th RN 45-6, may request verification (S406), and store and manage event data based on the result (S407, S408). For example, the 6th RN 45-6 may check a topic to be stored and managed, and may check whether a topic corresponding to the event data received from the 2nd RN 45-2 exists.

As a result of the verification of the 6th RN 45 - 6 , if the topic corresponding to the event data does not exist in the 6th RN 45 - 6 , the 2nd RN 45 - 2 is sent from the first publisher node 41 . The received event data may not be saved as valid data. On the other hand, as a result of the verification of the 6th RN 45 - 6 , if a topic corresponding to the event data exists in the 6th RN 45 - 6 , the 2nd RN 45 - 2 is sent from the first publisher node 41 . The received event data can be saved as valid data.

Furthermore, when a topic corresponding to the event data exists in the 6th RN 45-6, the 6th RN 45-6 is an RN that stores and manages data issued by the first publisher node 41, that is, , the information of the second RN 45-2 may be updated and managed.

5 is a flowchart illustrating an operation of an RN provided in an NDN-based communication system according to an embodiment of the present disclosure.

Referring to FIG. 5 , the publisher node may transmit data to the RN, and may configure a publish subscription message (Pub Data Massage) including the data to be transmitted and transmit it to the RN. In response, the RN may receive a publication subscription message (Pub Data Massage) (S501).

The RN uses the information included in the publication subscription message (Pub Data Massage) to check whether PSO information corresponding to the data exists (S502). When the PSO information corresponding to the data exists in the RN (S502-Y), the RN may store and manage the data included in the publication subscription message (Pub Data Massage) (S503). On the other hand, when there is no PSO information corresponding to the data in the RN (S502-N), the RN may request the TRN to check whether PSO information corresponding to the data exists (S504).

On the other hand, the TRN stores and manages the topic of data. In response to a request from the RN, it is checked whether the PSO information corresponding to the data exists in the topic stored and managed by the RN, and the result is returned to the RN. can be provided (S505).

The RN may check the result received from the TRN (S506) and, according to the received result, process the storage of data (S507, S508, S509). Specifically, if there is no PSO information corresponding to the data in the TRN (S506-N), the RN may delete the data received from the publisher node without storing the data (S507). On the other hand, if there is PSO information corresponding to the data in the TRN, the RN stores the PSO information corresponding to the data received from the publisher node (S508), and the data received through a publication subscription message (Pub Data Massage) It can be saved (S509).

6 is a block diagram illustrating an apparatus for executing an NDN-based communication system and method according to an embodiment of the present disclosure.

As described above, a plurality of nodes (or routers) may exist in an in-network system. In this case, the INP execution position may be determined to process data received from the user in the in-network system. That is, it is possible to determine a node for INP execution in the in-network.

In this case, as an example, the device configuration of FIG. 9 may be a configuration for a node (or a router) in an in-network system.

For example, each of the furnaces 800 may further include at least one of a memory 810 , a processor 820 , and a transceiver 830 as shown in FIG. 8 . In this case, as an example, the memory 810 may store the above-described user policy information or restriction condition information. In addition, the memory 810 may store other related information, and is not limited to the above-described embodiment. Also, the transceiver 830 may transmit an INP interest packet or transmit INP-executed data. That is, the transceiver 830 may be configured to transmit/receive data or information, and is not limited to the above-described embodiment.

Also, the processor 820 may control information included in the memory 810 based on the above description. In addition, the processor 820 may transmit information related to the in-network system to another node or device through the transceiver 1530 , and the embodiment is not limited thereto.

In order to implement the method according to the present disclosure, other steps may be included in addition to the illustrated steps, other steps may be excluded from some steps, or additional other steps may be included except some steps.

Various embodiments of the present disclosure do not list all possible combinations, but are intended to describe representative aspects of the present disclosure, and matters described in various embodiments may be applied independently or in combination of two or more.

In addition, various embodiments of the present disclosure may be implemented by hardware, firmware, software, or a combination thereof. For implementation by hardware, one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), general purpose It may be implemented by a processor (general processor), a controller, a microcontroller, a microprocessor, and the like.

The scope of the present disclosure includes software or machine-executable instructions (eg, operating system, application, firmware, program, etc.) that cause an operation according to the method of various embodiments to be executed on a device or computer, and such software or and non-transitory computer-readable media in which instructions and the like are stored and executable on a device or computer.

Claims (14)

In the NDN (Named Data Networking)-based communication system,
At least one publisher node that publishes content, and generates and provides topic information including a topic of the content and publication information including data of the content;
at least one subscriber node for generating and transmitting subscription request data for the content and receiving data of the content issued by the publisher node;
at least one topic rendezvous node for storing and managing the topic information;
At least one general rendezvous node that transmits the topic information received from the at least one publisher node to the topic rendezvous node, stores and manages the publication information, and provides data of the content to the at least one subscriber node An NDN-based communication system comprising a.
According to claim 1,
The at least one publisher node comprises:
constructs and transmits a topic message for transmitting the topic information;
An NDN-based communication system for constructing and transmitting a data message for transmitting the publication information.
3. The method of claim 2,
The general rendezvous node is
An NDN-based communication system that stores the topic information included in the topic message and delivers it to the topic rendezvous node.
3. The method of claim 2,
The general rendezvous node is
Upon receiving the data message, it is checked whether topic information corresponding to the data message exists,
An NDN-based communication system for requesting the topic information from the topic rendezvous node in response to the existence of the topic information.
5. The method of claim 4,
The general rendezvous node is
As topic information corresponding to the data message exists, an NDN-based communication system for storing and managing the publication information in consideration of the topic information.
According to claim 1,
The topic rendezvous node is
the topic information;
An NDN-based communication system for storing and managing the storage option information for each data.
According to claim 1,
The general rendezvous node is
the publication information;
An NDN-based communication system for storing and managing the storage option information for each data.
3. The method of claim 2,
The at least one general rendezvous node is
a first general rendezvous node located in the first region and a second general rendezvous node located in the second region;
In the first region, the at least one publisher node that was connected to the first general rendezvous node transmits the data message to the second general rendezvous node as it moves to the second region.
In a method for processing data in a named data networking (NDN)-based communication system,
generating, by at least one publisher node, topic information including a topic of content and publication information including data of the content, and publishing the content using the topic information and publication information;
the at least one general rendezvous node receiving the topic information from the at least one publisher node and transmitting the topic information to the topic rendezvous node;
a process in which the at least one topic rendezvous node stores and manages the topic information;
receiving and storing, by the at least one general rendezvous node, the publication information from the at least one publisher node;
A process in which at least one subscriber node generates and transmits a subscription request for the content;
and providing, by the at least one general rendezvous node, the data of the content corresponding to the subscription request to the at least one subscriber node.
10. The method of claim 9,
The process of receiving and storing the publication information is,
upon receiving the data message including the publication information, confirming whether topic information corresponding to the data message exists;
and requesting the topic information from the topic rendezvous node in response to the existence of the topic information.
11. The method of claim 10,
The process of requesting the topic information from the topic rendezvous node in response to the existence of the topic information includes:
and storing and managing the publication information in consideration of the topic information as topic information corresponding to the data message exists.
According to claim 1,
The process of storing and managing the topic information is,
the topic information;
An NDN-based data subscription method for storing and managing the data-specific storage option information.
According to claim 1,
The process of receiving and storing the publication information is,
the publication information;
An NDN-based data subscription method for storing and managing the data-specific storage option information.
10. The method of claim 9,
the at least one general rendezvous node includes a first general rendezvous node located in a first area and a second general rendezvous node located in a second area;
In the first region, when the at least one publisher node that was connected to the first general rendezvous node is moved to the second region, the at least one publisher node sends the data message to the second general rendezvous node. transmission process and
When the second general rendezvous node receives the data message including the publication information, checking whether topic information corresponding to the data message exists;
and requesting the topic information from the topic rendezvous node in response to the existence of the topic information.

Images