KR101041587B1 - Sensor network system which supports multi-hop routing between cluster heads and routing method thereof - Google Patents

Abstract

A cluster-based sensor network system and routing method are provided that support multi-hop routing between cluster heads. The cluster-based sensor network system supporting multi-hop routing between cluster heads according to the present invention generates a virtual routing message by adding a virtual routing message header to an original message having a cluster member node included in its own sensor network as a receiver. A sink node for transmitting to the head node of the cluster member node, and a cluster head node for extracting the original message from the received virtual routing message and transmitting the original message to a cluster member node designated as a receiver of the original message. .

Sensor network, multi-hop, clustering, cluster member, network lifetime

Description

Sensor-based network system which supports multi-hop routing between cluster heads and routing method

The present invention relates to a cluster-based sensor network system and a routing method supporting multi-hop routing between cluster heads. More specifically, in a sensor network composed of one or more clusters communicating with an external device through a sink node, when the message is transmitted to a cluster member node constituting the cluster rather than a cluster head node representing the cluster, the entire network It relates to a sensor network system and a routing method for delivering the message in a unicast manner only to the cluster member nodes instead of the method of broadcasting the message.

The clustering protocol for sensor networks is being studied to increase the energy efficiency and overall survival of the network by configuring nodes of the sensor network in a hierarchical structure. The clustering protocol combines physically adjacent nodes into a cluster and separates sensor nodes into cluster head nodes, which are representative of the cluster, and cluster member nodes that participate in the cluster. Layered. The clustering protocol improves the energy efficiency of the sensor network by reducing the amount of data transmitted by the cluster head by merging the data of cluster members.Each sensor node distributes energy evenly through periodic reclustering. It has the effect of increasing the survival time of the sensor network.

In the clustering structure of the sensor network, data transmission and reception between the cluster head node and the sink node relaying communication between the sensor network and the foreign network is essential. The communication method between the cluster head node and the sink node includes a method in which the cluster head nodes directly communicate with the sink node as shown in FIG. 1 and multi-hop routing between the cluster head nodes as shown in FIG. 2. There may be a method of communicating with the sink node through.

The method in which the cluster head nodes directly communicate with the sink node has a problem in that it is difficult to apply the actual size of the sensor network because all cluster head nodes should be able to communicate directly with the sink node. On the other hand, a method of communicating with a sink node through multi-hop routing between cluster head nodes can be applied regardless of network size.

Conventional cluster-based sensor networks focus only on delivering data from sensor nodes that sense the environment to the sink node. Therefore, in order to transmit a control message from a sink node to a cluster member node in a cluster, the message must be flooded or broadcasted throughout the network. This is because the sink node does not have routing information for the cluster member node.

The control message transmission method using the floating or broadcasting method can accurately transmit the control message to the corresponding cluster member node, but it causes a lot of traffic in the network to reduce network survival time by consuming energy of sensor nodes. There is this.

SUMMARY OF THE INVENTION The present invention has been made in an effort to solve the above-described problems of the prior art. When a message is transmitted to a cluster member node, the present invention is directed to only the cluster member node instead of a method of broadcasting the message to the entire network. To provide a sensor network system and a routing method for delivering the message in a cast manner.

The technical problems of the present invention are not limited to the above-mentioned technical problems, and other technical problems not mentioned will be clearly understood by those skilled in the art from the following description.

According to an aspect of the present invention, a cluster-based sensor network system that supports multi-hop routing between cluster heads according to an aspect of the present invention provides a virtual routing message to an original message having a cluster member node included in its sensor network. The original message is extracted from the sink node for generating a virtual routing message including a header and transmitted to the head node of the cluster member node and the received virtual routing message, and the original message is assigned to the cluster member node designated as a receiver of the original message. It includes a cluster head node sending a message.

According to another aspect of the present invention, a method for routing a cluster-based sensor network system supporting multi-hop routing between cluster heads includes an original message having a cluster member node included in its own sensor network as a receiver. Generating a virtual routing message with a virtual routing message header and transmitting it to a head node of the cluster member node, extracting the original message from the received virtual routing message, and sending the original message to a cluster member node designated as a receiver of the original message. Transmitting the original message.

According to the present invention as described above, the sink node transmits a message to a specific cluster member node of the sensor network in a unicast manner rather than flooding or broadcasting, thereby reducing the amount of traffic and reducing power consumption of each node. It has the effect of increasing the survival time.

Advantages and features of the present invention, and methods for achieving them will be apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but can be implemented in various forms. The embodiments of the present invention make the posting of the present invention complete and the general knowledge in the technical field to which the present invention belongs. It is provided to fully convey the scope of the invention to those skilled in the art, and the present invention is defined only by the scope of the claims. Like reference numerals refer to like elements throughout.

Hereinafter, a configuration and operation of a cluster-based sensor network system supporting multi-hop routing between cluster heads according to an embodiment of the present invention will be described with reference to FIG. 3.

First, an initial state of a cluster-based sensor network system supporting multi-hop routing between cluster heads according to the present embodiment will be described with reference to the detailed diagram of (a) initial stage shown in FIG. 3.

The cluster-based sensor network system supporting multi-hop routing between cluster heads according to the present embodiment may include a sink node 300, cluster head nodes 302 and 304, and a cluster member node 306.

The sink node 300 generates a virtual routing message in which a virtual routing message header is added to an original message of a cluster member node included in its jurisdiction sensor network, and transmits the virtual routing message to a head node of the cluster member node. The original message may be generated by the sink node 300 directly or provided from an external network.

Cluster head nodes 302 and 304 extract the original message from the received virtual routing message and send the original message to a cluster member node designated as the recipient of the original message.

The cluster member node 306 transmits and receives data through the cluster head node 304 that manages the cluster to which it belongs.

Hereinafter, the operation of the sensor network system according to the present embodiment will be described on the assumption that the sink node intends to transmit data to the cluster member node 306 belonging to the cluster B which is the jurisdiction cluster of the cluster head node 304.

The sink node 300 stores a routing table. The routing table stores data necessary for transmitting a message in a multi-hop manner to each cluster head node 302 or 304 included in the sensor network. The routing table stores identification information of each cluster head node and next hop information for transmitting a message to each cluster head node.

For example, as shown in FIG. 3, in order to send a message to the cluster head node 304 that manages the cluster B, the identification information of the cluster head node 304 is queried in the routing table, and then the corresponding message is transmitted. A message may be sent to the node according to the next hop information. This method of routing will be referred to as multihop routing hereinafter.

The sink node 300 also stores a virtual routing table. The virtual routing table includes identification information of all cluster member nodes and jurisdiction cluster head nodes included in the jurisdiction sensor network. As shown in FIG. 3, 3 which is identification information of the cluster member node 306 and 2 which is identification information of the jurisdiction cluster head node of the cluster member node 306 may be stored in the virtual routing table.

Identification information of the cluster member node and identification information of the jurisdiction cluster head node included in the virtual routing table may be received from the cluster head node. That is, the identification information of the cluster member node may be transmitted to the sink node by a cluster head node that manages the cluster to which the cluster member node is joined.

When the jurisdiction cluster head node adds a new cluster member node to its cluster, the jurisdiction cluster head node transmits a cluster membership message including the identification information of the added cluster member node and its identification information to the sink node, and the sink node. When the node receives the cluster member subscription message, the node may add the cluster member identification information and the cluster head identification information included in the cluster member subscription message to the virtual routing table.

For example, when the cluster member node 306 is newly joined, the cluster head node 304 updates its own routing table for the newly joined cluster member node 306 and identifies the cluster member node 306's identification information. And the cluster member join message including its identification information to the sink node 300, and the sink node 300 receiving the cluster member join message receives the cluster member join message 306 in the virtual routing table. The identification information of and the identification information of the cluster head node 304 that is the jurisdiction cluster head node may be matched and stored.

On the other hand, when the cluster head node identification information of the cluster member node designated as the receiver of the original message does not exist in its routing table, the cluster head node includes the cluster member node including the identification information of the cluster member node and its identification information. A message may be sent to the sink node. In this case, when receiving the cluster member withdrawal message, the sink node may delete the cluster member identification information and the cluster head identification information included in the cluster member withdrawal message from the virtual routing table.

Next, the structure of the original message to be transmitted to the cluster member node 306 will be described with reference to the detailed drawings of '(b) the original message to be transmitted to the cluster member' shown in FIG. 3. The original message may include a message type, receiver identification information, and sender identification information. Of course, the original message may further include a message payload. The message type field is used to identify the type of message. That is, the message type field is determined according to the type of message at the time of message transmission, and may be referred to for determining the message processing method of the receiving node when the message is received at the receiving node. However, it is preferable that an intermediate transit node other than the receiving node does not query the value of the message type field.

Next, a routing operation of the sink node 300 for transmitting a message to the cluster member node 306 will be described with reference to the detailed diagram of '(c) routing of the virtual routing message' shown in FIG. 3. .

The sink node 300 queries the routing table of the sink node 300 by using '3', which is identification information of the receiving node, as a key. Since the receiving node is a cluster member node, not a cluster head node, the identification information of the receiving node will not be queried in the routing table of the sink node 300.

The sink node 300 then inquires the identification information of the receiving node in the virtual routing table of the sink node 300. As a result, if the identification information of the receiving node is found, it means that the receiving node is a cluster member node. On the other hand, if the identification information of the receiving node is not found in the virtual routing table, it means that the receiving node is a node that does not exist in the sensor network, so that the sink node 300 may provide an error message.

In FIG. 3, since a message is transmitted to the cluster member node 306 belonging to the cluster B, identification information of the receiving node is queried in the virtual routing table of the sink node 300. When the identification information of the receiving node is inquired in the virtual routing table, that is, when it is determined that the receiving node is a cluster member node, the sink node 300 adds a virtual routing message to which the virtual routing message header is added to the original message to be transmitted. Create

The virtual routing message header is preferably configured in the same format as the header of the original message. The header of the original message means data excluding the payload of the original message, and the header of the virtual routing message also uses the same format as the header of the original message. Can be routed by

The virtual routing message header may include a virtual message type field, a virtual receiver field, and a virtual receiver field. The virtual message type field is set to a virtual routing type, and the virtual receiver field is head node identification information of the cluster member node queried in the virtual routing table using identification information of the cluster member node that is a receiver of the original message. Will be set to.

Referring to the detailed diagram of '(c) routing of the virtual routing message' shown in FIG. 3, the virtual receiver field of the virtual routing message header includes the cluster head node of the cluster B to which the cluster member node 306 as the receiving node belongs. An identification information '2', which is 304, is set, and an '0', which is identification information of the sink node 300, is set in the virtual sender field of the virtual routing message header.

The virtual routing message will also include the header of the original message. The virtual routing message may also include a payload of the original message.

The sink node 300 transmits the virtual routing message in a multi-hop manner. Since the virtual routing message header included in the virtual routing message has the same format as the header of the general message, the cluster header node 302 via the virtual routing message can route the virtual routing message in a general multi-hop manner. have. As mentioned above, the cluster header node 302, which is not the receiving node of the virtual routing message, preferably does not query the message type.

That is, the virtual routing message including the message that the sink node 300 wants to send to the cluster member node 306 is transmitted through the cluster head nodes by a general multi-hop method, so that the cluster member node 306 which is the receiver of the message is sent. A cluster head node 304 may be reached that governs the joined cluster.

Next, the operation of processing the virtual routing message by the cluster head node 304, which is the receiving node of the virtual routing message, is detailed for '(d) the cluster header sends the original message to the cluster member' shown in FIG. It will be described with reference to the drawings.

The cluster head node 304 receives the virtual routing message, determines that the recipient identification information matches its own, and queries the value of the virtual message type field included in the virtual routing message. Since the value of the virtual message type field of the virtual routing message is set to a virtual routing type, the cluster head node 304 may recognize that the received message is a virtual routing message rather than a general message. do.

The cluster head node 304 extracts the original message by removing the virtual routing message header from the received virtual routing message. As a result, as shown in the detailed diagram of '(d) the cluster header sends the original message to the cluster member' shown in FIG. 3, it can be seen that the identification information of the receiving node is '3'.

The cluster head node 304 transmits the original message to a receiving node in which '3' is set as identification information by referring to its own routing table.

If the identification information of the receiving node included in the original message is not found in its own routing table, the cluster head node 304 determines that the receiving node has left the cluster and sends the cluster leaving message to the sink node ( 300).

The message transmission method is preferably a unicast method with one receiver.

Hereinafter, a routing method of a cluster-based sensor network system supporting multi-hop routing between cluster heads according to another embodiment of the present invention will be described with reference to FIGS. 4 and 5. First, a method of determining the type of a receiving node and transmitting a message will be described with reference to FIG. 4.

A virtual routing table including identification information of all cluster member nodes included in the sensor network and identification information of the corresponding cluster head node is stored in the sensor node relaying data transmission and reception of the sensor network (S400).

Identification information of all cluster member nodes and identification information of a jurisdiction cluster head node included in the sensor network constituting the virtual routing table may be received from the jurisdiction cluster head node. That is, when the sink node receives the identification information of the cluster member node and the identification information of the jurisdiction cluster head node, it is preferable to store the identification information of the cluster member node and the identification information of the jurisdiction cluster head node in the virtual routing table. Do.

Hereinafter, an operation in which the virtual routing table is updated according to a change in cluster subscription status of a cluster member node will be described.

When a new cluster member node is added, a cluster member join message including identification information of the added cluster member node and identification information of a cluster head node that manages the cluster to which the cluster member node is added is sent to the sink node; The sink node adds the cluster member identification information and the cluster head identification information included in the received cluster member subscription message to the virtual routing table.

On the other hand, when the cluster member node is relocated from the cluster when the position of the cluster member node is changed or the power is turned off, the competent cluster head node detects this and the cluster member including the identification information of the withdrawn cluster node and its head node. An exit message may be sent to the sink node.

In addition, when the identification information of the cluster member node designated as the recipient of the original message does not exist in its routing table, the cluster member withdrawal message including the identification information of the cluster member node and its identification information is sent to the sink node. Can be sent. That is, the jurisdiction cluster head node may transmit the cluster member withdrawal message when the receiving node of the message transmitted from the sink node does not exist in its jurisdiction cluster.

The sink node deletes the cluster member identification information and the cluster head identification information included in the received cluster member withdrawal message from the virtual routing table.

When the sink node receives a message for receiving a specific node inside the sensor network from the external network as a receiver, or generates a signal to be provided to a specific node inside the sensor network, for example, a control signal (S402), the sink node receives the receiving node. Inquiry whether the identification information exists in the routing table (S404). The message to be transmitted by the sink node is referred to as an original message.

As a result of the inquiry (S404), when the identification information of the receiving node exists in the routing table, since the receiving node is a cluster head node (S405), the sink node transmits the message by a general multi-hop routing method (S414). .

As a result of the inquiry S404, when the identification information of the receiving node does not exist in the routing table, the sink node inquires again the identification information of the receiving node in the virtual routing table (S406).

If the identification information of the receiving node does not exist in the virtual routing table as a result of the inquiry (S406), since the receiving node is a node that does not exist inside the sensor network (S410), the sink node may generate an error message (S416). have.

As a result of the inquiry (S406), when the identification information of the receiving node exists in the virtual routing table, since the receiving node is a cluster member node (S408), the sink node refers to the cluster member node that is the receiving node by referring to the virtual route table. Send the original message (S412).

Hereinafter, an operation in which the sink node transmits the original message to the cluster member node will be described in detail with reference to FIG. 5.

The sink node queries the identification information of the cluster head node for the cluster member node that is the message receiver in the virtual routing table (S500).

In operation S502, a virtual routing message including a virtual routing message header is added to an original message having a cluster member node included in its sensor network. The format of the virtual routing message header is preferably the same as the format of the header of the original message.

The virtual routing message header includes a virtual message type field and a virtual receiver field, wherein the virtual message type field is set to a virtual routing type, and the virtual receiver field indicates identification information of the cluster member node that is a receiver of the original message. It may be set to the head node identification information of the cluster member node inquired in the virtual routing table.

When the sender field is included in the original message header, the sender field is preferably included in the virtual routing message header. Identification information of a node included in a sensor network may be set in the sender field or the receiver field. The identification information may be data that can uniquely identify a node included in the sensor network.

The sink node transmits the virtual routing message in a multi-hop manner (S504). The virtual routing message may be transmitted from the sink node directly to the cluster head node of the receiving node by a multi-hop method, or may be transmitted directly to the cluster head node of the receiving node via one or more cluster head nodes. When the virtual routing message passes through the cluster head node, the cluster head node multiplies the virtual routing message when the reception node identification information of the receiver field included in the virtual routing message header does not match its identification information. It is preferable to only route in a hop manner and not to query the virtual message type field. By the series of operations, the virtual routing message may be transmitted to the cluster head node of the receiving node by a general multi-hop routing scheme.

The cluster head node of the receiving node that has received the virtual routing message checks the type of the message since the receiving node identification information of the receiver field included in the virtual routing message header matches its identification information (S506). Since the cluster head node of the receiving node that receives the virtual routing message is set to a virtual routing type, unlike the general message, the cluster head node removes the virtual routing message header and extracts an original message to be provided to the receiving node. (S508).

The cluster head node of the receiving node that receives the virtual routing message transmits the original message to the receiving node by referring to its routing table (S510). The cluster head node of the receiving node that receives the virtual routing message may transmit the cluster member leave message to the sink node when the identification information of the receiving node is not found in its routing table.

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, You will understand. Therefore, it should be understood that the embodiments described above are exemplary in all respects and not restrictive.

1 is a clustering structure diagram of a sensor network in which cluster head nodes communicate directly with a sink node.

2 is a clustering structure diagram of a sensor network in communication with a sink node through multi-hop routing between cluster head nodes.

3 is a block diagram of a cluster-based sensor network system supporting multi-hop routing between cluster heads according to an embodiment of the present invention.

4 is a first flowchart of a routing method of a cluster-based sensor network system supporting multi-hop routing between cluster heads according to an embodiment of the present invention.

5 is a second flowchart of a routing method of a cluster-based sensor network system supporting multi-hop routing between cluster heads according to an embodiment of the present invention.

Claims (18)

A sink node for generating a virtual routing message including a virtual routing message header to an original message of a cluster member node included in its own sensor network, and transmitting the virtual routing message to a head node of the cluster member node; And It supports multi-hop routing between cluster heads including a cluster head node that extracts the original message from the received virtual routing message and sends the original message to a cluster member node designated as a receiver of the original message. The sink node supports a multi-hop routing between cluster heads storing a virtual routing table including identification information of all cluster member nodes included in the jurisdiction sensor network and identification information of the jurisdiction cluster head node. . The method of claim 1, The virtual routing message header, A cluster-based sensor network system supporting multi-hop routing between cluster heads configured in the same format as the header of the original message. delete The method of claim 1, The virtual routing message header, And a virtual message type field and a virtual receiver field, wherein the virtual message type field is set to a virtual routing type, and the virtual receiver field is set using the identification information of the cluster member node that is the receiver of the original message. A cluster-based sensor network system supporting multi-hop routing between cluster heads set as head node identification information of the cluster member nodes queried in. The method of claim 1, The identification information of the cluster member node and the identification information of the jurisdiction cluster head node included in the virtual routing table support multi-hop routing between cluster heads received from the jurisdiction cluster head node. The method of claim 5, The jurisdiction cluster head node, When adding a new cluster member node to its own cluster, multi-hop routing between cluster heads that sends a cluster membership message including the identification information of the added cluster member node and its identification information to the sink node is supported. Cluster-based sensor network system. The method of claim 6, The sink node, When receiving the cluster member subscription message, the cluster-based sensor network system supporting multi-hop routing between cluster heads to add the cluster member identification information and the cluster head identification information included in the cluster membership message to the virtual routing table. . The method of claim 5, The cluster head node, If the identification information of the cluster member node designated as the recipient of the original message does not exist in its routing table, transmitting a cluster member withdrawal message including the identification information of the cluster member node and its identification information to the sink node. Cluster-based sensor network system that supports multi-hop routing between cluster heads. The method of claim 8, The sink node, A cluster-based sensor supporting multi-hop routing between cluster heads that deletes the cluster member identification information and the cluster head identification information included in the cluster member exit message from the virtual routing table when the cluster member exit message is received; Network system. Storing, by the sink node, a virtual routing table including identification information of all cluster member nodes included in the jurisdiction sensor network and identification information of the jurisdiction cluster head node; Generating, by the sink node, a virtual routing message including a virtual routing message header to an original message of a cluster member node included in its sensor network, and transmitting the virtual routing message to a head node of the cluster member node; And Extracting the original message from the received virtual routing message by the head node of the cluster member node, and transmitting the original message to the cluster member node designated as the receiver of the original message. Routing method for supporting cluster-based sensor network systems. 11. The method of claim 10, The virtual routing message header, A routing method of a cluster-based sensor network system supporting multi-hop routing between cluster heads configured in the same format as the header of the original message. delete 11. The method of claim 10, The virtual routing message header, And a virtual message type field and a virtual receiver field, wherein the virtual message type field is set to a virtual routing type, and the virtual receiver field is set using the identification information of the cluster member node that is the receiver of the original message. A routing method of a cluster-based sensor network system that supports multi-hop routing between cluster heads, which is set as head node identification information of the cluster member nodes inquired at. 11. The method of claim 10, The storing of the virtual routing table may include: When the identification information of the cluster member node and the identification information of the jurisdiction cluster head node are received from the jurisdiction cluster head node, storing the identification information of the cluster member node and the identification information of the jurisdiction cluster head node in the virtual routing table. Routing method of a cluster-based sensor network system that supports multi-hop routing between cluster heads including. The method of claim 14, When a new cluster member node is added, a cluster member join message including identification information of the added cluster member node and identification information of a cluster head node that manages the cluster to which the cluster member node is added is transmitted to the sink node. The routing method of a cluster-based sensor network system supporting multi-hop routing between cluster heads, further comprising the steps. The method of claim 15, Routing of the cluster-based sensor network system that supports multi-hop routing between cluster heads further comprising the step of adding the cluster member identification information and the cluster head identification information included in the received cluster member subscription message to the virtual routing table. Way. The method of claim 14, If the identification information of the cluster member node designated as the recipient of the original message does not exist in its routing table, a cluster member withdrawal message including the identification information of the cluster member node and its identification information is transmitted to the sink node. The routing method of a cluster-based sensor network system supporting multi-hop routing between cluster heads, further comprising the steps. The method of claim 17, Deleting the cluster member identification information and the cluster head identification information included in the received cluster member withdrawal message from the virtual routing table further comprises: routing of a cluster-based sensor network system supporting multi-hop routing between cluster heads Way.

Images