KR102404984B1 - Method to communication in Cluster-based Information-Centric Wireless Networks - Google Patents

Abstract

The present invention relates to a cluster-based information-centric networking communication method that enables name-based communication by operating an information-centric networking mechanism in a cluster-structured WSN.
In the cluster-based information-centric networking communication method according to the present invention, in a WSN (Wireless Sensor Network) having a cluster structure having a cluster head (CH) and a plurality of CN (Child Nodes) for each cluster, different types of communication nodes are Information-centric cluster-based WSN communication is achieved by distributing content by requesting, forwarding, or responding to content using a naming system that supports data exchange between CNs, and supporting CH connection of new nodes to achieve information-centric networking. provided to support.

Description

{Method to communication in Cluster-based Information-Centric Wireless Networks}

The present invention relates to an information-centric networking communication method, and more particularly, to a cluster-based information-centric networking communication method in which an information-centric networking mechanism operates in a cluster-structured WSN to enable name-based communication.

With the development of mobile devices and high-performance networks, traffic that can be classified as content such as multimedia has increased in the network. Due to these changes in Internet traffic patterns, limitations and problems of the current TCP/IP network arise, and new future Internet structures are being studied. Among them, the most promising future Internet structure is the Information Centric Network (hereinafter abbreviated as "ICN"), and one of the implementation technologies of this ICN is the Named Data NETworking (hereinafter abbreviated as "NDN"). to be.

When requesting content in NDN, content name is used instead of IP. In other words, the focus is not on where the content is, but on what the content is. In NDN, content is requested by Content Name, and if any node has content, the content is transmitted.

In NDN, two node types request and transmit content using two packet types. The node types are Consumer and Provider, and the packet types are Interest Packet and Data Packet. In the node type, Consumer is a node that requests content, and Provider is a node that holds content. And, in the packet type, Interest Packet is a packet used by the Consumer when requesting content, and Data Packet is a packet used by the Provider to send the content when the Interest Packet is received. 1 shows the format of a general interest packet. The interest packet includes a content name in which the requested content name is registered, a selector in which a name item not described in the content name is described, and a random temporary variable to prevent routing loop problems. Contains a Nonce item. 2 is a format of a Data Packet, and the Data Packet includes a Content Name that uses the Content Name item of the Interest Packet as it is, Signature and Signed Info used for authentication and security of data itself, and a Data item that is delivered content. .

Meanwhile, all nodes in NDN have three data structures: Content Store (CS), Pending Interest Table (PIT), and Forwarding Information Base (FIB). Contents are stored in CS, information about the received Interest Packet is recorded in PIT, and information on nearby providers and contents is recorded in FIB.

3 shows an operation process when a node receives an interest packet in the NDN.

First, when the node receives the Interest Packet (S10), it first checks whether the CS, which is the content storage, has the content corresponding to the request (SS20), and if there is the content, it becomes the provider and responds with the Data Packet (S21) ). If the content is not in the CS, check the PIT to see if there has been a case where an interest packet requesting the same content has been received before (S30). In this case, the received Interest Packet is discarded (S41), otherwise the received Interest Packet is stored in the PIT (S42). On the other hand, if there is no record of receiving the Interest Packet requesting the same content from the PIT, the FIB is checked (S50). The packet is forwarded to the provider, and the PIT is updated (S51). If there are no details in the FIB, the received Interest Packet is discarded (S52). Through the above process, the Interest Packet is forwarded to the Provider.

4 shows an operation process when a node receives a data packet in the NDN.

When a node receives a data packet in the NDN (S60), it is first checked whether the CS has the same content as the received data packet (S70), and if the same content exists, the received data packet is discarded (S71). If there is no same content, check the PIT and check if there is a request for the previously received content (S80). If there is a requested record in the PIT, it is the requested content, so forward the received data packet and save it in own CS do (S81). If there is no record requested in the PIT, the received data packet is discarded (S82).

On the other hand, the information-oriented wireless sensor networking (hereinafter abbreviated as "WSN") method that has been recently studied mainly deals with interest and data packet transmission, and is used to avoid scope control, packet suppression, and broadcast storm. Various solutions such as delay timers are provided. However, these existing methods do not support a mechanism for clustering-based networking based on information-centric networking.

A cluster-based information-centric WSN requires the following functions.

(i) a new naming scheme that must prove compatibility between various types of communication nodes for content distribution, (ii) a method that can aggregate information detected from cluster member nodes before sending the sensed data to a sink node Customized naming and unified computing capabilities to nominate cluster head (CH) nodes; (iii) efficient mechanisms for association of new nodes in the network to clusters; (iv) support for moving subnodes between various clusters; v) A delivery process specifically designed for intra- and inter-cluster communication.

Therefore, in order to meet the information-centric cluster-based WSN requirements, a new NDN architecture is required to provide efficient communication between WSN nodes.

Republic of Korea Patent Publication No. 10-1726128 (Registered on April 5, 2017) Republic of Korea Patent Publication No. 10-1695577 (Registered on 2017.01.05.) Republic of Korea Patent Publication No. 10-0970999 (registered on July 12, 2010)

The present invention has been proposed to provide efficient communication between WSN nodes, and an object of the present invention is a cluster-based information-centric networking communication method to enable an information-centric networking mechanism to operate in a WSN of a cluster structure that is utilized in various fields. is to provide

A cluster-based information-oriented networking communication method according to the present invention for achieving the above object is a cluster-structured Wireless Sensor Network (WSN) having a cluster head (CH) and a plurality of CN (Child Node) for each cluster, different types Distributes content by requesting, forwarding, or responding to content using a naming system that supports data exchange between CH and CN, communication nodes of

The naming structure of the CN to support the information-oriented networking is a naming system in the form of "Node-ID/cluster-head unique name/location/type/time" (here, "Node-ID" is the ID of the CN) , "cluster-head unique name" is the name of the CH, "location" is the physical location of the CN, "type" is the data type detected (produced) by the node, and "time" is the information data detected from the sensor of the CN. means time), and the CH naming structure for supporting the information-oriented networking is named in the form of "cluster-head unique name/sink distance/cluster type/(child node or lite query)" scheme (where "cluster-head unique name" is the CH name prefix used to find the CH in a multi-hop communication scenario, "sink distance" is the distance from the CH to the sink node, and "cluster type" is the initial time of network formation. The selected cluster type, "child node or lite query", means the name of the CN to get data from or a light query).

Here, "lite query" included in the name structure of the CH is a task processed by a CH with more resources than the CN, and the components of the lite query are "task.field_comparison operator_values" separated by "_". It consists of a naming system (here, task is a task name, field is a field name, comparison operator is a comparison operator, and value is a value), so that short task components can be utilized in consideration of the limited resource properties of WSN nodes.

On the other hand, when a new node wants to join as a part of the network, the new node broadcasts an Interest packet requesting to join the CH (a); (b) determining whether or not to accept a new node as a lower node in the CH that has received the Interest packet, and responding through a data packet including its own CH information when accepting as a lower node; (c) when a new node receives a data packet from one or more CHs, determining a CH to be associated with and transmitting a "CH Association Interest" packet; Upon receiving the "CH Association Interest" packet, the CH stores the information of the CN, which is a new node, in a member collection data structure, and sends a "CH Association Data" packet to the CN to indicate that it has accepted the subscription request. Informing step (d) and; The CN receiving the "CH Association Data" packet completes the CN's own name including the CH Unique Name that has approved the subscription (e); includes.

The Interest packet transmitted in step (a) is named "CH info/node id/location/type/time" (here, "CH info" is a prefix used to indicate that the Interest packet is a CH selection request, "node" id" is the ID of the new node, "location" is the physical coordinates of the new node, "type" is the type of new node based on the data the new node detects, and "time" is the number of times the new node's data will be accessed for a specific time interval. indicates that it is possible).

In addition, the "CH Association Interest" packet transmitted in step (c) is named "CH_Association/CH Unique Name/node id/location/type/time" (here, "CH_Association" is a request for association of a new node "CH Unique Name" indicates that this field is targeting the CH mentioned by name, "node id" is the ID of the new node, and "location" is the type of new node based on the data the new node detects. , "type" indicates the type of the new node, and "time" indicates that the new node's data can be accessed during a specific time interval).

The data packet including the CH information responding in step (b) includes the CH distance from the sink node, the number of CNs already associated with the CH, the traffic load of the CH, and the unique name information of the CH itself for CH name search. do.

In addition, in step (d), the CN notifies the CN of accepting the subscription request through the "CH Association Data" packet, and then, through the synchronization process in the network, the new CN naming system "node sync message/node id/CH Unique" CN information including "Name/location/type/time" (where "node sync message" indicates a synchronization packet, "node id" is the ID of the new node, "CH Unique Name" is the CH unique name, and "location" is the physical coordinates of the new node, "type" is the type of the new node, and "time" indicates that the new node's data can be accessed during a specific time interval) to other CNs and CHs to share it.

On the other hand, when the CN moves from the joined CH to another CH, an association process for requesting to join a new CH is performed, and during the association process with the new CH, the previous CH of the CN sends an Interest packet including information of the new CH Upon receipt, the previous CH determines that the CN is no longer part of the cluster to which it belongs, and removes the name of this CN from the members-collection data structure.

Communication in such a cluster structure WSN proceeds according to a naming-based forwarding scenario within a cluster or between clusters, and the forwarding within the cluster is pull-based communication from CH to CN, CN Pool-based communication to CH, push-based communication from CN to CN is in progress, and the forwarding between clusters is multi-hop communication from CN to CN, multi-hop communication from CN to CH, and multi-hop from CH to CH communication is in progress.

In the present invention, by proposing a network structure for the information-oriented networking mechanism to operate in a cluster-structured WSN, a naming structure to be used instead of an IP address, and transmission methods of such information-oriented packets, There is an effect that can support cluster-based WSN communication.

1 is an example of the format of a conventional general interest packet,
2 is an example of a format of a conventional general Data Packet;
3 is a flowchart showing an operation process when a node receives an interest packet in NDN;
4 is a flowchart illustrating an operation process when a node receives a data packet in NDN;
5 is an example of a battlefield monitoring system using a clustering-based wireless sensor network;
6 is a flowchart illustrating a process performed when a CH according to the present invention receives a packet;
7 is a flowchart illustrating a process performed when a CN receives a packet according to the present invention;
8 is an architectural schematic diagram of CH and CN according to the present invention;
9 is an example of adding CN information to a member collection data structure according to the present invention;
10 is an example illustrating a forwarding scenario of intra-cluster and inter-cluster communication according to the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 5 shows an example of a battlefield monitoring system using a clustering-based wireless sensor network, and the necessity of the present invention will be first described through the use case of the battlefield monitoring system of FIG. 5 .

The battlefield monitoring system as in FIG. 5 requires various nodes to perform functions such as cooperative target tracking, sensitive area monitoring, data analysis, and communication. These nodes can be deployed in clusters on the battlefield and in nearby suspicious areas. The battlefield monitoring system can be used to monitor various objects, such as reconnaissance robots, tanks, and enemy movement patterns. The battlefield surveillance system also generates alerts and forwards the acquired information along with nearby friendly forces to the base station for preventive action and immediate response. This battlefield surveillance system may consist of three layers for (i) detection and monitoring, (ii) data aggregation and analysis, and (iii) data fusion. Nodes in this layer can be loosely or tightly coupled to each other for efficient monitoring, target tracking, analysis and alert generation.

In the above-mentioned use case, because WSN uses a traditional address-based communication method such as an IP address, it has a disadvantage that may cause problems in the efficiency and scalability of networking. For example, extracting vibration data from a single sensor in a battlefield surveillance system requires proactive information about the address of each sensor and the type of data each sensor generates (addressed in content/data mapping). In this case, managing the addresses and locations of all nodes in a large-scale environment (eg, an enterprise) with a large number of sensors or nodes becomes quite complex and time-consuming.

In order to solve the problems caused by the IP address-based communication method in the WSN, the present invention utilizes the NDN (Named Data Networking) communication model, which is one of the implementation methods of the ICN (Information Centric Network), but extends the existing NDN architecture This provides a named service to the nodes of the cluster-based WSN. That is, the present invention proposes an information-centric approach that enables name-based communication in a cluster-based WSN.

To this end, the present invention first provides an exchange between a resource-rich cluster head node (hereinafter abbreviated as “CH”) and a resource-limited sub-node (Child Node; hereinafter abbreviated as “CN”). It supports data and proposes a set of new naming schemes for new node associations in the network. And to achieve data aggregation and computation in resource-rich CH, we propose a custom name integration Lite Query structure. The new light query structure provides various user-defined and IoT-related constraints to further reduce the size of data generated under CH management. In addition, we propose a set of named-based forwarding mechanisms for energy-efficient intra-cluster and intercluster (multi-radio ops) communication with the goal of minimizing unnecessary packet transmission.

6 is a flowchart illustrating a process performed when a CH receives a packet according to an embodiment of the present invention, FIG. 7 is a flowchart illustrating a process when a CN receives a packet, and FIG. A schematic diagram of the architecture of CH and CN is shown.

In the present invention, in order to enable cluster-based communication in the WSN, new packet types are proposed together with the interest/data packet of the existing NDN, which will be described in detail later.

As shown in FIG. 6, when receiving a packet, the CH first checks the packet type (S110). The received packet of CH is divided into two types: (i) Contents/Query Packet and (ii) Management Packet. In the former case, CH is an existing Interest/Data packet, or is It is determined whether the packet is an interest/data packet (S120), and the packet is processed according to a corresponding packet processing pipeline (ie, an existing interest/data packet processing pipeline or a query processing pipeline) (S121) (S122).

Similarly, in the latter case, the CH checks the packet type (S130), and the CH reception management packet is divided into three types: (i) information packet, (ii) association packet, and (iii) synchronization packet. . Once the type of the packet is determined, the CH assigns the packet to the corresponding packet processing pipeline, that is, the information collection/data packet processing pipeline for information packet processing (S131), the associated packet to make an appropriate decision on the received associated packet. The packet is transferred to the processing pipeline ( S132 ) and the synchronization packet processing pipeline ( S133 ) for processing.

As in FIG. 7 , the CN first checks the packet type like the CH (S210). CN's received packet can be classified into two main types: (i) existing Interest/Data Packet (Content Packet) and (ii) Management Packet. The existing interest/data packet is processed according to the existing interest/data packet processing pipeline (S220), and in the case of the management packet, the CN further confirms the subtype (S230). When the subtype is identified, the CN performs a corresponding packet processing pipeline, that is, an information interest/data packet processing pipeline (S231) for processing information packets, an associated packet processing pipeline (S232) for appropriate decisions on the received related packet, The packet is transferred to the synchronization packet processing pipeline and processed (S232).

Hereinafter, the naming scheme used for processing such packets will be described in detail.

In the present invention, content is distributed by requesting/delivering/responding content using a naming system that supports data exchange between CH and CN, which are different types of communication nodes. At this time, the naming system of CH and CN nodes is as follows same.

< CH with CN Naming for requesting content from nodes >

(One) CN name structure ( CN Naming Structure)

The form of the namespace of the CN proposed in the present invention is the same as "Node-ID/cluster-head unique name/location/type/time".

The first part "Node-ID" is the ID of the CN, which is used during the new node association process and is used to distinguish data generated by different CNs under one CH management.

The second part "cluster-head unique name" is the name of the CH, which is used during information transfer within the cluster and is used to limit the number of duplicate packet transmissions.

The third component "location" means the physical location of the CN that can be obtained through the GPS (Global Positioning System) module installed in the node.

The fourth part "type" refers to the type of data detected (produced) by the node (eg temperature, pressure, audio, video, etc.).

The last part "time" means the time of information data sensed from the sensor of CN.

(2) CH Naming Structure

The namespace format of CH proposed in the present invention is "cluster-head unique name/sink distance/cluster type/(child node or lite query)".

The first part "cluster-head unique name" refers to the CH name prefix used to find the CH in a multi-hop communication scenario.

The second part "sink distance" means the distance from the CH to the sink node.

The third part "cluster type" is the type of cluster selected at the initial stage of network formation, and determines the type of data handled by the cluster. If, in order to accept association requests of various types of CNs, the CH may select "Heterogeneous" as the cluster type. Alternatively, the CH can select a specific cluster type (eg, temperature, scalar, audio, video, etc.) so that only CNs that generate the specified type of data are associated with the CH.

The last component "child node or lite query" can have two types of values, either containing a light query (more on that below) or specifying the name of a CN to get data from.

< WSN customized for Lite -Query structure >

Lite-query component corresponds to "child node or lite query", which is the last part of the CH name structure described above, and can only process CH nodes. The task of processing light queries is only done in CH, because CH generally has sufficient resources such as computing, storage, and battery compared to other CNs, so it can process and store the results that the query can produce. .

A light query consists of a naming scheme of "task.field_comparison operator_values", where task represents the task name, field represents the field name, comparison operator represents a comparison operator, and value represents a value.

An example of such a light query could be "tem.val_gt_25".

Each component of a light query is separated by a "_" and plays an important role in filtering the requested content (or detected data).

The first component of a light query (eg tem.val) is a combination of two dynamic keywords, where the character "." is used to separate the two keywords. Here, the first keyword indicates task names such as vibration, temperature, and pressure. Limit the size of the job name to 3 characters to compress the size of the Lite query and store 5-10 bytes in the content name. For example, task “temperature” may be defined via “tem”, while task “vibration” may be defined via “vib”. Therefore, by using 3 letters of 52 English characters (uppercase and lowercase), the structure can be extended to about 523 unique tasks. The second keyword defines field names such as date, time, NID (Node ID) or val (value). The second keyword referencing the field name can be up to 4 bytes long. These two keywords combine to form a unique dynamic keyword used to filter content. For example, "tem.time" indicates that the requested temperature data should be filtered according to the time value of this light query.

The second component of the light query structure (eg gt) is the comparison operator. For example, you can use the comparison operator "lte" (Less than or equal) to compare <Task>.<Field> values. In the above example, tem.val_gt_25 is the job name, and val_gt_25 means a request for data whose temperature value is greater than 25 degrees gt (greater than), that is, larger.

< CH Join Process >

When joining the network, a new unassociated node can choose a CH to become part of the network. In the present invention, the CH responds to the new node's cluster selection and CH Association request. This CH join process largely consists of i) CH selection step and ii) CH Association step, and is defined as follows.

(1) CH selection step

In the CH selection phase, the new node broadcasts an Interest packet named "CH info/node id/location/type/time", and the description of this name is as follows.

The first component "CH info" is a prefix used to indicate that this Interest packet is a CH selection request, and this element is used as a routing prefix to find multiple CHs in the network.

The second component "node id" is the ID of the new node, from a CH point of view this name component is variable and can take a variety of values. The CH uses this ID to distinguish the current node from other CNs, and also the generated data.

The third component "location" is the location component, the physical coordinates of the new node, and CH can be used to decide whether or not to accept the current node as a child node.

The fourth component "type" is the type of the new node based on the data (eg temperature, pressure, video, audio, etc.) generated by the new node. Like the location component, the CH uses this component to decide whether or not to accept the current node as a child node.

The last component "time" indicates that the new node's data can be accessed during a certain time interval.

As such, the hierarchical name format consists of five elements, of which only the first element is used to statically find a CH in the network, the remaining four elements are variable and their values depend on unassociated nodes. . When a CH receives an Interest packet with this name, it may or may not respond depending on its current workload. When there is no excessive work load on the CH, the CH transmits CH-related information such as the CH distance from the sink node, the number of CNs already associated with the CH, the traffic load of the CH, and the unique name of the CH itself for CH name retrieval. respond with

(2) CH association (association) step

When a new node receives a selection response from one or more CHs, it decides which CH to associate with. The CH selection decision may be based on various parameters.

① After the CN determines the CH to select, it delivers the “CH Association Interest” packet with the name “CH_Association/CH Unique Name/node id/location/type/time”. This name has the following components:

- CH_Association: Indicates that the current aggregation packet is an association request from a node that is not associated.

- CH Unique Name: The current collection packet indicates that only the CH whose name is mentioned in this field is designated.

- The remaining components of the name are the same as previously presented.

② When the CH receives the “CH Association Interest” packet, it uses the name component of this Interest packet as it is, and creates an Interest packet to retrieve data from this CN later.

③ In addition, the CH additionally stores CN information in a member collection data structure, and FIG. 9 shows an example of adding CN information to a member collection data structure. After storing this information, the CH does two things:

- Respond with Data packet to CN,

- Initiate the synchronization process on the network (detailed below).

④ The CH notifies the CN that the CH has accepted the Association request by sending the “CH Association Data” packet.

⑤ When CN receives this data packet, CN completes its own name by adding CH Unique Name as the second component.

< New CN Synchronization Process >

When the new CN completes the association process with the CH, the CH shares the new node information (eg naming scheme) with the CN and other CHs.

Another CH may further share this information with its CN. The reason for sharing this information is to allow other CH nodes and CNs to recognize the name of the new node so that it can be used to fetch content in the future. Such a synchronization process may increase in cost (ie, the number of generated packets, overhead, time delay, etc.) depending on the number of nodes participating in the process. Therefore, the scope of the synchronization process depends on the WSN application scenario, and it should be used differently according to the application requirements.

The naming scheme used for the new CN synchronization process can be defined as "node sync message/node id/CH Unique Name/location/type/time". A "node sync message" among the name components indicates that it is a sync packet. The rest of the name components are the same as previously defined and represent the information of the new node.

< CN Mobility >

The CN proposed in the present invention can move smoothly. When the CN moves from one CH to another, the join process is restarted.

During the association process with the new CH, the old CH of this CN may receive an Interest packet including the information of the new CH. Thus, the former CH assumes that this CN is no longer part of the cluster. Also, remove the name of this CN from the members-collection data structure.

If the CN is out of the communication range of the old CH, the information or association packet with the new CH may not be received by the old CH. In this case, when the association process is completed, the new CH shares information with the old CH through the synchronization process This allows the old CH to assume that the CN is out of the communication range of the old cluster and is now generating data as part of the new cluster.

< Forwarding Scenarios >

In a cluster-based WSN, communication may be intra-cluster or inter-cluster communication.

Intra-cluster communication can be divided into three subcategories: (i) CH-initiated, pull-based communication, (ii) CN-initiated, pull-based communication, and (iii) CN-initiated, push-based communication.

Similarly, inter-cluster communication can be divided into three subcategories: (i) other cluster CN forwarding, (ii) other cluster CH forwarding, and (iii) CH forwarding.

10 shows a forwarding scenario of such intra-cluster and inter-cluster communication, and a detailed description is as follows.

(1) In-cluster forwarding - CH to CN: In this case, the CH acts as a consumer and can issue interest rate packets carrying the name of the content to be retrieved from the CN one hop away. All CNs are one hop away from the corresponding CH, so only the CN that generated the data responds, while other nodes in the cluster ignore the Interest packet.

(2) Intra-cluster forwarding - CN to CH: In this case, CN acts as a consumer and CH acts as a producer. When the CH receives the Interest packet, the CH responds with a Data packet while all other nodes within the communication range of the CH remain silent.

(3) In-Cluster Forwarding (Push Scenario) - CN to CH: This mechanism is designed for push-based communication scenarios where subnodes can send data packets directly to the CH, such as in an emergency (e.g.: In the case of epidemics, car accidents), data can be attached to the interest packet. This Interest packet is broadcast from the lower node to the CH. CH responds with a Data packet to acknowledge the receipt of this Interest packet, and other sub-nodes that receive this Interest packet ignore this Interest packet.

(4) Inter-cluster forwarding - multi-hop communication (CN-CN): This mechanism is used for inter-cluster communication scenarios, where a CN can get the contents of other CNs that are members of other clusters. In this case, only CHs of consumer and producer subnodes participate in communication and act as forwarders.

(5) Inter-cluster forwarding - multi-hop communication (CN-CH): This mechanism is used to retrieve some content from the CH of another cluster in the lower node of the cluster.

(6) Inter-Cluster Forwarding - Multi-Hop Communication (CH-CH): In this scenario, a CH communicates with another CH to retrieve some content or request data based on a Lite query. For example, a data aggregation operation may be required in the CH. In this case, the CH transmits an interest packet to another CH to receive aggregated data.

As described above, the present invention proposes the following to support information-oriented cluster-based WSN communication.

(i) a new naming scheme that must demonstrate good compatibility with resource-limited and resource-rich nodes for content dissemination;

(ii) integrated computing capabilities specifically tailored for the cluster head node;

(iii) Aggregation function of information collected before data transmission to the sink node

(iv) an efficient mechanism to provide associations of new nodes in the network;

(v) support for moving child nodes between various clusters;

(vi) a delivery process specifically designed for intra- and inter-cluster communication;

The present invention can be utilized in various fields, for example, can be utilized in fields such as battlefield monitoring system, forest fire detection, smart building communication, health management monitoring, and the like.

The present invention is not limited to the above-described embodiments, and various modifications and variations can be made by those of ordinary skill in the art to which the present invention pertains within the scope of equivalents of the technical spirit of the present invention and the claims to be described below. Of course, this can be done.

Claims (10)

In a cluster structure WSN (Wireless Sensor Network) with CH (Cluster Head) and multiple CN (Child Node) for each cluster, using a naming system that supports data exchange between CH and CN, which are different types of communication nodes, A cluster-based information-centric networking communication method that distributes content by requesting, delivering, or responding to content from a CN or CH, and accepting a CH connection request from a new node in the CH to achieve information-centric networking, comprising:
The naming structure of the CN to support the information-oriented networking is a naming system in the form of "Node-ID/cluster-head unique name/location/type/time" (here, "Node-ID" is the ID of the CN) , "cluster-head unique name" is the name of the CH, "location" is the physical location of the CN, "type" is the data type detected (produced) by the node, and "time" is the information data detected from the sensor of the CN. means time), and
The naming structure of CH for supporting the information-centric networking is a naming system in the form of "cluster-head unique name/sink distance/cluster type/(child node or lite query)" (herein, "cluster-head unique "name" is the CH name prefix used to find the CH in a multi-hop communication scenario, "sink distance" is the distance from the CH to the sink node, "cluster type" is the type of cluster selected at the beginning of network formation, "child node" or lite query" means the name of the CN to get data from or a light query), but
The "lite query" included in the name structure of the CH is a task processed by the CH with more resources than the CN, and the components of the lite query are "task.field_comparison operator_values" separated by "_" (here, task is a task name, field is a field name, comparison operator is a comparison operator, and value is a value) A cluster-based information-centric networking communication method.
delete delete In a cluster structure WSN (Wireless Sensor Network) with CH (Cluster Head) and multiple CN (Child Node) for each cluster, using a naming system that supports data exchange between CH and CN, which are different types of communication nodes, A cluster-based information-centric networking communication method that distributes content by requesting, delivering, or responding to content from a CN or CH, and accepting a CH connection request from a new node in the CH to achieve information-centric networking, comprising:
The naming structure of the CN to support the information-oriented networking is a naming system in the form of "Node-ID/cluster-head unique name/location/type/time" (here, "Node-ID" is the ID of the CN) , "cluster-head unique name" is the name of the CH, "location" is the physical location of the CN, "type" is the data type detected (produced) by the node, and "time" is the information data detected from the sensor of the CN. means time), and
The naming structure of CH for supporting the information-centric networking is a naming system in the form of "cluster-head unique name/sink distance/cluster type/(child node or lite query)" (herein, "cluster-head unique "name" is the CH name prefix used to find the CH in a multi-hop communication scenario, "sink distance" is the distance from the CH to the sink node, "cluster type" is the type of cluster selected at the beginning of network formation, "child node" or lite query" means the name of the CN to get data from or a light query),
When a new node joins as part of the network and wants to become
(a) broadcasting, by a new node, an Interest packet requesting to join a CH;
(b) determining whether or not to accept a new node as a lower node in the CH that has received the Interest packet, and if accepted as a lower node, responding through a data packet including its own CH information;
(c) when the new node receives data packets from one or more CHs, determining a CH to be associated with and transmitting a "CH Association Interest"packet;
(d) After receiving the "CH Association Interest" packet, the CH stores the information of the CN, which is a new node, in a member collection data structure, and then sends a "CH Association Data" packet to the CN to request membership informing you that you have accepted it;
(e) the CN receiving the "CH Association Data" packet completes the CN's own name including the CH unique name that has approved the subscription; cluster-based information-centric networking comprising: communication method.
5. The method of claim 4,
The Interest packet transmitted in step (a) is,
Named as "CH info/node id/location/type/time" (where "CH info" is the prefix used to indicate that the Interest packet is a CH selection request, "node id" is the ID of the new node, and "location" is The new node's physical coordinates, "type" is the type of the new node based on the data it detects, and "time" indicates that the new node's data can be accessed during a specific time interval). Information-centric networking communication method.
5. The method of claim 4,
The "CH Association Interest" packet transmitted in step (c) is,
Named "CH_Association/CH Unique Name/node id/location/type/time" (where "CH_Association" indicates that this is an Association request from a new node, and "CH Unique Name" refers to the CH whose name is mentioned in this field. Indicates targeted, where "node id" is the ID of the new node, "location" is the physical coordinates of the new node, "type" is the type of the new node based on the data the new node is detecting, and "time" is the specific time interval. indicates that the new node's data can be accessed while
5. The method of claim 4,
In the data packet containing the CH information responding in step (b),
A cluster-based information-centric networking communication method, characterized in that the CH distance from the sink node, the number of CNs already associated with the CH, the traffic load of the CH, and the unique name information of the CH itself for CH name search are included.
5. The method of claim 4,
In step (d) above
After the CN notifies the CN of acceptance of the subscription request through the "CH Association Data" packet,
CN information including "node sync message/node id/CH Unique Name/location/type/time", which is a naming scheme of a new CN through a synchronization process in the network (here, "node sync message" indicates a synchronization packet, "node id" is the ID of the new node, "CH Unique Name" is the CH unique name, "location" is the physical coordinates of the new node, "type" is the type of the new node, and "time" is the name of the new node for a specific time interval. A cluster-based information-centric networking communication method, characterized in that by passing and sharing data to other CNs and CHs).
5. The method of claim 4,
When the CN moves from the joined CH to another CH,
Go through the association process to request membership in a new CH,
During the association process with the new CH, the old CH of the CN receives an Interest packet containing the information of the new CH, and the old CH determines that the CN is no longer a part of the cluster to which it belongs, so the member-collection data structure (members-collection data structure) structure), a cluster-based information-centric networking communication method, characterized in that the name of this CN is removed.
In a cluster structure WSN (Wireless Sensor Network) with CH (Cluster Head) and multiple CN (Child Node) for each cluster, using a naming system that supports data exchange between CH and CN, which are different types of communication nodes, A cluster-based information-centric networking communication method that distributes content by requesting, delivering, or responding to content from a CN or CH, and accepting a CH connection request from a new node in the CH to achieve information-centric networking, comprising:
The naming structure of the CN to support the information-oriented networking is a naming system in the form of "Node-ID/cluster-head unique name/location/type/time" (here, "Node-ID" is the ID of the CN) , "cluster-head unique name" is the name of the CH, "location" is the physical location of the CN, "type" is the data type detected (produced) by the node, and "time" is the information data detected from the sensor of the CN. means time), and
The naming structure of CH for supporting the information-centric networking is a naming system in the form of "cluster-head unique name/sink distance/cluster type/(child node or lite query)" (herein, "cluster-head unique "name" is the CH name prefix used to find the CH in a multi-hop communication scenario, "sink distance" is the distance from the CH to the sink node, "cluster type" is the type of cluster selected at the beginning of network formation, "child node" or lite query" means the name of the CN to get data from or a light query),
Cluster Structure Communication in WSN proceeds according to the forwarding scenario based on naming within or between clusters,
In the cluster forwarding, pull-based communication from CH to CN, pull-based communication from CN to CH, and push-based communication from CN to CN are in progress,
The forwarding between the clusters is a cluster-based information-oriented networking communication method, characterized in that multi-hop communication from CN to CN, multi-hop communication from CN to CH, and multi-hop communication from CH to CH is performed.

Images