KR101074126B1 - Method of configuration management for wireless sensor network - Google Patents

Abstract

The present invention relates to a sensor network, and more particularly, to a method for managing a node configuration of a wireless sensor network, the method comprising: receiving a connection establishment report message transmitted from a node connected to the sensor network, and a node included in the connection establishment report message; Storing the relevant address information in an internal database, checking a group ID (Identifier) designating a node type among the node related address information, requesting node related collection information suitable for the node group, and responding to the request. And storing the transmitted node-related collection information in an internal database, and displaying and outputting the status of nodes connected to the sensor network based on the node-related collection information.

Sensor, network, extended address.

Description

How to manage node configuration in sensor network {METHOD OF CONFIGURATION MANAGEMENT FOR WIRELESS SENSOR NETWORK}

The present invention relates to a sensor network, and more particularly, to a node configuration management method of a wireless sensor network.

The present invention is derived from a study conducted as part of the IT source technology development project of the Ministry of Knowledge Economy and the Ministry of Information and Communication Research and Development. [Task management number: 2008-F-053-01, Task name: QoS and scalability support (S -MoRe) Sensor network advancement technology development (standardized connection)].

Wireless sensor network technology spreads sensor nodes with computing power and wireless communication ability in natural environment or battlefield to form autonomous network, and sends and receives sensing information obtained from wireless network to each other to monitor and control remotely through network. As a technology that can be utilized.

The wireless sensor network is a core technology that forms the basis of the ubiquitous network, and is widely used in various applications such as environmental monitoring, medical systems, telematics, home networks, and logistics systems. Wireless sensor network technology helps to identify or improve the living environment through various sensors, and is focused on providing better services through various applications.

In order to provide better service and provide various functions through the wireless sensor network, the operation and management of the sensor network should be preceded above all. In particular, due to the characteristics of the wireless sensor network, it is scattered on the natural environment or the battlefield to form an autonomous network. Therefore, a more efficient management plan is continuously required in consideration of various network environments.

Accordingly, an object of the present invention is to configure a node of a sensor network that can reliably and efficiently manage network configuration information and information related to the location of sensor nodes in a wireless sensor network that involves frequent network configuration changes to provide various ubiquitous services. To provide a management method.

Node configuration management method of the sensor network according to an embodiment of the present invention for solving the above problems,

 Receiving a connection establishment report message transmitted from a node connected to the sensor network;

Storing node-related address information included in the connection establishment report message in an internal database;

Checking the group identifier (Identifier) designating the node type among the node-related address information and requesting node-related collection information suitable for the node group;

Storing node-related collection information transmitted in response to the request in an internal database;

And displaying and outputting the states of nodes connected to the sensor network based on the node-related collection information.

Furthermore, the node configuration management method according to another embodiment of the present invention,

The method of claim 1, further comprising: requesting to initiate node polling to monitor configuration changes and status of nodes connected to the sensor network;

Receiving a disconnection report or node status report message of a node transmitted in response to the node polling start request;

And updating the internal database according to the content of the received message.

And changing and outputting a state of nodes connected to a sensor network according to the internal database update.

In addition, in the embodiment of the present invention, if the group ID is a router or sensor node ID, the sensor list of the corresponding node is requested as node-related collection information.

If the group ID is an actuator ID, the actuator information of the corresponding node is requested as the node-related collection information.

In order to implement the above-described embodiment of the present invention, the node-related address information includes extended address information, and the extended address information includes a node having group ID information designating a node type and a unique serial number for each group ID. And ID information.

According to the problem solving means as described above, the present invention includes an extended address having a group ID that can grasp the characteristics of the node in the connection setting report message to be transmitted to the operation management server 140, the operation management server 140 The node can accurately maintain the node information by requesting each node to transmit the information related to the node through the group ID included in the received extended address and storing and managing the received information in an internal database in response to the request. In addition, there is an advantage that can easily identify the characteristics of the node and output it to the operator.

In addition, the operation management server of the present invention requests the node polling periodically and receives the request response and reflects the request response in the database, so that the configuration status and status of each node can be periodically monitored, so that the node status of each sensor network is continuously monitored. The effect that can be maintained is obtained.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, if it is determined that a detailed description of related known functions or configurations may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

1 is a block diagram illustrating a sensor network according to an embodiment of the present invention. As shown in FIG. 1, the wireless sensor network includes various sensor nodes 100 and a sink node 110 serving as a coordinator.

The sensor nodes 100 may be configured of a router, a sensor terminal node, an actuator controlled by a driving command, a mobile node, and the like according to characteristics. In the sensor network, there is a gateway 120 system that connects the IP-based network 130 and the sensor network to provide a ubiquitous application service. The gateway 120 system is interlocked with the sensor network operation management server 140 through the IP network 130. The sink node 110 of the sensor network illustrated in FIG. 1 is configured with a sensor node, an actuator node, a router node, and the like to configure a large-capacity system so that services using the sensor network can be efficiently performed.

2 illustrates a structure of extended address information allocated to each sensor node 100 according to an embodiment of the present invention. The reason for allocating the extended address information as shown in FIG. 2 to each sensor node 100 is to classify and manage the type of each node constituting the sensor network.

Referring to FIG. 2, the extended address information may have a size of 8 bytes, and among them, a group ID (2 bytes) defining a node type and a node having a unique serial number for each group. Contains an ID (2 bytes). The group ID may be classified as follows, and the extended address information is included in the connection establishment report message to be described later and transmitted to the operation management server 140 through the sink node 110.

0x0000: sink node,

0x0001: router,

0x0002: sensor node,

0x0003: actuator,

0x0004: Mobile node.

Meanwhile, the operation management server 140 receives a connection establishment report (AssocReq) message indicating that the new node 100 is connected through the gateway 120 and the sink node 110. The operation management server 140 checks whether the PAN ID, sink ID, and gateway ID included in the connection establishment report message are correct, and expands the address information of the node in the internal DB, the short address information of the node, and the parent. (parent) Stores and manages node address information. And based on the storage management information, each node constituting the sensor network is displayed to the operator through the user interface means. More detailed operation of the operation management server 140 will be described in detail with reference to FIGS. 3 to 5.

For reference, in the process in which an arbitrary node 100 is initially connected to the Sensence Network and a connection establishment report message is transmitted, priority of the parent node and the PAN ID are first given to the sink node 110 and the gateway 120. If the properness is not checked by checking the correctness, etc., the connection setup will not be performed. Although the sink node 100 and the gateway 120 check the validity of the connection configuration information, the operation management server 140 also checks the ID accuracy of each node and the validity of the parent node, the unknown PAN ID. Alternatively, when an error occurs in the gateway 120 ID, an error message is transmitted to the gateway 120 without performing a corresponding process and the status is displayed on the user interface screen.

Hereinafter, a method of managing the configuration of each node by using information of each node included in the connection establishment report message and transmitted will be described in detail with reference to the accompanying drawings.

3 to 5 are flowcharts illustrating a method for managing a node of a sensor network according to an embodiment of the present invention. More specifically, FIG. 3 is a sensor network when a node connected to the sensor network is a mobile node. FIG. 4 illustrates a management flowchart, and FIG. 4 assumes a case where a node connected to the sensor network is a sensor node, and FIG. 5 assumes a case where a node connected to the sensor network is an actuator.

Referring to FIG. 3, first, one node 100 may request a connection setup to the sink node 110 in order to be connected to a sensor network (step S1). The connection establishment request includes a part of node-related address information. A part of the node-related address information includes extended address information as shown in FIG. 2, and the extended address information has two-byte group ID information designating a node type and a unique serial number for each group ID. Contains node ID information of 2 bytes in size. In response to this request, the sink node 110 transmits a connection establishment request response containing configuration information (topology address, routing information, synchronization information, etc.) to the corresponding node 100 (step S2). In addition, when the sink node 110 transmits a connection establishment report message (AssocReq) containing node-related address information to the gateway 120 (step S3), the connection establishment report message is managed by the operation management server 140 through the IP network. It is delivered to (S4 step). As described above, the sink node 110 and the gateway 120 check the validity of the parent node and the accuracy of the PAN ID in the process of transmitting the connection establishment report message.

Meanwhile, the operation management server 140 receiving the connection establishment report message through the gateway 120 checks the validity of the PAN ID, sink ID, and gateway ID included in the connection establishment report message, and includes node-related address information (extended address). Information, short address information, parent node address information, etc.) are stored in an internal database (step S5). The storage method is a method of mapping the short addresses of the nodes belonging to the group to the group designated by the extended address. If a shortcut address of the node is stored when the node is connected, the newly updated shortcut address is updated.

The operation management server 140 storing node related address information then checks a group ID (Identifier) designating a node type among the node related address information (step S6). If the check result group ID is "0x0004" indicating a mobile node, the operation management server 140 stores only the node type in the internal database without a subsequent procedure and terminates the connection establishment reporting function. If the check result of the step S6 group ID is an ID indicating a router or sensor node, that is, "0x0001" or "0x0002", the operation management server 140 recognizes that the node is a sensor node that includes a sensor, Figure 4 Proceed to (ⓐ).

As shown in FIG. 4, when the operation management server 140 transmits a message (GetSensorList_Request) requesting a sensor list of a corresponding node as node-related collection information (step S11), the sensor list request message. The gateway 120 is transmitted to the corresponding sensor node 100 through the sink node 110 (steps S12 and S13). Accordingly, the sensor node 100 transmits a sensor list request response message (GetSensorList_Response) including the sensor list information held by the sensor node 100 to the sink node 110 (step S14). The sensor list request response message is also transmitted to the operation management server 140 through the sink node 110 and the gateway 120 (steps S15 and S16).

Upon receiving the sensor list request response message, the operation management server 140 reconstructs the sensor list by comparing the node-related collection information, that is, the sensor list with the sensor node side shortcut address already registered in the internal database, and then stores the stored information in the internal database ( Step S17). The operation management server 140 displays and outputs the state or sensor list of the sensor nodes connected to the sensor network based on the node-related collection information (step S18), so that the operator has progressed without a connection setting report of the router or the sensor node. You may be notified. In some cases, the completion status of the connection establishment report may be notified by displaying the sensor node icon or the router icon instead of the sensor list.

For reference, if there is no response to the sensor list request for a predetermined time, the operation management server 140 retries the sensor list request for a programmed number of times (for example, 3 times). If there is no response despite the retry, the operation management server 140 displays and outputs to the operator that the sensor list is not stored in the sensor node 100. If the sensing information value is transmitted from the sensor node 100 that does not respond to the sensor list request, the operation management server 140 may retry the above-described sensor list request and collect the sensor list information.

On the other hand, if the check result group ID of step S6 is an ID indicating an actuator node, that is, "0x0003", the operation management server 140 recognizes that the node is an actuator node performing an actuating function and proceeds to FIG. )do.

As shown in FIG. 5, the operation management server 140 transmits a message (GetActInfo_Request) for requesting actuator information (light driving, air purification system, etc.) of the node as the node-related collection information to the gateway 120 (S21). In step), the actuator information request message is transmitted to the corresponding actuator node 100 through the gateway 120 and the sink node 110 (steps S22 and S23). In response, the actuator node 100 transmits an actuator information request response message (GetActInfo_Response) including its actuator information to the sink node 110 (step S24). The actuator information request response message is also transmitted to the operation management server 140 through the sink node 110 and the gateway 120 (steps S25 and S26).

Upon receiving the actuator information request response message, the operation management server 140 configures the actuator information in comparison with the registered shortcut address and stores it in the internal database (step S27). And the operation management server 140 outputs the actuator information collection completion indication (step S28), the operator is informed of the information collection state of the actuator node (100).

In the actuator information collection process, if there is no response from the corresponding actuator node 100, the actuator information request may be retried as many times as programmed.

As described above, by including an extension address having a group ID capable of grasping the characteristics of the node in the connection setting report message and transmitting it to the operation management server 140, the operation management server 140 is included in the received extended address. By requesting each node to transmit the information related to the node through the group ID, and storing the received information in response to the request in the internal database, it is possible not only to accurately maintain the node information but also to facilitate the characteristics of the node. It will be able to identify and print to the operator.

On the other hand, the operation management server 140 may perform a node polling (node polling) procedure to monitor the configuration change and state of the node according to the operation policy.

6 is a diagram illustrating a node polling process of a sensor network according to an embodiment of the present invention. This node polling process is preferably repeated every programmed period.

Referring to FIG. 6, the operation management server 140 transmits a node polling start request message (StartPolling_Request) to the gateway 120 at predetermined intervals (S31). The node polling start request message is transmitted to the sink node 110 through the gateway 120 (step S32). Then, the sink node 110 transmits a node polling start request response message to the gateway 120 (step S33), and performs a polling function for determining whether to establish connection of each node (or sensor) in the sensor network (step S35). )do. If the node connection is released for a specific node as a result of polling in the sensor network (step S36), the sink node 110 forwards a disconnection report message (AssocReleaseReq) to the gateway 120 (step S37). , The disconnection report message is delivered to the operation management server 140 (step S38).

The operation management server 140 receives the disconnection report message of the nodes transmitted in response to the node polling start request and updates the internal database according to the received message content (step S39). For example, if a disconnected node (or sensor) is already connected to another router or sink node (that is, the shortcut address included in the disconnect report message is not in the group ID), then the change needs to be reflected. However, if the node (or sensor) is simply disconnected, the short address of the node is deleted from the group ID by reflecting the disconnection state.

On the other hand, if the connection of the node (or sensor) is still maintained, the sink node 100 sends a message (node status report message) for reporting status information on the node through the gateway 120 to the operation management server 140. (S40, S41 steps). Operation management server 140 updates the internal database according to the node status report message content (step S42). That is, when the same information as the previous state is received, the contents of the message are ignored, and when new state information is received, the content is reflected in the DB.

For reference, the above-described polling procedure assumes a case in which the operation management server 140 periodically requests, but periodically polls at the sink node 110 according to the state of the sink node 110 to release the connection. You can also report and report node status.

As described above, if the node polling is performed periodically, the operation management server 140 can periodically monitor the configuration change and state of each node, thereby continuously maintaining the node state of each sensor network.

Although the present invention has been described with reference to the embodiments illustrated in the drawings, this is merely exemplary, and it will be understood by those skilled in the art that various modifications and equivalent other embodiments are possible. . Accordingly, the true scope of the present invention should be determined only by the appended claims.

1 is an exemplary configuration of a wireless sensor network according to an embodiment of the present invention.

2 is an exemplary structure diagram of extended address information allocated to each sensor node 100 according to an embodiment of the present invention.

3 to 5 are flowcharts illustrating a node management method of a sensor network according to an embodiment of the present invention.

6 is a diagram illustrating a node polling process of a sensor network according to an embodiment of the present invention.

Claims (7)

Receiving a connection establishment report message transmitted from a node connected to the sensor network; Storing node-related address information included in the connection establishment report message in an internal database; Checking the group identifier (Identifier) designating the node type among the node-related address information and requesting node-related collection information suitable for the node group; Storing node-related collection information transmitted in response to the request in an internal database; And displaying and outputting the status of nodes connected to the sensor network based on the node-related collection information. The method of claim 1, further comprising: requesting to initiate node polling to monitor configuration changes and status of nodes connected to the sensor network; Receiving a disconnection report or node status report message of a node transmitted in response to the node polling start request; And updating an internal database according to the content of the received message. The method of claim 2, further comprising changing and outputting a state of nodes connected to a sensor network according to the internal database update. The method according to any one of claims 1 to 3, wherein if the group ID is a router or a sensor node ID, a sensor list of the corresponding node is requested as node-related collection information. The method according to any one of claims 1 to 3, wherein if the group ID is an actuator ID, the actuator information of the node is requested as node-related collection information. The method according to any one of claims 1 to 3, wherein if the group ID is a mobile node, the node-related collection information request step is deactivated. The node according to any one of claims 1 to 3, wherein the node-related address information includes extended address information, and the extended address information includes a node having group ID information designating a node type and a unique serial number for each group ID. Node configuration management method of a sensor network comprising the ID information.

Images