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

Abstract

Provided are an apparatus for managing object resources of an underground utility based on Internet of things and a method thereof. The apparatus comprises: a middleware core for receiving a sensing value report for an underground utility from a sensor node; an ID manager for confirming whether a global ID of the sensor node according to the sensing value report is previously registered, checking whether a network ID is changed if the global ID is previously registered, and updating network IDs matched with the global ID if the network ID is changed; and a sensing DB for storing global IDs and network IDs for each sensor node registered in advance. The sensor node obtains a sensing value from a sensor installed in an underground utility and wirelessly transmits the sensing value report through an access point, the global ID is a unique ID for one sensor node, and the network ID includes an access point address to which the sensor node is connected, a personal area network (PAN) address, a sensor node address, and a sensor address. Accordingly, it is possible to effectively manage the state an underground utility by issuing one unique ID for each object device of the underground utility.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an apparatus and method for managing underground objects,

The present invention relates to an apparatus and method for monitoring the status of underground objects and managing object resources based on the Internet of Things (IOT).

Generally, the object Internet represents object resources according to a single ID system. It mainly uses a personal area network (PAN) address area representing a network to which area it belongs and a separate device address area for dividing each object into one object ID.

Since the object resource uses low-power wireless communication method in the Internet of the objects, when a factor obstructing the radio wave, a new connection is attempted with a peripheral PAN having a stronger signal. When connected to a new PAN, the address representing the individual resource is set to a new value depending on the situation of the corresponding PAN. In case of applying the existing Internet object method to underground surveillance monitoring, it is difficult to collect and manage accurate information due to the frequent change of ID due to the nature of underground burial monitoring, in which information of a specific location must be collected at regular intervals.

That is, in the case of object devices for managing underground objects, the intensity of the radio signal changes frequently due to radio interference due to various vehicles and people passing over the underground objects. Therefore, depending on the intensity of the radio signal which changes frequently, the wireless communication equipment of the object apparatus must perform frequent connection change, which results in frequent change of the ID due to the change of the PAN and the device address. As a result, there is a problem that it is difficult to perform stable management on a service platform including middleware that manages object devices of underground objects.

An embodiment of the present invention is to solve the problems of the prior art, and it is an object of the present invention to provide an apparatus and method for managing a subterranean material object resource management apparatus capable of stably managing a subterranean object apparatus in various wireless environments by assigning a unique global ID to each object apparatus .

Also, an embodiment of the present invention is to provide an apparatus and method for managing an underground buried object resource that can monitor and manage the status of underground buried materials in consideration of various communication connection situations of underground buried objects.

It should be understood, however, that the technical scope of the present invention is not limited to the above-described technical problems, and other technical problems may exist.

According to one aspect of the present invention, there is provided an apparatus for managing an underground embedded object resource based on the Internet, including a middleware core for receiving a sensing value report on a subterranean material from a sensor node, An ID manager for confirming whether or not the global ID of the sensor node is previously registered according to the global ID and for updating the network ID matched to the global ID when the network ID is changed by confirming whether or not the network ID is changed in the case of the previously registered global ID, The sensor node acquires a sensing value from a sensor installed in a subterranean basement and wirelessly transmits the sensing value report through the access point, and the global ID is transmitted to the one The only sensor node for the sensor 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 above-mentioned objects of the present invention, the state of the underground facility can be effectively managed by issuing one unique ID for each object apparatus of underground objects.

Further, according to any one of the tasks of the present invention, state information of underground objects can be periodically and reliably transmitted to a service platform through middleware even when the propagation environment changes due to a complicated traffic flow, a movement of people, It is possible to effectively construct the object Internet surveillance network which can preliminarily monitor subsidence and depression in the city center.

FIG. 1 is a block diagram of a underground buried object resource management system according to an embodiment of the present invention.
2 is a diagram for explaining a wireless communication problem applied to a underground buried object resource management system according to an embodiment of the present invention.
3 and 4 are data flow charts for explaining the initial registration process of AP and PAN according to an embodiment of the present invention.
5 and 6 are data flow charts for explaining the initial registration process of the underground object object apparatus (sensor node) according to an embodiment of the present invention.
7 and 8 are data flow charts for explaining an initial registration process of a transducer according to an embodiment of the present invention.
FIG. 9 is a data flow chart for explaining a method of managing underground objects in an underground according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings, which will be readily apparent to those skilled in the art. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly illustrate the present invention, parts not related to the description in the drawings are omitted, and like parts are denoted by similar reference numerals throughout the specification. In the following description with reference to the drawings, the same reference numerals will be used to designate the same names, and the reference numerals are merely for convenience of description, and the concepts, features, and functions Or the effect is not limited to interpretation.

Throughout the specification, when an element is referred to as "including" an element, it does not exclude other elements unless specifically stated to the contrary, But do not preclude the presence or addition of one or more of the other features, numbers, steps, operations, elements, parts, or combinations thereof.

In this specification, the term "unit" or "module" includes a unit implemented by hardware, a unit implemented by software, and a unit realized by using both. Further, one unit may be implemented using two or more hardware, or two or more units may be implemented by one hardware. On the other hand, 'to' or 'module' is not meant to be limited to software or hardware, but may be configured to be in an addressable storage medium and configured to play one or more processors. Thus, by way of example, 'a' or 'module' refers to components such as software components, object-oriented software components, class components and task components, and processes, Microcode, circuitry, data, databases, data structures, tables, arrays, and variables, as will be appreciated by those skilled in the art. It is to be understood that the functions provided in such components and portions (or modules) may be combined with a smaller number of components and / or components (or modules) (Or ' modules '). ≪ / RTI > In addition, the components and 'part' (or 'module') may be implemented to play one or more CPUs in a device or a secure multimedia card.

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

FIG. 1 shows an example of a system for underground burial management installed in a city center, and waterworks, sewerage, and urban railways, which affect the safety of an underground space, are shown as examples of underground burials. For reference, the type and burial position of the underground material are not limited.

The underground buried object resource management system 100 is a system for collecting status information of underground buried objects from time to time utilizing an Internet (IoT) device (hereinafter, referred to as object device or sensor node).

1, the underground buried object resource management system 100 includes a object apparatus 110 for obtaining a sensing value from at least one sensor 111 installed for each underground object, An access point (AP) 120 that receives the status information of the underground objects and the status information of the underground objects from the AP 120, And an underground buried object resource management device 130 for monitoring the status of the underground buried object by analyzing the received state information.

The underground object managing apparatus 130 includes a middleware 131, a sensing database (DB) 132, and a data analysis module 133.

The underground buried object resource management device 130 analyzes the state of the underground buried object based on the state information received from each underground object object device 110, (Eg, "groundwater gauging" in the example) (eg, measurement information about groundwater level in an underground space, etc.).

1, the underground buried object resource management apparatus 130 according to an embodiment of the present invention includes status information from the object apparatus 110 installed for each underground buried object, and is installed in the underground water well P10 And acquires environmental measurement information from the sensor P11 through the AP 120. [ At this time, the object device 110 further includes a sensing device 110 for acquiring a sensing value from the sensor P11 installed in the groundwater pipe P10 and transmitting the sensing value to the AP 120. [

Specifically, the object devices 110 per underground buried object measure at least one of the state of the underground buried object and the environmental information of the underground space through the sensors 111 and P11 included therein. Then, the AP 120 controls the sensors of the sensor nodes (that is, the object devices 110 according to the underground objects), and collects sensing values of the respective sensors and transmits them to the underground object resource management device 130. At this time, the sensor node 110 transmits data to the AP 120 through various possible wireless paths, and transmits the data to the most reliable PAN (for example, the closest distance PAN) among the wireless PANs available as a wireless path And transmits the data.

At this time, the address values used for the sensor node 110 to transmit data include a sensor address, a sensor node address, a PAN address, and an AP address. In an embodiment of the present invention, the address values are integrated to set a network ID. Such a network ID may be expressed as "AP address: sensor node address: sensor address ". An actuator may be positioned at various locations of various sensors in the underground object management system 100. Hereinafter, such sensors or actuators are collectively referred to as transducers. Hereinafter, for convenience of explanation, the expressions "ID" and "address" are used in the same meaning.

On the other hand, in urban areas, management and monitoring problems may occur due to the use of wireless sensor nodes in managing underground objects.

For example, in FIG. 2, sensors such as a leakage sensor and a gyro sensor are attached to a water supply pipe, a sewage pipe (that is, a subway underground), and the measured values are connected to a sensor node And is transmitted to the external AP 120 wirelessly via the AP 110. [

At this time, since the ground exposure point of the water supply and drainage pipe is the manhole P20, the antenna of the sensor node 110 is located around the manhole or the manhole, and the AP 120 is installed on the roof of the surrounding building or on the street lamp Can be installed. The sensor node 110 performs wireless communication through the AP 2 120-2 closest to the AP 2 120-2 and the sensor node 110-2 as shown in FIG. ≪ RTI ID = 0.0 > 110 < / RTI > In this case, communication obstruction occurs between the sensor node 110 and the AP2 120-2 due to radio wave interference. In this situation, the sensor node 110 finds another AP having a good radio signal and connects to the AP 1 (120-1) which is farther from the AP 2 (120-2) Communication is performed. The sensor node 110 changes the connecting AP from time to time according to the change of the position of the parked vehicle around the manhole P20 so that the PAN address and the individual address to which the sensor node 110 belongs are changed from time to time, . In other words, due to the nature of underground objects, Internet devices such as sensor nodes for monitoring are not easy to manage frequently after installation. Therefore, low-power operation and battery use are required for long-term operation of the sensor node. However, such a low power operation restricts the strength of the wireless signal of the sensor node 110, which makes it more sensitive to the wireless signal size in communication with the AP 120, resulting in a change of the access AP more frequently.

In order to solve this problem, the underground burial object resource management apparatus 130 according to an embodiment of the present invention assigns a unique global ID to each sensor node 110. For reference, the global ID is assigned to only one device in the world, and may be given without duplication in device manufacture or may be given by the middleware 131 of the underground object management device 130. [ And is issued by the middleware 131 in the embodiment of the present invention. As shown in FIG. 1, the middleware 131 includes a middleware core, a middleware UI (user interface), and an ID manager.

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

3 and 4 are data flow charts for explaining the initial registration process of AP and PAN according to an embodiment of the present invention.

FIG. 3 shows a procedure of registering in the underground object managing apparatus 130 when there is a network ID to which the AP and the PAN are assigned in advance, respectively. In addition, FIG. 4 shows a procedure of registering in the underground object managing apparatus 130 when the AP and the PAN each have no network ID.

3, when the AP and the PAN are initially registered in the middleware 131 of the underground object managing apparatus 130 in a state in which the unique network ID is already assigned, even if the AP and the PAN have a network ID The case where these pieces of information are not stored in the sensing DB 132 will be described.

First, the AP and the PAN send a registration request to the middleware 131 of the underground object resource management device 130 at step S301. The middleware core determines whether the address corresponding to the registration request is stored in the network 132 already stored in the sensing DB 132 Identify the identity. At this time, the middleware core transmits a network ID confirmation request to the ID manager (S302), and the ID manager transmits a request to confirm whether the ID is the previously registered ID in the sensing DB (S303).

For reference, the sensing DB 132 stores a pre-registered AP address, a PAN address, a sensor node address and sensor address, a network ID corresponding to reported status information and environment information, and a global ID ID is stored.

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

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

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

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

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

On the other hand, when the attribute value of the device stored in the sensing DB needs to be manually modified, the user may further modify the property through the middleware UI (User Interface).

4, when the AP and the PAN are initially registered in the middleware 131 of the underground object resource management device 130 in a state where they do not have a unique network ID, the AP and the PAN are registered in the middleware 131 through the middleware, And a case of initial registration is explained.

If the AP and the PAN device do not have their own unique network ID, then the network ID is given from the middleware at the first registration of the device. This is because PAN addresses should not be overlapped within the same radio radius in order to avoid interference with each other in wireless communication. Therefore, it is more safe and efficient for the PAN coordinator to be given not to be duplicated through the middleware, .

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

On the other hand, when the AP and the PAN do not have a network ID given from the middleware, the network ID value is stored as a specific value (for example, 0) and the device registration is requested. The first part of the procedure is the same as when registering with its own network ID. For reference, if the AP and the PAN device do not have their own unique network IDs, it may be unnecessary to ask whether the network ID is registered in the sensing DB. However, since the case where the network ID is 0 is not registered, So that the process can be simplified.

Specifically, the ID manager checks whether the network ID of the corresponding device is 0, generates a new network ID if it is 0 (S408), and requests the new network ID and the attribute of the corresponding device to register together in the sensing DB (S409) . For reference, a new network ID is returned in a response message when a registration response is transmitted to the device. Accordingly, the device attempting registration recognizes the new network ID given through the response message, and uses it for all future communication procedures (for example, when the device is registered again after power-off).

For example, when creating a new network ID, the ID manager can use a method of sequentially incrementing the IDs starting from 1, one by one. Also, if a registration cancel message is received from the corresponding device, it is regarded that the ID has been retrieved and the retrieved ID is stored in the ID pool. The IDs thus retrieved are not immediately used, and only when the sequentially increasing value reaches the highest value (for example, 0xFFFF when the ID is 2 bytes and 0xFFFFFFFF when the ID is 4 bytes) It can also be used by removing it from the ID pool.

4, steps S410 to S413 correspond to steps S310 to S313 described above with reference to FIG. 3, and therefore, detailed description thereof will be omitted.

Meanwhile, according to one embodiment of the present invention, a global ID is assigned to the sensor node 110, thereby solving the problem of sensing data management according to changes in the wireless connection environment of the sensor nodes.

Hereinafter, it is assumed that the network ID of the sensor node 110 in the embodiment of the present invention uses a value assigned by the sensor node itself in the wireless sensor network. 3 and 4, it is also possible for the underground buried object resource management apparatus 130 to assign an address to the sensor node 110 in the same manner as in the AP or PAN. Also, since the global ID is not easy to assign a unique value globally at the sensor node level, it is an easy method to be given from the middleware of the underground object management device 130. [

5 and 6 are data flow charts for explaining the initial registration process of the underground object object apparatus (sensor node) according to an embodiment of the present invention.

FIG. 5 shows a procedure of registering in the underground object managing apparatus 130 when the sensor node 110 has a global ID assigned in advance. FIG. 6 shows a procedure of registering in the underground object managing apparatus 130 when the sensor node 110 does not have a global ID previously granted.

Referring to FIG. 5, a description will be given of a case where the sensor node 110 receives a global ID from the middleware 131 and attempts to register it with the middleware 131 with a global ID.

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

In step S503, the ID manager transmits a global ID of the sensor node 110 to the sensing DB 132 to confirm whether the ID is a previously registered ID.

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

At this time, if the global ID is already stored and registered in the sensing DB, the ID manager transmits a success response to the middleware core (S505).

The middleware core receiving the response changes the state of the sensor node from off-line to online (S506), and transmits a response indicating registration success to the corresponding sensor node (S507).

On the other hand, after the preceding step S504, the ID manager obtains the network ID value recorded in the sensing DB after receiving the success response, and compares it with the network ID value of the sensor node currently attempting to register.

As a result of the comparison, if the two network ID values are different, it means that the corresponding sensor node is connected to another PAN and the PAN ID is changed, A case where a node address is given, and the like. Accordingly, the ID manager requests update of the network ID stored in the sensing DB with the network ID received from the sensor node attempting to register (S508). Then, the ID manager can transmit a success response to the sensor node when a completion response to the network ID update is received from the sensing DB (S509). As a result of the comparison, even if the two network IDs are the same, the ID manager sends a success response to the middleware core.

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

Then, the ID manager transmits the corresponding global ID to the sensing DB to request registration (S511), and receives a success response to the sensing ID 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 the online state (S514).

Then, the middleware core transmits a response indicating the success of global ID registration to the corresponding sensor node (S515).

Referring to FIG. 6, a process of initial registration in which a sensor node has not been given a global ID in advance or a new global ID is assigned after factory initialization will be described.

First, the sensor node 110 transmits a registration request to the middleware 131 of the underground object resource management device 130 in step S601. In step S601, the middleware core registers the global ID in response to the registration request in the ID manager 132, (Step S602).

At this time, when there is no global ID value, the sensor node tries to register it as a specific value (for example, 0) set in advance. This is similar to the case of registering AP / PAN to connect without its own network ID value.

In step S603, the ID manager confirms whether the global ID is registered in the sensing DB 132 in step S603. The ID manager receives an initial registration confirmation response on the global ID from the sensing DB in step S604.

At this time, the ID manager transmits a success response to the middleware core when the received response is the pre-registered global ID (S605), and the middleware core changes the device status of the corresponding sensor node from offline to online (S606). Then, the middleware core transmits a device registration success response to the corresponding sensor node (S607).

On the other hand, if there is no global ID previously given to the sensor node, the global ID to be checked in step S602 is zero. Accordingly, in step S604, a response is received that the corresponding global ID is not the registered global ID.

Accordingly, the ID manager proceeds to a new ID creation registration process, generates a 'new' global ID and matches the device attribute information of the corresponding sensor node (S608), and proceeds to 'new' registration 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 status as a new device online (S612).

The middleware core also mounts a 'new' global ID in the response message to the sensor node (S613), and allows the sensor node to use the global ID assigned from the next time.

As described above, the global ID assignment and management for the sensor node of the ID manager can be performed in the same manner as the network ID assignment and management of the AP / PAN described above. That is, a value that increases the global ID sequentially from 1 can be used. If unregistering the used global ID can be performed, it can be stored in the ID pool. Also, when the number of issued global IDs reaches the maximum value, the global ID value stored in the ID pool can be used again as the global ID.

Meanwhile, in the underground buried object resource management system 100 according to the embodiment of the present invention, at least one sensor installed in a facility capable of underground environment measurement such as underground buried object or canopy is connected to a sensor node (not shown) through a transducer That is, underground object devices).

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

7 and 8 are data flow charts for explaining the initial registration process of the transducer according to an embodiment of the present invention.

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

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

In step S702, the middleware core transmits a registration confirmation request to the ID manager in response to the received registration request (i.e., the network ID) (S702). The ID manager transmits a registration ID confirmation request (S703).

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

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

At this time, the ID manager confirms the registration time at the time of the existing registration for the transducer device. If the existing registration time of the transducer device is earlier than a predetermined time (for example, the default value can be set to 5 minutes and can be changed via a configuration file) (i.e., It is regarded as re-registration of the same transducer, and the device state is changed to online (S706), and the transducer device is responded to the transducer device success (S707).

On the other hand, if the ID manager confirms the existing registration time of the corresponding transducer device, if there is a pre-registration within a predetermined reference time range (S708), the ID manager considers that the transducer of the same standard exists in the same sensor node, Response) to the transducer device (S709).

Upon receipt of the registration failure message (reason: pre-registration), the transducer device recognizes that transducers of the same standard have already been registered in the same sensor node, increases the transducer address value to a specific value (for example, 0x1000) The device registration is requested again with the middleware core (S710). 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 a transducer of the same standard exists in accordance with the previous registration time is as follows. In the installation and operation of the sensor node, re-start or power-off & power- Even if there is only one identical standard transducer at the node, re-registration attempts may occur. For reference, if the default value of the predetermined time (i.e., the reference time range) is set to about 5 minutes as described above, it is determined that restarting occurs after a longer time than 5 minutes in case of restarting, If there are several same standard transducers in the sensor node, it can be judged that all attempts to register these transducers within 5 minutes will be made.

On the other hand, when the response in step S704 is a response indicating that 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 to be registered with the sensor node device together with the device attribute information (S711), transmits them to the sensing DB (S712), and receives the success response from the sensing DB (S713) .

Then, the ID manager transmits a success response to the middleware core (S714), and the middleware core changes the device status of the transducer to online (S715), and transmits a success response to the transducer device (S716) .

On the other hand, the transducer device for monitoring underground objects is often a complex sensor type equipped with several sensors. There can be more than 10 types of sensing. In this case, more than 10 transducer registration messages can occur, which can cause an excessive burden on the wireless sensor node communication.

8 illustrates an initial registration process for storing a basic attribute value of a transducer ID in an aliasing DB and processing only a list of transducer IDs in a single registration message without attribute information .

Basically, the procedure is similar to the process of registering a transducer with attribute information. That is, steps S801 to S810 in FIG. 8 correspond to steps S701 to S710 described above with reference to FIG. 7, and therefore detailed description thereof will be omitted. For reference, when a plurality of transducer registration messages are received from a transducer of a complex sensor type, it is possible to judge whether or not the transducer registration information is preliminarily registered using only the first transducer ID in the transducer ID list.

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

Specifically, when the ID of the transducer device is determined to be the ID of the transducer device, 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 the attribute information, the ID manager requests the inquiry DB to inquire the alias attribute information (S812), and receives the response from the sensing DB (S813).

If a response is received from the sensing DB that alias attribute information corresponding to the transducer device exists, the ID manager requests the sensor DB to register the network ID for the transducer device as a new ID (S814) , And receives a success response thereto from the sensing DB (S815).

The ID manager then sends 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 transmits a response including the new ID information to the transducer device (S818).

On the other hand, if it is determined in step S813 that there is no alias attribute information corresponding to the transducer device from the sensing DB, the ID manager transmits a registration failure response to the middleware core (S819) And transmits a failure response in which the cause of failure is an alias unregistered to the transducer device (S820).

The transducer address alias table can be changed at any time, and even if you register it as the default value through alias, if you need to change the attribute value for each transducer device later, you can change the individual attribute value through the middleware UI have.

Hereinafter, a method for managing status information of underground objects according to an embodiment of the present invention will be described in detail with reference to FIG.

FIG. 9 is a data flow chart for explaining a method of managing underground objects in an underground according to an embodiment of the present invention.

FIG. 9 illustrates a method for storing and managing state information based on a global ID when a network ID is changed when a sensing value is reported through an underground object device (i.e., a sensor node).

Even if the wireless node of the sensor node is changed and the network ID of the sensor node is changed, it is effective not to proceed the registration process of the sensor node again due to communication burden of the low power wireless communication. Accordingly, the sensor node according to the embodiment of the present invention transmits only the sensing value report message even if the network ID of the sensor node changes, and the middleware 131 of the underground object resource management device 130 transmits the sensing value report message Only recognizes the wireless connection change.

Specifically, the sensor node 110 transmits a sensing value report including a sensing value (i.e., state information) acquired from a sensor installed in a subterranean material or a sensor installed in a facility such as a gateway (S901).

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

The middleware core of the underground burial object resource management device 130 receiving the sensing value report of the sensor node transmits the global ID according to the sensing value report of the corresponding sensor node to the ID manager to check whether the global ID is the previously registered ID (S902) .

Then, the ID manager requests the sensing DB 132 to confirm whether the global ID is pre-registered (S903), and receives a response according to whether or not the global ID is initially registered in the sensing DB (S904).

At this time, the network ID is also inquired from the sensing DB and the network ID in the sensing value report message is compared. If the network ID value based on the sensor value report of the sensor node differs from the previously registered network ID value with respect to the global ID of the corresponding sensor node, the ID manager transmits the network ID value of the sensing DB to the network ID Update.

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

Then, the sensing DB retrieves the following (i.e., matched) transducer address (i.e., ID) list based on the network ID value on the sensing DB that has been stored in advance and sends a completion response to the ID (S906).

The reason is that the network IDs of the transducers previously stored in the sensor node are also updated so as to correspond to the network ID of the changed sensor node.

The ID manager transmits an update request to the network ID according to the sensing value report of the corresponding sensor node in the sensing DB (S907), and the sensing DB stores the address of the sensor node and the matching transducer in the network ID, and transmits a completion response 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 the completion response from the sensing DB (S912).

On the other hand, if the network ID in the sensed value report message is compared with the network ID from the sensing DB in step S904, and the network ID is the same as the network ID registered in advance, the ID manager immediately returns to step S911 ) To store the sensing value.

When the sensing value of the underground objects and the underground environment is stored in the sensing DB 132 of the underground buried object resource management device 130, the data analysis module 133 calculates the underground Performs the submerged condition monitoring operation. The monitoring operation of the underground sub-condition is not limited. For example, when the status information (ie, information based on the sensing value) for an underground buried object exceeds a predetermined threshold value, Warning, and status information.

Next, the ID manager transmits a success response in the case where the global ID for the sensing value reporting to the middleware core is the pre-registered ID (S913), and the middleware core that receives the response returns the device status for the sensor node from offline to online . If the network ID is changed, the sensor node of the previous network ID is displayed as a member, and the new network ID is displayed as a new sensor node (S914). Then, the middleware core transmits a success response to the corresponding sensor node for global ID confirmation and sensing value storage (S915).

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

If it is determined in step S904 that the global ID is not a registered value, the ID manager transmits the failure response to the middleware core in step S916. In step S916, the middleware core determines whether the reason for the sensor node is a global ID unregistered sensor A value report failure response is transmitted (S917).

Therefore, even if frequent wireless connection changes are made to manage underground objects, the sensor node not only reports the sensing value but also reports the sensed value, as well as the fact that the network ID is changed, to the middleware Can be notified. At the same time, the middleware detects the change of the network configuration and can effectively perform the network management for the underground monitoring.

The apparatus and method for managing an underground buried object resource according to an embodiment of the present invention may be embodied 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 a recording medium is a computer-readable medium, which may be any available medium that can be accessed by a computer, and includes both volatile and nonvolatile media, removable and non-removable media. The computer-readable medium may also include computer storage media, which may be volatile and / or non-volatile, implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, Nonvolatile, removable and non-removable media.

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

It will be understood by those skilled in the art that the foregoing description of the present invention is for illustrative purposes only and that those of ordinary skill in the art can readily understand that various changes and modifications may be made without departing from the spirit or essential characteristics of the present invention. will be. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive. For example, each component described as a single entity may be distributed and implemented, and components described as being distributed may also be implemented in a combined form.

The scope of the present invention is defined by the appended claims rather than the detailed description and all changes or modifications derived from the meaning and scope of the claims and their equivalents are to be construed as being included within the scope of the present invention do.

100: Underground materials resource management system
110: Sensor node (underground object device)
111: Sensor
120: access point
130: Underground materials resource management device
P10: Gwanjeong
P11: Sensor
P20: Manhole

Claims (1)

1. An underground buried object resource management apparatus based on the Internet of objects,
A middleware core receiving a sensing value report on underground objects from a sensor node;
The sensor node checks whether the global ID of the sensor node has been registered according to the sensing value report, confirms whether the network ID is changed if it is a previously registered global ID, and checks whether the network ID matches the network ID matched with the global ID, An update ID manager; And
And a sensing DB in which a global ID and a network ID for each sensor node registered in advance are stored,
The sensor node obtains a sensing value from a sensor installed in a subterranean basement and wirelessly transmits the sensing value report through the access point,
The global ID is a unique ID for one sensor node,
Wherein the network ID includes an access point address, a personal area network (PAN) address, a sensor node address, and a sensor address connected to the sensor node.

Images