KR102067021B1 - Apparatus and method for managing of undrground utility things resource - Google Patents

Abstract

The present invention provides an apparatus and method for managing underground resources based on IoT, wherein the device checks whether a middleware core receives a sensing value report for underground assets from a sensor node and whether a global ID of a sensor node is registered according to the sensing value report. In the case of a registered global ID, an ID manager for checking whether the network ID is changed and updating network IDs matched to the global ID, and a global ID and network ID for each registered sensor node are stored. It includes a sensing DB, the sensor node obtains the sensing value from the sensor installed in the underground buried, and wirelessly transmits the sensing value report through the access point, the global ID is a unique ID for one sensor node, network ID is a sensor Access accessed by the node STE address, a (Personal Area Network) PAN address, node address sensor and the sensor address.

Description

Device and method for managing underground resource objects resource {APPARATUS AND METHOD FOR MANAGING OF UNDRGROUND UTILITY THINGS RESOURCE}

The present invention relates to an apparatus and method for monitoring the state of underground buried goods and managing things resources based on the Internet of Things (IoT).

In general, in the IoT, things resources are represented by a single ID system. Mainly, a personal area network (PAN) address area representing which area a network belongs to and an individual device address area for distinguishing each object are used as one thing ID.

In the IoT, since IoT resources use low-power wireless communication methods, when a disturbance factor occurs, a new connection is attempted to a peripheral PAN with a stronger signal. When connected to a new PAN, an address representing an individual thing resource is set to a new value according to the situation of the corresponding PAN. When the existing IoT method is applied to underground buried surveillance, it is difficult to collect and manage accurate information due to frequent ID changes due to the characteristics of underground buried surveillance which must collect information of a specific location at regular intervals.

That is, in the case of the thing devices for underground buried management, the strength of the radio signal changes frequently during the wireless connection due to radio interference caused by various vehicles and people passing over the underground buried. Therefore, the wireless communication equipment of the IoT device must frequently change the access according to the radio wave strength that changes frequently, and thus the ID change is caused by frequent PAN and device address change. As a result, there has been a problem that stable management in a service platform including middleware that has to manage things devices of underground buried is difficult.

One embodiment of the present invention is to solve the problems of the prior art, and to provide a unique underground ID for each thing device, underground underground thing resource management device and method that can stably manage the underground buried thing devices in various wireless environments To provide.

In addition, an embodiment of the present invention is to provide an underground storage object resource management apparatus and method that can always monitor and manage the status of the underground buried in consideration of various communication connection situations of the underground buried.

However, the technical problem to be achieved by the present embodiment is not limited to the technical problem as described above, and other technical problems may exist.

As a technical means for achieving the above-described technical problem, the underground buried thing resource management apparatus based on the Internet of Things according to an aspect of the present invention, the middleware core for receiving a sensing value report for the underground buried from the sensor node, the sensing value report ID manager for confirming whether or not the global ID of the sensor node according to the pre-registration, and in the case of the registered global ID, if the network ID is changed to update the network ID matching the global ID if the network ID is changed, and dictionary It includes a sensing DB that stores the global ID and network ID for each sensor node registered in the sensor node, the sensor node obtains the sensing value from the sensor installed in the underground buried, and wirelessly transmits the sensing value report through the access point, the global ID is one The only ah for the sensor nodes D, and the network identification includes a sensor node is connected to the access point address, PAN (Personal Area Network) address, node address sensor and the sensor address.

According to any one of the problem solving means of the present invention described above, it is possible to effectively manage the state of the underground facilities by issuing one unique ID for each thing device of the underground buried.

In addition, according to any one of the problem solving means of the present invention, even when the radio wave environment changes according to the complex traffic flow, the movement of people, and the parking situation in the city, the status information of the underground buried to the service platform periodically and stably through the middleware By transmitting, it is possible to effectively establish an IoT surveillance network that can proactively monitor urban settlements and settlements.

1 is a block diagram of an underground buried thing resource management system according to an embodiment of the present invention.
2 is a view for explaining a wireless communication problem applied to the underground buried thing resource management system according to an embodiment of the present invention.
3 and 4 are data flowcharts illustrating an initial registration process of an AP and a PAN according to an embodiment of the present invention.
5 and 6 are data flow diagrams illustrating an initial registration process of an underground buried object device (sensor node) according to an embodiment of the present invention.
7 and 8 are data flowcharts illustrating an initial registration process of a transducer according to an embodiment of the present invention.
9 is a data flow diagram illustrating a method for managing underground buried things resources according to an embodiment of the present invention.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted in the drawings, and like reference numerals designate like parts throughout the specification. In addition, while describing with reference to the drawings, even if the configuration shown by the same name may be different according to the drawing number, the drawing number is just described for convenience of description and the concept, features, functions of each configuration by the corresponding reference number Or the effects are not to be construed as limiting.

Throughout the specification, when a part is said to "include" a certain component, it means that it can further include other components, without excluding the other components, unless otherwise stated, one or more It is to be understood that the present invention does not exclude in advance the possibility of the presence or the addition of other features, numbers, steps, operations, components, parts, or combinations thereof.

In the present specification, the term 'unit' or 'module' includes a unit realized by hardware, a unit realized by software, and a unit realized by both. In addition, one unit may be realized using two or more pieces of hardware, and two or more units may be realized by one piece of hardware. The term 'unit' or 'module' is not limited to software or hardware, and may be configured to be in an addressable storage medium or may be configured to reproduce one or more processors. Thus, as an example, 'part' or '~ module' means components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, and the like. , Procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functionality provided within these components and the '~' (or '~') modules may be combined into smaller numbers of components and '~' (or '~' modules) or combined with additional components. It can be further separated into '~' (or '~'). In addition, the components and '~' (or '~') may be implemented to play one or more CPUs in the device or secure multimedia card.

1 is a block diagram of an underground buried thing resource management system according to an embodiment of the present invention. FIG. 2 is a diagram illustrating a wireless communication problem applied to an underground buried thing resource management system according to an exemplary embodiment of the present invention.

In FIG. 1, an example of a system for underground buried management installed in a city center is illustrated, and waterworks, sewerage, and urban railways that affect safety of underground spaces are illustrated as examples of underground buried materials. For reference, the type and location of the underground buried is not limited.

The underground storage thing resource management system 100 is a system that collects the status information of the underground storage by using IoT devices (hereinafter referred to as a thing device or a sensor node) from time to time.

As illustrated in FIG. 1, the underground buried thing resource management system 100 may include a thing device 110 that acquires a sensing value from one or more sensors 111 installed for each underground buried material, and sensing information (ie, from each of the things devices). State information for each underground buried material), and then collect the collected information and deliver it to the underground buried thing resource management device 130, and access point (Access Point, AP) 120, and state information of the underground buried material from the AP 120 Receiving and analyzing the received state information includes the underground material thing resource management device 130 for monitoring the status of the underground buried.

In this case, the underground buried thing resource management device 130 includes a middleware 131, a sensing database (DB) 132, and a data analysis module 133.

Underground storage thing resource management device 130 analyzes the status of the underground buried ground based on the state information received from each underground buried thing device 110, facilities that can monitor the environment of the underground space (an embodiment of the present invention) In the example, information from "groundwater wells" (eg, measurement information on groundwater levels in underground spaces) is also collected and analyzed.

That is, as shown in FIG. 1, the underground storage object resource management apparatus 130 according to the exemplary embodiment of the present invention is installed in the groundwater well P10 together with the state information from the thing device 110 installed for each underground installation. Environment measurement information from the sensor P11 is obtained through the AP 120. At this time, the thing device 110 for obtaining the sensing value from the sensor (P11) installed in the groundwater well (P10) and transmits to the AP 120 is further included.

Specifically, the object devices 110 for each underground buried material measure at least one of the state of the underground buried material and environmental information of the underground space through the included sensors 111 and P11. In addition, the AP 120 controls the sensors of the sensor nodes (that is, the underground device for each underground buried object), collects the sensing values of each sensor, and transmits the sensor values to the underground buried material resource management device 130. In this case, the sensor node 110 transmits data to the AP 120 through various possible wireless paths, but is transmitted to the most reliable PAN (for example, the closest PAN) among the various wireless PANs available as the wireless path. Connect and send data.

In this case, as the address values used by the sensor node 110 to transmit data, a sensor address, a sensor node address, a PAN address, and an AP address are included. In an embodiment of the present invention, a network ID is set by integrating these address values, and the network ID may be expressed as "AP address: PAN address: sensor node address: sensor address". On the other hand, the actuator (actuator) may be located in the location of the various sensors of the underground buried object resource management system 100 as needed, hereinafter such sensors or drivers are collectively referred to as a transducer. In the following description, the expressions "id" and "address" are used in the same meaning in a mixed manner.

Meanwhile, in the city center, problems in management and monitoring may occur due to the use of wireless sensor nodes in managing underground burial.

For example, in FIG. 2, a sensor such as a leak sensor or a gyro sensor is attached to a water supply pipe, a sewer pipe (ie, underground buried material), and the measured values are stored in a sensor node (ie, an object device) to manage the underground deposit. It is transmitted to the external AP 120 wirelessly through the 110.

At this time, since the ground exposure point of the water and sewage pipe is a manhole (P20), the antenna of the sensor node 110 is located on the manhole or around the manhole, and the AP 120 is located on the roof of a neighboring building or on a street lamp to cover a wide range as much as possible. Can be installed. The sensor node 110 performs wireless communication through the nearest AP 2 (120-2), but there are many parking vehicles in the city center (especially residential area, etc.), as shown in FIG. It is often possible to park a vehicle with a lot of metal in between. In this case, jamming causes communication disturbances between the sensor node 110 and the AP2 120-2. In this situation, the sensor node 110 finds another AP having a good radio signal. The sensor node 110 connects to the AP 1 120-1, which has a straight line distance from the originally connected AP 2 120-2, but has no radio interference. Communication will proceed. As the position of the parking vehicle around the manhole (P20) changes, the sensor node 110 changes the AP to be connected from time to time, and accordingly, the PAN address and the individual address to which the sensor node 110 belongs also change from time to time. Becomes difficult. In other words, IoT devices such as sensor nodes for surveillance are not easy to manage frequently after installation. Therefore, low power operation and battery usage are required for long term operation of the sensor node. However, such low power operation has a limitation on the strength of the wireless signal of the sensor node 110, and thus becomes more sensitive to the wireless signal size in communication with the AP 120, resulting in more frequent changes of the access AP.

In order to solve this problem, the underground buried thing resource management device 130 according to an embodiment of the present invention grants a global ID which is a unique ID for each sensor node 110. For reference, the global ID may be assigned to only one device in the world, and may be given so that there is no duplication at the time of manufacturing the device, or may be given in the middleware 131 of the underground object thing resource management device 130. In the embodiment of the present invention, the middleware 131 is issued. As shown in FIG. 1, the middleware 131 includes a middleware core, a middleware user interface (UI), and an ID manager.

Hereinafter, the processes from the device registration method of the underground buried thing devices through the respective components of the underground buried thing resource management device 130 to the method of safely storing the sensing value report in a situation where the sensor node is frequently changed in detail. Explain.

3 and 4 are data flowcharts illustrating an initial registration process of an AP and a PAN according to an embodiment of the present invention.

3 illustrates a procedure in which the AP and the PAN are registered in the underground object thing resource management apparatus 130 when there is a network ID previously assigned. In addition, FIG. 4 illustrates a procedure in which the AP and the PAN are registered in the underground object thing resource management apparatus 130 when there is no network ID.

Referring to FIG. 3, the AP and PAN are initially registered with the middleware 131 of the underground storage object resource management device 130 in a state where a unique network ID has already been given, even though the AP and PAN have a network ID. The case where these information is not stored in the sensing DB 132 will be described.

First, when the AP and the PAN transmit a registration request to the middleware 131 of the underground buried thing resource management device 130 (S301), the middleware core has a network in which an address according to the registration request is already stored in the sensing DB 132. Check if it is ID. In this case, the middleware core transmits a network ID confirmation request to the ID manager (S302), and the ID manager transmits a request for checking whether the ID is a registered ID in the sensing DB (S303).

For reference, the sensing DB 132 includes a previously registered AP address, PAN address, sensor node address, sensor address, network ID corresponding to the reported status information and environmental information, and globally issued by the ID manager for each sensor node. ID is stored.

Next, the sensing DB transmits a response to the ID manager in response to the network ID registration check request (S304).

At this time, if the response is that the network ID is already stored in the sensing DB, the ID manager transmits a success response to the middleware core (S305), the middleware core receiving the change the state of the device from offline to online After that (S306), and transmits a response indicating a successful registration to the device (S307).

On the other hand, if the response received through the step (S304) is a response that the network ID is not registered in the sensing DB, the ID manager determines the registration of the network ID requested to register from the device (S308), The requested network ID and the attribute value of the corresponding device are registered together in the sensing DB (S309).

When the ID manager receives a response that the network ID registration is successful from the sensing DB (S310), the ID manager transmits a response including the network ID registered as the middleware core (S311).

The middleware core changes the state of the corresponding device from offline to online state (S312), and transmits a response indicating the successful registration to the corresponding device together with the network ID information (S313).

On the other hand, if it is necessary to manually modify the attribute values of the device stored in the sensing DB, the user may further include a procedure for modifying through the middleware UI (User Interface).

Referring to FIG. 4, when the AP and the PAN do not have a unique network ID, the AP and the PAN initially register with the middleware 131 of the underground storage object resource management device 130. The case of initial registration by granting is given.

When the AP and the PAN device do not have their own unique network ID, the network ID is given from the middleware at the first registration time of the device. In order to avoid interference with each other in wireless communication, it is safe and efficient that the PAN addresses are not duplicated through the middleware rather than the PAN coordinator by itself. Can be.

In FIG. 4, steps S401 to S407 correspond to steps S301 to S307 described above with reference to FIG. 3, and thus a detailed description thereof will be omitted.

On the other hand, if the AP and the PAN does not have a network ID assigned from the middleware, the network ID value is stored as a specific value (for example, 0) to request device registration. The first part of the procedure is the same as when registering with your own network ID. For reference, if the AP and the PAN device do not have their own unique network ID, the process of asking the sensing DB for registration may be unnecessary. However, since the case where the network ID is 0 is not registered, the unique network ID is not processed without exception handling. It is possible to share the same procedure as in the case of having the effect of simplifying the process.

In detail, the ID manager checks whether the network ID of the corresponding device is 0, generates a new network ID when 0 (S408), and requests registration of the new network ID and the attribute values of the corresponding device together with the sensing DB (S409). . For reference, upon registration response sent to the device, the new network ID is returned in a response message. Accordingly, the device attempting to register recognizes the new network ID given through the response message and utilizes it for all communication procedures (for example, when registering the device again after power-off).

For example, when generating a new network ID, the ID manager may use a method of assigning values sequentially starting from 1 and sequentially increasing by one. In addition, if a registration release message is received from the device, the ID is regarded as recovered and the collected ID is stored in the ID pool. The retrieved IDs are not used immediately, and the retrieved IDs are only available if the sequentially increasing value reaches the highest value (for example, 0xFFFF if the ID is 2 bytes, 0xFFFFFFFF if the ID is 4 bytes). Can also be taken out of the ID pool.

In addition, since steps S410 to S413 in FIG. 4 correspond to steps S310 to S313 described above with reference to FIG. 3, a detailed description thereof will be omitted.

On the other hand, according to an embodiment of the present invention, by assigning a global ID to the sensor node 110, it is possible to solve the sensing data management problem according to the change of the wireless connection environment of the sensor nodes.

Hereinafter, in an embodiment of the present invention, it is assumed that the network ID of the sensor node 110 uses a value assigned by the sensor node in the wireless sensor network. In this case, as described above with reference to FIGS. 3 and 4, the underground object thing resource management apparatus 130 may assign an address to the sensor node 110 in the same manner as in the AP or PAN. In addition, since the global ID is not easy to assign a unique value globally at the sensor node level, it is an easy method to assign the global ID to the middleware of the underground storage object resource management device 130.

5 and 6 are data flow diagrams illustrating an initial registration process of an underground buried object device (sensor node) according to an embodiment of the present invention.

FIG. 5 illustrates a procedure in which the sensor node 110 is registered in the underground object thing resource management apparatus 130 when a global ID previously assigned is present. In addition, FIG. 6 illustrates a procedure in which the sensor node 110 is registered in the underground buried thing resource management device 130 when there is no global ID previously assigned.

Referring to FIG. 5, a procedure in which the sensor node 110 receives a global ID from the middleware 131 previously and attempts to register with the middleware 131 in the state having the global ID will be described.

First, when the sensor node 110 requests the device registration with the middleware 131 of the underground object thing resource management device 130 (S501), the middleware core checks the global ID of the corresponding sensor node 110 with the ID manager. Request (S502).

Then, the ID manager sends a global ID of the sensor node 110 to the sensing DB 132 and requests confirmation whether the ID is a registered ID (S503).

Next, the sensing DB transmits a response to the ID manager in response to the global ID registration check request (S504).

In this case, when the response indicates that the global ID is already stored and registered in the sensing DB, the ID manager transmits a success response to the middleware core (S505).

Upon receiving this, the middleware core changes the state of the sensor node from offline to online state (S506), and then transmits a response indicating a successful registration to the corresponding sensor node (S507).

On the other hand, after the previous step (S504), after receiving the success response, the ID manager obtains the network ID value recorded in the sensing DB, and compares with the network ID value of the sensor node currently attempting registration.

If the two network ID values are different as a result of the comparison, this means that the sensor node is connected to another PAN due to a change in wireless connection, or a new sensor in the PAN coordinator due to timeout, even if the PAN ID remains the same. This is the case when a node address is given. Accordingly, the ID manager requests an update of the network ID stored in the sensing DB using the network ID received from the sensor node attempting to register (S508). Then, when the ID manager receives a complete response to the network ID update from the sensing DB (S509), it may transmit a success response to the sensor node. Even if the two network IDs are the same as a result of the comparison, the ID manager sends a success response to the middleware core.

On the other hand, if the response received in step S504 is a response that the global ID value is not the ID registered in the sensing DB, the ID manager stores the global ID requested from the sensor node together with the device attribute information (S510).

Then, the ID manager transfers the corresponding global ID to the sensing DB (S511) and receives a success response from the sensing DB (S512).

Next, the ID manager transmits a response including the corresponding global ID to the middleware core (S513), and the middleware core changes the state of the corresponding sensor node to an online state (S514).

The middleware core transmits a response indicating a successful global ID registration to the corresponding sensor node (S515).

On the other hand, referring to Figure 6, the sensor node has not been given a global ID in advance, or after the factory initialization to explain the process of initial registration to receive a new global ID.

First, when the sensor node 110 transmits a registration request to the middleware 131 of the underground buried thing resource management device 130 (S601), the middleware core senses the global ID according to the registration request to the ID manager. A request is made to determine whether the global ID is already stored at step S602.

In this case, when there is no global ID value, the sensor node attempts to register using a preset value (eg, 0) as an address value. This is similar to the case of registering the AP / PAN to access without its network ID value.

The ID manager requests confirmation of the pre-registration to the sensing DB 132 using the requested global ID value (S603), and the ID manager receives a pre-registration confirmation response for the corresponding global ID from the sensing DB (S604).

At this time, if the received response is a registered global ID, the ID manager transmits a success response to the middleware core (S605), and the middleware core changes the device state of the corresponding sensor node from offline to online (S606). The middleware core then transmits a device registration success response to the corresponding sensor node (S607).

On the other hand, if there is no global ID previously assigned to the sensor node, in step S602, the global ID that is the confirmation request object is 0. Therefore, in step S604, a response is received that the corresponding global ID is not a registered global ID.

Accordingly, the ID manager proceeds to the registration process of creating a new ID, generates a global ID as 'new', matches the device attribute information of the corresponding sensor node (S608), and also proceeds to register a 'new' with the sensing DB ( S609).

Next, the sensing DB transmits a success response to the ID manager as a result of registering the new global ID and the device attribute information of the corresponding sensor node (S610).

The ID manager transmits a response including the new global ID to the middleware core (S611), and the middleware core sets the state of the sensor node as a new device online (S612).

In addition, the middleware core is equipped with a 'new' global ID and transmits the response message to the sensor node (S613), so that the sensor node can use the global ID assigned from the next time.

The global ID grant and management of the sensor node of the ID manager may be performed in the same manner as the network ID grant and management of the AP / PAN described above. That is, a value that sequentially increases the global ID from 1 may be used, and may be stored in the ID pool when deregistering the used global ID. In addition, when the number of issued global IDs reaches the maximum value, the global ID value included in the ID pool may be used again as a global ID.

On the other hand, in the underground buried object resource management system 100 according to an embodiment of the present invention, one or more sensors installed in a facility that can measure the underground environment, such as underground buried or wells, the sensor node (transducer) That is, the data may be transmitted to the underground buried object device.

Hereinafter, an initial registration process of the transducer device to the underground buried thing resource management device 130 will be described with reference to FIGS. 7 and 8.

7 and 8 are data flowcharts illustrating an initial registration process of a transducer according to an embodiment of the present invention.

FIG. 7 illustrates an initial registration process when the transducer device to be registered in the underground object thing resource management device 130 has attribute information.

First, the transducer device requests the device registration to the middleware core of the underground buried thing resource management device 130 (S701).

Then, the middleware core transmits a request for confirming registration of the address (that is, network ID) according to the received registration request to the ID manager (S702), and the ID manager requests the confirmation of the registered ID for the corresponding network ID to the sensing DB. (S703).

Then, the sensing DB checks whether the corresponding network ID is stored and transmits a response to the ID manager (S704).

If a success response is received that the response from the sensing DB corresponds to the registered ID of the network ID, the ID manager transmits the success response to the middleware core (S705).

At this time, the ID manager checks the registration time at the time of the existing registration for the transducer device. If the existing registration time of the transducer device is made earlier than the fixed time (for example, the default value can be set to 5 minutes and can be changed via a configuration file) (ie the reference time range) Previously registered), the device status is changed to on-line by considering the re-registration of the same transducer (S706) and responds to the transducer device with success (S707).

On the contrary, if the ID manager checks the existing registration time of the corresponding transducer device, and there is a pre-registration within a predetermined reference time range (S708), it fails because the transducer of the same standard is considered to exist in the same sensor node (the reason is Register) to send the response to the transducer device (S709).

The transducer device receiving the registration failure message (reason: pre-registration) recognizes that a transducer of the same standard is pre-registered in the same sensor node and increases the transducer address value to a specific value (for example, 0x1000). Re-request device registration with the middleware core (S710). As such, the middleware receiving the device registration message from the transducer device attempts to register with the network ID including the increased transducer address.

The reason for determining whether there is a transducer of the same specification according to the previous registration time is that the sensor may be restarted or power-off & power-on occurs in the installation and operation of the sensor node. This is because re-registration attempts may occur even if there is only one transducer of the same specification in the node. For reference, if 5 minutes is set as the default value of the predetermined time (that is, the reference time range) as described above, in case of restarting, it is determined that restarting occurs after a longer time than 5 minutes. If there are several transducers of the same specification in the sensor node, it can be determined that all registration attempts of these transducers will be made within 5 minutes.

Meanwhile, when the response of step S704 is a response indicating a case where the network ID is not a value registered in the sensing DB, the transducer device is registered in the sensing DB based on the attribute value of the transducer device included in the registration message. do.

At this time, the ID manager registers the network ID requested for registration confirmation from the sensor node device together with the device attribute information (S711), transmits them to the sensing DB (S712), and receives a success response thereto from the sensing DB (S713). .

Then, the ID manager transmits the success response to the middleware core (S714), the middleware core changes the device state of the corresponding transducer to online and sets it (S715), and then transmits the success response to the transducer device (S716). .

On the other hand, the transducer device for underground buried monitoring is often in the form of a composite sensor equipped with a plurality of sensors. There can be as many as ten or more sensing types, in which case more than ten transducer registration messages can occur, resulting in an excessive burden on wireless sensor node communication.

In FIG. 8, the basic attribute value of the transducer ID is stored in the DB in the form of aliasing, and the initial registration process for processing only the list of the transducer ID as a single registration message without the attribute information will be described. .

Basically, the procedure is similar to the process of registering a transducer with attribute information. That is, since steps S801 to S810 in FIG. 8 correspond to steps S701 to S710 described above with reference to FIG. 7, a detailed description thereof will be omitted. For reference, when a plurality of transducer registration messages are received from the transducer in the form of a complex sensor, it may be determined whether the registration is already performed using only the first transducer ID in the transducer ID list.

On the other hand, when the ID manager receives a response from the sensing DB that the network ID of the transducer is not registered in advance in step S804, the ID manager proceeds to the new registration with the network ID according to the registration request from the transducer device, Since there is no property value according to the producer address, the property value is stored in the sensing DB as the default value. At this time, the transducer address alias table is created in the sensing DB in advance, and this value is used as a default attribute value. That is, the transducer address alias may be created and stored in the sensing DB through the middleware UI in advance.

In detail, when the ID manager determines that the ID of the transducer device is not registered, the ID manager registers the network ID according to the registration request from the transducer (S811).

At this time, since the transducer device does not have attribute information, the ID manager requests an inquiry of the alias attribute information from the sensing DB (S812), and receives a response thereto from the sensing DB (S813).

At this time, when receiving a response from the sensing DB that the alias attribute information corresponding to the transducer device exists, the ID manager requests to register the network ID of the transducer device as a new ID to the sensing DB (S814). In step S815, a successful response is received from the sensing DB.

Then, the ID manager transmits a registration success response of the transducer device to the middleware core (S816).

Accordingly, the middleware core changes the state of the transducer device online (S817), and then transmits a response including new ID information to the corresponding transducer device (S818).

On the other hand, when receiving the response from the sensing DB that the alias attribute information corresponding to the transducer device does not exist in step S813, the ID manager transmits a registration failure response to the middleware core (S819), and the middleware core The reason for the failure is transmitted to the transducer device, a failure response of which Alias is not registered (S820).

The transducer address alias table can be changed at any time, and even if the default value is registered through alias, if the attribute value needs to be changed for each transducer device later, the individual attribute value change can be performed through the middleware UI. have.

Hereinafter, referring to FIG. 9, a method of managing state information of underground buried water according to an embodiment of the present invention will be described in detail.

9 is a data flow diagram illustrating a method for managing underground buried things resources according to an embodiment of the present invention.

In FIG. 9, a method of storing and managing state information based on a global ID when a network ID is changed when reporting a sensing value through an underground buried object device (ie, a sensor node) will be described.

Even if the sensor node's wireless connection is changed so that the network ID of the sensor node is changed, it is effective not to repeat the registration process of the sensor node due to the communication burden of low power wireless communication. Therefore, the sensor node according to an embodiment of the present invention transmits only a sensing value report message even when its network ID is changed, and the middleware 131 of the underground buried thing resource management device 130 transmits a sensing value report message. Only recognize wireless connection changes.

In detail, the sensor node 110 transmits a sensing value report including a sensing value (that is, state information) obtained from a sensor installed in a basement or a sensor installed in a facility such as a well (S901).

For reference, when the sensing value is reported from the sensor node, even though the corresponding message is generated by the transducer instead of the sensor node, communication is performed using the global ID of the sensor node. That is, if the sensing value report message is generated in the transducer, the sensor node adds its global ID when passing through the sensor node.

After receiving the sensing value report of the sensor node, the middleware core of the underground buried thing resource management apparatus 130 transmits the ID to the ID manager to check whether the global ID according to the sensing value report of the sensor node is a registered ID (S902). .

Then, the ID manager requests the sensing DB 132 to check whether the global ID is registered in advance (S903), and receives a response according to whether the global ID is registered in the sensing DB (S904).

At this time, the network ID is also searched from the sensing DB to compare the network ID in the sensing value report message. If the network ID value according to the sensing value report of the sensor node is different from the network ID value registered for the global ID of the sensor node, the ID manager uses the network ID value of the sensing DB as the network ID in the sensing value report message. Update

In addition, the ID manager requests to query the transducer ID list matching the global ID of the sensor node to the sensing DB (S905).

Then, the sensing DB inquires the following (ie matched) list of transducer addresses (ie, IDs) based on the network ID value stored in the sensing DB, and sends a completion response to the ID manager. (S906).

This is to update the network ID of the transducers previously stored for the sensor node to correspond to the changed network node ID of the sensor node.

The ID manager transmits an update request to the network ID according to the sensing value report of the corresponding sensor node to the sensing DB (S907), and the sensing DB transmits the address of the corresponding sensor node and the transducer matched thereto according to the sensing value report. After updating collectively with the ID, a complete response is transmitted to the ID manager (S910).

After this process, the ID manager stores the sensing value received from the sensor node in the sensing DB (S911), and receives a completion response thereto from the sensing DB (S912).

On the other hand, as a result of comparing the network ID in the sensing value report message by also querying the network ID from the sensing DB in the step (S904), if the network ID is the same as the network ID registered in advance, the ID manager immediately steps (S911) To save the sensing value.

For reference, when sensing values of the underground buried material and the underground environment are stored in the sensing DB 132 of the underground buried thing resource management device 130, the data analysis module 133 may preset the basement based on the stored sensing values. Perform the buried condition monitoring operation. Underground buried condition monitoring operation is not limited, for example, if the status information (that is, information based on sensing values) for any underground buried material exceeds a preset threshold, The operation of outputting warning and status information can be performed.

Next, the ID manager delivers a success response when the global ID for the sensing value report is a registered ID to the middleware core (S913), and the middleware core receiving the ID sends the device status of the corresponding sensor node offline online. Change to In addition, when the network ID is changed, the sensor node of the previous network ID is displayed as absent, and the new node is displayed as a new sensor node in the online state (S914). The middleware core transmits a success response to the global ID check and the sensing value storage to the corresponding sensor node (S915).

For reference, the above-described steps S905 to S910 may be performed through the ID manager after the middleware core receives the registration confirmation response regarding the global ID.

On the other hand, if the response of step S904 is a response that the global ID is not a registered value, the ID manager transmits to the middleware core as a failure response (S916), the middleware core is a sensor whose reason is a global ID not registered to the corresponding sensor node. The value report failure response is transmitted (S917).

Through this, even if frequent wireless connection changes are made to manage underground burials, the sensor node simply reports sensing values without notifying the middleware without notifying the middleware. You can notify. At the same time, the middleware also detects changes in the network configuration, and can effectively perform network management for underground buried monitoring.

The underground buried thing resource management apparatus and method according to an embodiment of the present invention described above may be implemented in the form of a computer program stored in a medium executed by a computer or a recording medium including instructions executable by the computer. . Such recording media are computer readable media, which can be any available media that can be accessed by a computer, and includes both volatile and nonvolatile media, removable and non-removable media. In addition, the computer readable medium may include a computer storage medium, which may be volatile and implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. It includes both nonvolatile, removable and non-removable media.

Although the methods and systems of the present invention have been described in connection with specific embodiments, some or all of their components or operations may be implemented using a computer system having a general purpose hardware architecture.

The foregoing description of the present invention is intended for illustration, and it will be understood by those skilled in the art that the present invention may be easily modified in other specific forms without changing the technical spirit or essential features of the present invention. will be. Therefore, it should be understood that the embodiments described above are exemplary in all respects and not restrictive. For example, each component described as a single type may be implemented in a distributed manner, and similarly, components described as distributed may be implemented in a combined form.

The scope of the present invention is shown by the following claims rather than the above description, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included in the scope of the present invention. do.

100: underground buried object resource management system
110: sensor node (underground buried object device)
111: sensor
120: access point
130: underground buried object resource management device
P10: Well
P11: sensor
P20: manhole

Claims (9)

A middleware core receiving the sensing value report from a sensor node which acquires the sensing value from a sensor installed in the underground buried material and wirelessly transmits the sensing value report through an access point;
An ID manager for checking whether a global ID of the sensor node is pre-registered and a network ID is changed according to the sensing value report; And
It includes a sensing DB that stores the global ID and network ID for each sensor node registered in advance.
The ID manager receives a global ID confirmation request from the middleware core that receives the registration request of the sensor node, transmits a request to confirm whether the ID is a pre-registered ID to the sensing DB, and responds to a previously stored global ID. If received, transmits a success response to the middleware core, and if it is not a previously stored global ID, registers the global ID and attribute information of the sensor node in the sensing DB,
If there is no global ID previously assigned, the sensor node transmits the confirmation request by setting a global ID for confirmation request as a preset value.
When the network ID is changed, the ID manager updates the network ID value of the sensing DB with the network ID in the sensing value report message to update network IDs matching the global ID, and the transducer ID matching the global ID. Requesting a list query to the sensing DB, and the sensing DB collectively updates the address of the transducer matched with the sensor node to correspond to the network ID of the sensor node according to the sensing value report. Device.
The method of claim 1,
The global ID is a unique ID assigned to the sensor node worldwide, and is assigned by the ID manager.
Underground buried things resource management device.
The method of claim 1,
The network ID includes an access point address, a personal area network (PAN) address, a sensor node address, and a sensor address to which the sensor node is connected.
Underground buried things resource management device.
delete delete delete delete The method of claim 1,
The ID manager assigns sequentially increasing values when generating a new global ID, but uses the global ID value recovered in the ID pool when the sequentially increasing value reaches a maximum value.
Underground buried things resource management device.
The method of claim 1,
When the ID manager receives a network ID confirmation request according to a registration request of the transducer device, the ID manager determines whether the existing registration time of the transducer device is within a preset reference time range.
Underground buried things resource management device.

Images