WO2010062114A2 - Device and method for sensor node management based on metadata - Google Patents

Device and method for sensor node management based on metadata Download PDF

Info

Publication number
WO2010062114A2
WO2010062114A2 PCT/KR2009/006994 KR2009006994W WO2010062114A2 WO 2010062114 A2 WO2010062114 A2 WO 2010062114A2 KR 2009006994 W KR2009006994 W KR 2009006994W WO 2010062114 A2 WO2010062114 A2 WO 2010062114A2
Authority
WO
WIPO (PCT)
Prior art keywords
sensor node
identification code
information
metadata
sensor
Prior art date
Application number
PCT/KR2009/006994
Other languages
French (fr)
Korean (ko)
Other versions
WO2010062114A3 (en
Inventor
성종우
Original Assignee
Sung Jong-Woo
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sung Jong-Woo filed Critical Sung Jong-Woo
Publication of WO2010062114A2 publication Critical patent/WO2010062114A2/en
Publication of WO2010062114A3 publication Critical patent/WO2010062114A3/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network

Definitions

  • the present invention relates to an apparatus and method for managing a sensor node based on metadata, and more particularly, to retrieve metadata of a sensor node and to control the sensor node using an identification code assigned to the sensor node constituting the sensor network.
  • An apparatus and method are provided.
  • the present invention relates to an apparatus and method for managing a sensor node based on metadata, and more particularly, to retrieve metadata of a sensor node and to control the sensor node using an identification code assigned to the sensor node constituting the sensor network.
  • An apparatus and method are provided.
  • the technical problem to be achieved by the present invention is to avoid the additional memory usage and communication overhead between nodes, and to overcome the disadvantage that dynamic update is impossible, the meta data of the sensor node stored in the data server based on the identification code uniquely assigned to the sensor node.
  • the present invention provides a sensor node management apparatus and method based on metadata for acquiring data and managing sensor nodes based on information included in the metadata.
  • Another technical problem to be solved by the present invention is a sensor node stored in a data server based on an identification code uniquely assigned to a sensor node in order to avoid additional memory usage and inter-node communication overhead, and to overcome the disadvantage that dynamic update is impossible.
  • To provide a computer-readable recording medium recording a program for acquiring the data of the data and executing the sensor node management method based on metadata that can manage the sensor node based on the information contained in the metadata. have.
  • the sensor node management apparatus based on metadata is retrieved from an external device having access information of a data server storing metadata of a plurality of sensor nodes constituting a sensor network.
  • An address obtaining unit for obtaining access information of a data server corresponding to an identification code of a target sensor node;
  • a data acquisition unit accessing a data server corresponding to the obtained access information of the data server and acquiring metadata corresponding to the identification code of the sensor node to be searched;
  • a sensor node manager which accesses the searched sensor node and transmits a control message based on the information included in the metadata.
  • the method for managing a sensor node based on metadata is to search from an external device having access information of a data server storing metadata of a plurality of sensor nodes constituting a sensor network.
  • an apparatus and method for managing a sensor node based on metadata since data related to a sensor node is stored in a separate data server instead of a sensor node with limited resources, an overhead of a sensor node according to data storage and communication Can be reduced, and data related to the sensor node can be easily obtained.
  • modifying registered data or adding new data it is possible to connect to a data server and update data for a plurality of sensor nodes collectively.
  • an inquiry message or a control command is transmitted to the sensor node, whereby active control of the sensor network and utilization of the sensor data are possible.
  • FIG. 1 is a block diagram showing the configuration of a preferred embodiment of a sensor node management apparatus according to the present invention
  • FIG. 2 is a view showing an example of a unique identification code assigned to a sensor node
  • FIG. 3 is a diagram illustrating a general execution procedure for an ONS query
  • FIG. 4 is a diagram illustrating a process of obtaining an address of a metadata server by providing an identification code assigned to a sensor node to a naming server by the address obtaining unit;
  • FIG. 5 is a diagram illustrating an example of an interface where a data acquisition unit queries and responds to metadata to be obtained from a metadata server;
  • FIG. 6 is a diagram illustrating an example of a format of a query message to be transmitted to a sensor node among metadata obtained from a metadata server;
  • ZCL ZigBee Cluster Library
  • FIG. 8 illustrates an example of a message conforming to the frame format of FIG. 7,
  • FIG. 9 is a flowchart illustrating a preferred embodiment of a method for managing a sensor node based on metadata according to the present invention.
  • FIG. 1 is a block diagram showing the configuration of a preferred embodiment of a sensor node management apparatus according to the present invention.
  • the sensor node management apparatus 100 includes an identification code extractor 110, an address acquirer 120, a data acquirer 130, and a sensor node access information storage 140. And a sensor node manager 150.
  • the address acquisition unit 120 accesses a sensor node to be searched based on a unique identification code assigned to each of the plurality of sensor nodes constituting the sensor network, and access information of a data server storing metadata of the sensor node to be searched. Acquire.
  • the identification code is preferably fixed to each of the sensor nodes.
  • Data collected from sensor nodes are sensor data that collects physical state information in response to a specific period or a specific event, and information dynamically obtained from the sensor node for management purposes such as location information or battery level.
  • metadata is data necessary for the sensor node to describe the service, function, and characteristics of the sensor node and is static additional information that does not change during operation of the sensor node.
  • the metadata may include information about a sensor collecting specific physical data, a function provided by a sensor node, a communication format, etc. in order to utilize data collected from a sensor node or a wireless sensor network.
  • Metadata of sensor node includes data about sensor object such as sensor type, sensor unit, operating system type and version of sensor, power consumption conversion information, sensor node manufacturer, etc. Contains data about the format of the message. Table 1 below describes the types and examples of metadata.
  • Applications Sensor node images, icons, etc.
  • the metadata is stored inside the sensor node, additional sensor node overhead is generated for storage and transmission in order to obtain metadata, which is a functional specification of the sensor node. Therefore, the metadata is stored in a separate data server rather than a sensor node, and the data server is distributed and located in a network on the Internet.
  • the data server storing metadata is configured separately from the sensor node, the metadata does not need to be stored in each sensor node, and in order to obtain the metadata, an identification code uniquely assigned to each sensor node is obtained. Acquiring the data is easy because the access information of the data server is acquired based on the data server. In addition, when modifying registered data or adding new data, it is possible to connect to a data server and update data for a plurality of sensor nodes collectively.
  • a method for uniquely identifying the metadata and the sensor node is required.
  • the network address used in the sensor network such as ZigBee is dynamically changed according to the topology, so the sensor metadata and sensor node cannot be uniquely identified, and the IPv6 address used in MAC address and 6LowPan also fixedly identifies a single sensor node. It is not possible to work with metadata servers.
  • the address schemes used in the existing sensor network cannot identify the sensor node with a fixed and unique address or look up or resolve the connection information of the data server where the data is stored. Used separately.
  • sensor node can be uniquely identified regardless of time and place such as EPC or OID, and code assignment is composed of hierarchical structure or tree structure, so that lookup of metadata server is possible. .
  • code assignment is composed of hierarchical structure or tree structure, so that lookup of metadata server is possible.
  • the stored identification code may be used to access the sensor node. However, if the identification code is not stored in advance, the identification code transmitted with the sensor data should be extracted.
  • the sensor node management apparatus 100 according to the present invention may include an identification code extraction unit 110. Since the data transmitted from the sensor node includes the identification code and the data collected from the sensor, the identification code extraction unit 110 extracts the identification code from the transmitted data and provides it to the address acquisition unit 120.
  • the address acquisition unit 120 may directly access a sensor node to obtain an address of a data server in which metadata of the sensor node is stored.
  • a separate device is not required for acquiring an address, but there is a problem in that an overhead may be generated by additionally including a pointer to the sensor node. Therefore, there is a need to use a separate device that can obtain the address of the data server based on the identification code of the sensor node.
  • the address acquisition unit 120 may obtain the address of the data server by accessing the naming server that stores the address of the data server. That is, the address acquisition unit 120 accesses a naming server in which connection information of a data server storing metadata of a plurality of sensor nodes constituting a sensor network is stored corresponding to a unique identification code assigned to each sensor node. To obtain the address of the data server corresponding to the identification code of the sensor node to be searched.
  • the address acquisition unit 120 accesses the naming server and obtains the address of the data server corresponding thereto by providing an identification code assigned to the sensor node.
  • the address of the data server is stored corresponding to each identification code assigned to each of the plurality of sensor nodes.
  • the identification code When building a database by storing the address of the data server inside the naming server, you can simply store the identification code and the address of the data server in a one-to-one correspondence. It is easy when searching for an address.
  • the identification code must contain these classification criteria. For example, by including manufacturer information or product information of a sensor node in an identification code, identification codes of sensor nodes having the same manufacturer information or product information among a plurality of sensor nodes may be classified and stored separately.
  • the classification criteria may be plural, and when there are a plurality of classification criteria, the identification codes may be classified and stored in a hierarchical manner by dividing them into upper and lower standards.
  • EPC is a code system created by the international organization EPCglobal to integrate existing code systems.
  • FIG. 2 An example of an EPC configuration is shown in FIG. Referring to FIG. 2, the identification code includes header information, manufacturer information of a sensor node, product information of a sensor node, and a serial code. The information included in the code can be configured in various forms in consideration of convenience of use and issuance and management of the code.
  • the product information of the sensor node is used as a lower standard. You can reclassify the address of the data server based on.
  • An example of classifying and storing the address of the metadata server among the data servers using the sensor node manufacturer information and the product information as the upper standard and the lower standard is shown in Table 2 below.
  • Metadata server address A company temperature Senser http://icu.com/aaa Pressure sensor http://icu.com/aab Light sensor http://icu.com/aac Company B temperature Senser http://icu.com/bba Pressure sensor http://icu.com/bbb Light sensor http://icu.com/bbc Company C temperature Senser http://icu.com/cca Pressure sensor http://icu.com/ccb Light sensor http://icu.com/ccc
  • the naming server extracts the classification criteria from the identification code and stores the address of the metadata server as shown in Table 2 below. Search the address of the metadata server corresponding to the identification code input from the address acquisition unit 120 in the database. In this case, when there are a plurality of classification criteria included in the identification code, the classification criteria corresponding to the upper criteria are first extracted and searched. Referring to Table 2, for example, if the identification code of the sensor is entered in the naming server to obtain the address of the metadata server in which the metadata of the temperature sensor manufactured by Company B is stored, the naming server is the first manufacturer The information is extracted from the identification code to retrieve a group of metadata server addresses classified as Company B. Next, the product information, which is a lower standard, is extracted from the identification code to search the address of the metadata server corresponding to the temperature sensor.
  • the process of obtaining the address of the data server corresponding to the identification code from the naming server is called resolving, and the address obtaining unit 120 may obtain the address of the data server by the above-mentioned method.
  • the resolving method used to obtain the address of the data server from the naming server For example, when an identification code of a sensor node has a hierarchical structure such as an EPC, an object naming service (ONS) may be used as one method of resolving.
  • OTS object naming service
  • ONS is a framework for providing information location of products corresponding to EPCs stored in RFID tags in a manner similar to the domain name service (DNS) that specifies the location of computers on the Web.
  • DNS domain name service
  • ONS operates on the DNS framework, and a general procedure for ONS queries is shown in FIG. Referring to FIG. 3, when an RFID reader reads an EPC composed of a bit sequence stored in an RFID tag and sends it to a local server, the local server changes the EPC to a Uniform Resource Identifier (URI), and the local ONS resolver resolves the URI. Perform DNS query by changing to domain name. The DNS returns, as a response, the URL corresponding to the query result among the stored URLs.
  • URI Uniform Resource Identifier
  • the naming server changes the identification code of the EPC type to the URI, and then changes the URI to the domain name. Find the matching address among the stored metadata server's addresses.
  • the naming server outputs the address of the retrieved metadata server as a response and provides the address acquisition unit 120.
  • 4 illustrates a process in which the address obtaining unit 120 obtains an address of the metadata server by providing an identification code assigned to the sensor node to the naming server.
  • the naming server If the response output from the naming server is output in the form of an A record consisting solely of IP addresses, it cannot be applied to advanced web service resolving. Therefore, the naming server outputs the response as a NAPTR record having a plurality of fields to indicate a protocol, a service, and the like. Table 3 below shows the NAPTR record response output from the naming server.
  • the order field and the pref field have integer values.
  • a 'u' in the flag field means that the response contains a URI.
  • the service field indicates a type of service and may have various types according to services supported by a server such as html, XMLRPC, EPC information service (EPCIS), and web service (WS).
  • Regexp means that the address is expressed as a regular expression. Therefore, the URL representing the retrieved metadata server address is output in the form of regular expression.
  • the original function of ONS is to obtain the address of the server that stores the information of the RFID tagged product from the EPC read by the RFID reader.
  • what the address acquisition unit 120 wants to acquire from the naming server is the address of the server where the data of the sensor node is stored, not the information of the tagged object.
  • the access information of the data server may be added as a type of service constituting the service field of the NAPTR record. . Therefore, the part indicated as 'EPC + x-metadata' in the service field among the NAPTR record responses shown in Table 3 means that the outputted response provides the connection information of the metadata server, and the address indicated by the regular expression is the address of the metadata server. It indicates that. Also, if a service type indicating the address of the sensor data server is added to the service field, it means that the outputted response provides connection information of the sensor data server.
  • the data obtaining unit 130 accesses the data server located at the address to obtain the stored data. do.
  • data is classified and stored in groups according to appropriate criteria, and all data or only data of a group selected as needed can be obtained.
  • FIG. 5 illustrates an example of an interface in which the data obtaining unit 130 queries and responds to metadata to be obtained from the metadata server.
  • query messages can be defined using communication protocols such as TCP and UDP, or SOAP, an Internet protocol, or HTTP, can be used.
  • the sensor node manager 150 accesses a sensor node to be searched based on the information included in the metadata and transmits a control message.
  • the sensor node In order to transmit the control message, the sensor node should be connected to a search target sensor node. In this case, an identification code included in data transmitted from the sensor node may be used.
  • a broadcast message including a target identification code may be transmitted to communicate with a sensor node corresponding to the identification code.
  • additional overhead may occur in communication between sensor nodes due to the length of the identification code included in each transmission message.
  • the identification code is fixed and assigned to the sensor node and is unique worldwide, it is very long when compared to the sensor network address that is used only temporarily inside the sensor node. Can be a constraint on the phase. Also, because the identification code is not an address, it cannot be used for direct unicast communication with the sensor node.
  • the identification code is converted into a network address for routing between sensor nodes, for example, a network address of ZigBee, or a short length that can shorten the length of the communication message between sensor nodes as much as possible. It should be converted into the identification code of and communicated.
  • the short length identification code is fixed to the sensor node and, unlike the uniquely assigned identification code around the world, is guaranteed to be unique only within the sensor network.
  • a short identification code consisting of a natural number is sequentially assigned to a sensor node having a unique identification code fixedly assigned to the sensor node, and a corresponding table is configured, so that the actual communication between the sensor network nodes is performed at the sensor node.
  • a short, uniquely unique identification code of natural numbers may be used.
  • the sensor node management apparatus 100 may further include a sensor node access information storage unit 140 for this purpose.
  • the sensor node manager 150 obtains the connection information of the searched sensor node corresponding to the identification code from the sensor node connection information storage 140 to access the searched sensor node. Access information about the unique identification code and its corresponding network address or short length identification code fixedly assigned to the sensor node is registered in the sensor node access information storage unit 140 of the base station, and the network address of the sensor node is changed. At each point in time, or when the topology changes.
  • the connection information corresponding to the identification code of the sensor node may be obtained from the conversion table stored in the sensor node connection information storage 140.
  • FIG. 6 illustrates an example of a format of a query message to be transmitted to a sensor node among metadata obtained from a metadata server.
  • MAC_CapabilityFlags description "FFD, main powers, disabled receiver during idle periods, no security”> 7 ⁇ / MAC_CapabilityFlags>
  • the metadata includes three blocks, an ⁇ identifier> block, a ⁇ ZigBeeDescriptor> block, and a ⁇ device> block.
  • ⁇ identifier> represents EPC information and shows type and identifier assigned to sensor node.
  • the ⁇ ZigBeeDescriptor> block contains the contents of all the static Descriptors defined in ZigBee. Existing ZigBee defines two mandatory Descriptors and three optional Descriptors as Descriptors. Through Service Discovery provided by ZigBee, these Descriptors can be requested to specific sensor nodes and the contents of Descriptors can be received.
  • the ⁇ ZigBeeDescriptor> block describes the characteristic content of the sensor node.
  • the ⁇ ZigBeeDescriptor> block contains the Profile ID, List, and Endpoint of the input cluster and output cluster.
  • the ⁇ device> block shows the functional specification information implemented in the sensor node.
  • the ⁇ device> block describes the cluster implemented in the sensor node.
  • ZigBee cluster library ZCL
  • ZCL ZigBee cluster library
  • the ⁇ device> block contains attributes and commands.
  • the sensor node corresponding to the above message is a sensor node with On / Off switch actuating function, has On / Off attribute representing the state, and defines a Toggle command to change the state of the switch.
  • Sensor node management apparatus 100 can optionally show the operation specification of the metadata and implement a GUI that receives the user's input, using the attributes or commands of the metadata through the user's input or automated script Can be.
  • the metadata of the On / Off switch of the above message defines attributes and unique command identifiers for each command.
  • standard commands for accessing these attributes and using commands are provided. By providing a frame format, it is possible to communicate with sensor nodes based on metadata information.
  • ZCL ZigBee Cluster Library
  • the sensor node implementing ZigBee can communicate in the corresponding frame format.
  • the contents of the frame format depend on the functions provided by the sensor node. Because it is different, the metadata is decoded to construct a frame and send it to the sensor node using values appropriate for specific attributes and commands.
  • FIG. 8 is an example of a message that follows the frame format of FIG. This is an example of a user sending a toggle command to a ZigBee-based light sensor node.
  • the function specification provided by the light sensor node is identified, and the ZCL command is configured according to user input or automated script.
  • the device is a light device and provides a toggle command.
  • the identifier and other information of the toggle command (Endpoint, cluster ID, APS profile ID, APS Src Endpint, APS). command) can be obtained.
  • a message frame having a toggle command can be configured according to the frame format of FIG. 8.
  • APS Dest Endpoint 0x0A
  • APS cluster ID 0x06
  • APS profile ID 0x0400
  • APS Src Endpint 0x01
  • the APS payload command is 0x02.
  • the message sent to the search target sensor node may be transmitted based on a unique identification code fixed to the search target sensor node, and when the sensor node access information storage unit 140 is used, the search target In order to reduce the size of a network address or a message of a sensor node, a short identifier assigned to the sensor node may be transmitted as a receiving identifier to a search target sensor node.
  • the sensor node management apparatus 100 when used, not only the metadata is obtained from the data server based on the identification code assigned to the sensor node, but also the sensor is based on the information included in the acquired metadata.
  • the sensor network can be actively used by sending the appropriate query message or control command to the node.
  • FIG. 9 is a flowchart illustrating a preferred embodiment of a method for managing a sensor node based on metadata according to the present invention.
  • the identification code extracting unit 110 may perform a search on the sensor node.
  • the identification code assigned to the search target sensor node is extracted from the transmitted data (S910).
  • the address acquisition unit 120 accesses a naming server in which connection information of a data server storing metadata of a plurality of sensor nodes is stored corresponding to an identification code assigned to each sensor node to identify a sensor node to be searched. Access information of the data server corresponding to the code is obtained (S920).
  • the naming server stores the address of the data server based on at least one of the information included in the identification code as a classification criterion.
  • the classification of the data server is classified hierarchically by dividing each classification criteria into upper and lower criteria.
  • the data acquisition unit 130 accesses the data server corresponding to the obtained access information of the data server and acquires metadata corresponding to the identification code of the sensor node to be searched for (S930).
  • the sensor node manager 150 transmits an inquiry message or a control command to the sensor node to be searched by using information included in the acquired metadata, that is, a communication message format (S940).
  • the invention can also be embodied as computer readable code on a computer readable recording medium.
  • the computer-readable recording medium includes all kinds of recording devices in which data that can be read by a computer system is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, and the like, and may also be implemented in the form of a carrier wave (for example, transmission over the Internet). Include.
  • the computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

Abstract

Provided are a device and a method for sensor node management based on metadata. An address acquisition part acquires the access information of a data server corresponding to the identification code of a search target sensor node from an external device holding the access information of the data server in which metadata of a plurality of sensor nodes constituting a sensor network is saved. A data acquisition part accesses the data server corresponding to the acquired access information of the data server and acquires metadata corresponding to the identification code of a search target sensor node. A sensor node management part accesses the search target sensor node based on the information included in the metadata and transmits a control message. The device for sensor node management of the present invention stores data on a sensor node in a sensor node whose resources are limited but in a separate data server, thereby reducing the sensor node overhead that results from storage and communication of data, and easily acquiring data related to the sensor node. Also, the device communicates with the sensor node having an identification code and transmits a query message or a control command to the sensor node, thereby enabling active control of a sensor network and utilization of sensor data.

Description

메타데이터에 기반한 센서노드 관리장치 및 방법Sensor node management device and method based on metadata
본 발명은 메타데이터에 기반한 센서노드 관리장치 및 방법에 관한 것으로, 보다 상세하게는, 센서 네트워크를 구성하는 센서노드에 부여된 식별코드를 사용하여 센서노드의 메타데이터를 검색하고 센서노드를 제어하는 장치 및 방법에 관한 것이다.The present invention relates to an apparatus and method for managing a sensor node based on metadata, and more particularly, to retrieve metadata of a sensor node and to control the sensor node using an identification code assigned to the sensor node constituting the sensor network. An apparatus and method are provided.
본 발명은 메타데이터에 기반한 센서노드 관리장치 및 방법에 관한 것으로, 보다 상세하게는, 센서 네트워크를 구성하는 센서노드에 부여된 식별코드를 사용하여 센서노드의 메타데이터를 검색하고 센서노드를 제어하는 장치 및 방법에 관한 것이다.The present invention relates to an apparatus and method for managing a sensor node based on metadata, and more particularly, to retrieve metadata of a sensor node and to control the sensor node using an identification code assigned to the sensor node constituting the sensor network. An apparatus and method are provided.
본 발명이 이루고자 하는 기술적 과제는, 추가적인 메모리 사용과 노드 간 통신 오버헤드를 피하고 동적 업데이트가 불가능하다는 단점을 극복하기 위해 센서 노드에 고유하게 할당된 식별코드를 기초로 데이터 서버에 저장된 센서노드의 메타데이터를 획득하고, 메타데이터에 포함된 정보를 기초로 센서노드를 관리할 수 있는 메타데이터에 기반한 센서노드 관리장치 및 방법을 제공하는 데 있다.The technical problem to be achieved by the present invention is to avoid the additional memory usage and communication overhead between nodes, and to overcome the disadvantage that dynamic update is impossible, the meta data of the sensor node stored in the data server based on the identification code uniquely assigned to the sensor node. The present invention provides a sensor node management apparatus and method based on metadata for acquiring data and managing sensor nodes based on information included in the metadata.
본 발명이 이루고자 하는 또 다른 기술적 과제는, 추가적인 메모리 사용과 노드 간 통신 오버헤드를 피하고 동적 업데이트가 불가능하다는 단점을 극복하기 위해 센서 노드에 고유하게 할당된 식별코드를 기초로 데이터 서버에 저장된 센서노드의 데이터를 획득하고, 메타데이터에 포함된 정보를 기초로 센서노드를 관리할 수 있는 메타데이터에 기반한 센서노드 관리방법을 컴퓨터에서 실행시키기 위한 프로그램을 기록한 컴퓨터로 읽을 수 있는 기록매체를 제공하는 데 있다.Another technical problem to be solved by the present invention is a sensor node stored in a data server based on an identification code uniquely assigned to a sensor node in order to avoid additional memory usage and inter-node communication overhead, and to overcome the disadvantage that dynamic update is impossible. To provide a computer-readable recording medium recording a program for acquiring the data of the data and executing the sensor node management method based on metadata that can manage the sensor node based on the information contained in the metadata. have.
상기의 기술적 과제를 달성하기 위한, 본 발명에 따른 메타데이터에 기반한 센서노드 관리장치는, 센서 네트워크를 구성하는 복수의 센서노드의 메타데이터가 저장된 데이터 서버의 접속정보를 보유하고 있는 외부장치로부터 검색대상 센서노드의 식별코드에 대응하는 데이터 서버의 접속정보를 획득하는 주소획득부; 상기 획득한 데이터 서버의 접속정보에 대응하는 데이터 서버에 접속하여 상기 검색대상 센서노드의 식별코드에 대응하는 메타데이터를 획득하는 데이터 획득부; 및 상기 메타데이터에 포함된 정보를 기초로 상기 검색대상 센서노드에 접속하여 제어메시지를 전송하는 센서노드 관리부;를 구비한다.In order to achieve the above technical problem, the sensor node management apparatus based on metadata according to the present invention is retrieved from an external device having access information of a data server storing metadata of a plurality of sensor nodes constituting a sensor network. An address obtaining unit for obtaining access information of a data server corresponding to an identification code of a target sensor node; A data acquisition unit accessing a data server corresponding to the obtained access information of the data server and acquiring metadata corresponding to the identification code of the sensor node to be searched; And a sensor node manager which accesses the searched sensor node and transmits a control message based on the information included in the metadata.
상기의 기술적 과제를 달성하기 위한, 본 발명에 따른 메타데이터에 기반한 센서노드 관리방법은, 센서 네트워크를 구성하는 복수의 센서노드의 메타데이터가 저장된 데이터 서버의 접속정보를 보유하고 있는 외부장치로부터 검색대상 센서노드의 식별코드에 대응하는 데이터 서버의 접속정보를 획득하는 주소획득단계; 상기 획득한 데이터 서버의 접속정보에 대응하는 데이터 서버에 접속하여 상기 검색대상 센서노드의 식별코드에 대응하는 메타데이터를 획득하는 데이터 획득단계; 및 상기 메타데이터에 포함된 정보를 기초로 상기 검색대상 센서노드에 접속하여 제어메시지를 전송하는 센서노드 관리단계;를 갖는다.In order to achieve the above technical problem, the method for managing a sensor node based on metadata according to the present invention is to search from an external device having access information of a data server storing metadata of a plurality of sensor nodes constituting a sensor network. An address acquisition step of acquiring access information of the data server corresponding to the identification code of the target sensor node; A data acquiring step of accessing a data server corresponding to the acquired access information of the data server and acquiring metadata corresponding to the identification code of the sensor node to be searched; And a sensor node management step of accessing the search target sensor node and transmitting a control message based on the information included in the metadata.
본 발명에 따른 메타데이터에 기반한 센서노드 관리장치 및 방법에 의하면, 센서노드에 관한 데이터가 리소스가 제한된 센서노드가 아닌 별도의 데이터 서버에 저장됨으로써, 데이터의 저장과 통신에 따른 센서노드의 오버헤드를 줄일 수 있고, 센서노드와 관련된 데이터를 용이하게 획득할 수 있다. 또한, 등록된 데이터를 수정하거나 새로운 데이터를 추가 등록하고자 할 경우에도 데이터 서버에 접속하여 복수의 센서노드에 대한 데이터를 일괄적으로 업데이트하는 것이 가능하다. 나아가 획득한 메타데이터의 기능명세에 따라서 식별코드를 가지는 센서노드와 통신하여 질의메시지 또는 제어명령을 센서노드에 전송함으로써, 센서 네트워크에 대한 능동적인 제어 및 센서 데이터의 활용이 가능하다.According to an apparatus and method for managing a sensor node based on metadata according to the present invention, since data related to a sensor node is stored in a separate data server instead of a sensor node with limited resources, an overhead of a sensor node according to data storage and communication Can be reduced, and data related to the sensor node can be easily obtained. In addition, when modifying registered data or adding new data, it is possible to connect to a data server and update data for a plurality of sensor nodes collectively. Furthermore, by communicating with a sensor node having an identification code according to the function specification of the acquired metadata, an inquiry message or a control command is transmitted to the sensor node, whereby active control of the sensor network and utilization of the sensor data are possible.
도 1은 본 발명에 따른 센서노드 관리장치에 대한 바람직한 실시예의 구성을 도시한 블록도,1 is a block diagram showing the configuration of a preferred embodiment of a sensor node management apparatus according to the present invention;
도 2는 센서노드에 할당되는 고유한 식별코드의 일 예를 도시한 도면,2 is a view showing an example of a unique identification code assigned to a sensor node,
도 3은 ONS 질의에 대한 일반적인 수행절차를 도시한 도면,3 is a diagram illustrating a general execution procedure for an ONS query;
도 4는 주소획득부가 센서노드에 부여된 식별코드를 네이밍 서버에 제공하여 메타데이터 서버의 주소를 획득하는 과정을 도시한 도면,4 is a diagram illustrating a process of obtaining an address of a metadata server by providing an identification code assigned to a sensor node to a naming server by the address obtaining unit;
도 5는 데이터 획득부가 메타데이터 서버로부터 획득하고자 하는 메타데이터에 관하여 질의하고 응답받는 인터페이스의 한 예를 도시한 도면,5 is a diagram illustrating an example of an interface where a data acquisition unit queries and responds to metadata to be obtained from a metadata server;
도 6은 메타데이터 서버로부터 획득한 메타데이터 중에서 센서노드에 전송할 질의 메시지의 포맷의 일 예를 도시한 도면,6 is a diagram illustrating an example of a format of a query message to be transmitted to a sensor node among metadata obtained from a metadata server;
도 7은 메타데이터에서 기술하고 있는 속성과 커맨드를 이용해서 센서노드와 통신하기 위한 ZigBee 스팩의 표준 ZCL (ZigBee Cluster Library) 프레임 포맷을 도시한 도면,7 illustrates a ZigBee specification standard ZCL (ZigBee Cluster Library) frame format for communicating with a sensor node using attributes and commands described in metadata.
도 8은 도 7의 프레임포맷을 따르는 메시지의 예를 도시한 도면, 그리고,8 illustrates an example of a message conforming to the frame format of FIG. 7, and
도 9는 본 발명에 따른 메타데이터에 기반한 센서노드 관리방법의 바람직한 실시예의 수행과정을 도시한 흐름도이다.9 is a flowchart illustrating a preferred embodiment of a method for managing a sensor node based on metadata according to the present invention.
이하에서 첨부된 도면들을 참조하여 본 발명에 따른 메타데이터에 기반한 센서노드 관리장치 및 방법의 바람직한 실시예에 대해 상세하게 설명한다.Hereinafter, exemplary embodiments of an apparatus and method for managing a sensor node based on metadata according to the present invention will be described in detail with reference to the accompanying drawings.
도 1은 본 발명에 따른 센서노드 관리장치에 대한 바람직한 실시예의 구성을 도시한 블록도이다.1 is a block diagram showing the configuration of a preferred embodiment of a sensor node management apparatus according to the present invention.
도 1을 참조하면, 본 발명에 따른 센서노드 관리장치(100)는, 식별코드 추출부(110), 주소획득부(120), 데이터 획득부(130), 센서노드 접속정보 저장부(140) 및 센서노드 관리부(150)를 구비한다.Referring to FIG. 1, the sensor node management apparatus 100 according to the present invention includes an identification code extractor 110, an address acquirer 120, a data acquirer 130, and a sensor node access information storage 140. And a sensor node manager 150.
주소획득부(120)는 센서 네트워크를 구성하는 복수의 센서노드 각각에 부여된 고유의 식별코드를 기초로 검색대상 센서노드에 접속하여 검색대상 센서노드의 메타데이터가 저장되어 있는 데이터 서버의 접속정보를 획득한다. 이때 식별코드는 센서노드 각각에 고정되어 부여되는 것이 바람직하다.The address acquisition unit 120 accesses a sensor node to be searched based on a unique identification code assigned to each of the plurality of sensor nodes constituting the sensor network, and access information of a data server storing metadata of the sensor node to be searched. Acquire. In this case, the identification code is preferably fixed to each of the sensor nodes.
센서 네트워크에서 사용되는 데이터는 센서노드에서 수집되는 데이터와 미리 정의되는 메타데이터 두 가지가 있다. 센서노드에서 수집되는 데이터는 특정 주기 또는 특정 이벤트에 맞추어서 물리적 상태 정보를 수집하는 센서데이터 및 위치정보나 배터리 잔량과 같이 관리용도로 센서노드에서 동적으로 획득되는 정보이다. 반면에 메타데이터는 센서노드의 서비스와 기능 및 특성을 기술하여 센서노드가 이용할 수 있기 위해서 필요한 데이터로, 센서노드의 동작 중에 변화하지 않는 정적인 부가 정보이다. 예를 들면, 메타데이터는 센서노드 또는 무선 센서 네트워크에서 수집된 데이터를 활용하기 위해서 특정 물리적 데이터를 수집한 센서에 대한 정보와 센서 노드에서 제공되는 기능 및 통신 포맷 등을 포함할 수 있다.There are two types of data used in the sensor network: data collected at the sensor node and predefined metadata. Data collected from sensor nodes are sensor data that collects physical state information in response to a specific period or a specific event, and information dynamically obtained from the sensor node for management purposes such as location information or battery level. On the other hand, metadata is data necessary for the sensor node to describe the service, function, and characteristics of the sensor node and is static additional information that does not change during operation of the sensor node. For example, the metadata may include information about a sensor collecting specific physical data, a function provided by a sensor node, a communication format, etc. in order to utilize data collected from a sensor node or a wireless sensor network.
센서노드의 메타데이터에는 센서의 유형, 센서 단위 등 센서의 측정 대상에 관한 데이터, 센서의 운영체제 타입 및 버전, 전력소모 변환정보, 센서노드 제조사 등 센서기기에 관한 데이터 및 센서노드와 통신하기 위한 응용 메시지의 포맷에 관한 데이터가 포함되어 있다. 다음의 표 1에는 메타데이터의 종류 및 예가 기재되어 있다.Metadata of sensor node includes data about sensor object such as sensor type, sensor unit, operating system type and version of sensor, power consumption conversion information, sensor node manufacturer, etc. Contains data about the format of the message. Table 1 below describes the types and examples of metadata.
표 1
메타데이터 분류 메타데이터의 예
센서 센서 타입, 센싱 단위, 유효범위, 예민도,칼리브레이션(Calibration) 정보, 제조사 등
센서노드 센서의 리스트, 하드웨어/소프트웨어/네트워크 정보,운용 정보(Duty Cycle), 배터리 모델 및 정보 등
센서 데이터 이벤트 정보, 이벤트 설정 정보, 제공되는 서비스 리스트,서비스별 메시지 포맷 등
응용 센서 노드 이미지, 아이콘 등
Table 1
Metadata Classification Example of metadata
sensor Sensor type, sensing unit, effective range, sensitivity, calibration information, manufacturer, etc.
Sensor node List of sensors, hardware / software / network information, duty cycle, battery model and information
Sensor data Event information, event setting information, service list provided, message format for each service, etc.
Applications Sensor node images, icons, etc.
메타데이터가 센서노드 내부에 저장되는 경우, 센서노드의 기능 명세서인 메타데이터를 획득하기 위해서는 저장과 전송을 위하여 추가적인 센서노드 오버헤드가 발생한다. 따라서 메타데이터는 센서노드가 아닌 별개의 데이터 서버에 저장되며, 데이터 서버는 인터넷 상의 네트워크에 분산되어 위치한다.When metadata is stored inside the sensor node, additional sensor node overhead is generated for storage and transmission in order to obtain metadata, which is a functional specification of the sensor node. Therefore, the metadata is stored in a separate data server rather than a sensor node, and the data server is distributed and located in a network on the Internet.
이와 같이 메타데이터가 저장되는 데이터 서버가 센서노드와 별개로 구성됨으로써, 메타데이터를 각각의 센서노드에 저장할 필요가 없으며, 메타데이터를 얻고자 할 경우에 각 센서노드에 고유하게 부여된 식별코드를 기초로 데이터 서버의 접속정보를 획득하여 해당 데이터 서버에 접속하면 되므로 데이터의 획득이 용이하다. 또한 등록된 데이터를 수정하거나 새로운 데이터를 추가 등록하고자 할 경우에도 데이터 서버에 접속하여 복수의 센서노드에 대한 데이터를 일괄적으로 업데이트하는 것이 가능하게 된다.As the data server storing metadata is configured separately from the sensor node, the metadata does not need to be stored in each sensor node, and in order to obtain the metadata, an identification code uniquely assigned to each sensor node is obtained. Acquiring the data is easy because the access information of the data server is acquired based on the data server. In addition, when modifying registered data or adding new data, it is possible to connect to a data server and update data for a plurality of sensor nodes collectively.
분산된 센서메타데이터 서버에 저장된 메타데이터와 센서노드를 연동하기 위해서는 고유하게 메타데이터 및 센서노드를 식별할 수 있는 방법이 필요하다. ZigBee 등 센서네트워크에서 사용되는 네트워크 주소는 토폴로지에 따라 동적으로 변경되어서, 센서 메타데이터와 센서노드를 고유하게 식별할 수 없으며, MAC 어드레스 및 6LowPan 등에서 사용하는 IPv6 어드레스 역시 단일 센서 노드를 고정 식별하고, 메타데이터 서버와 연동하는 것이 불가능하다. 기존의 센서 네트워크에서 사용되는 주소체계들은 센서 노드를 고정되고 고유하게 식별하거나 해당 데이터가 저장되어 있는 데이터 서버의 접속정보를 룩업 또는 리졸빙하여 획득하는 것이 불가능하였기 때문에, 센서 노드에 고유한 식별자를 별도로 부여하여 사용한다.In order to link metadata stored in a distributed sensor metadata server with a sensor node, a method for uniquely identifying the metadata and the sensor node is required. The network address used in the sensor network such as ZigBee is dynamically changed according to the topology, so the sensor metadata and sensor node cannot be uniquely identified, and the IPv6 address used in MAC address and 6LowPan also fixedly identifies a single sensor node. It is not possible to work with metadata servers. The address schemes used in the existing sensor network cannot identify the sensor node with a fixed and unique address or look up or resolve the connection information of the data server where the data is stored. Used separately.
식별코드로는 EPC나 OID와 같이 시간과 장소에 관계없이 센서노드를 고유하게 식별할 수 있으며, 코드의 할당이 계층적인 구조 또는 트리구로 이루어져서, 메타데이터 서버의 검색(lookup)이 가능하도록 구성한다. 센서노드에 고유 코드를 할당하여 저장함으로서 센서노드를 고유하게 식별하고, 센서데이터의 전송 시에 센서노드에서 수집되는 데이터와 함께 전송된다.As identification code, sensor node can be uniquely identified regardless of time and place such as EPC or OID, and code assignment is composed of hierarchical structure or tree structure, so that lookup of metadata server is possible. . By assigning and storing a unique code to the sensor node, the sensor node is uniquely identified and transmitted along with data collected from the sensor node when the sensor data is transmitted.
센서노드에 부여된 식별코드가 본 발명에 따른 센서노드 관리장치(100)의 내부에 이미 저장되어 있는 경우에는 저장된 식별코드를 이용하여 센서노드에 접속할 수 있다. 그러나 식별코드가 사전에 저장되어 있지 않은 경우에는 센서데이터와 함께 전송된 식별코드를 추출하여야 한다. 이를 위하여 본 발명에 따른 센서노드 관리장치(100)는 식별코드 추출부(110)를 구비할 수 있다. 센서노드로부터 전송되는 데이터는 식별코드와 센서로부터 수집된 데이터를 포함하고 있으므로, 식별코드 추출부(110)는 전송된 데이터로부터 식별코드를 추출하여 주소획득부(120)에 제공한다.If the identification code assigned to the sensor node is already stored in the sensor node management apparatus 100 according to the present invention, the stored identification code may be used to access the sensor node. However, if the identification code is not stored in advance, the identification code transmitted with the sensor data should be extracted. To this end, the sensor node management apparatus 100 according to the present invention may include an identification code extraction unit 110. Since the data transmitted from the sensor node includes the identification code and the data collected from the sensor, the identification code extraction unit 110 extracts the identification code from the transmitted data and provides it to the address acquisition unit 120.
주소획득부(120)는 센서노드에 직접 접속하여 센서노드의 메타데이터가 저장되어 있는 데이터 서버의 주소를 획득할 수 있다. 이와 같이 데이터 서버의 주소를 센서노드로부터 직접 획득하는 경우에는 주소획득을 위해 별도의 장치가 필요없다는 장점이 있으나, 센서노드가 부가적으로 포인터를 포함하도록 함으로써 오버헤드가 발생할 수 있다는 문제가 있다. 따라서 센서노드의 식별코드를 기초로 데이터 서버의 주소를 획득할 수 있는 별도의 장치를 이용할 필요성이 있다.The address acquisition unit 120 may directly access a sensor node to obtain an address of a data server in which metadata of the sensor node is stored. As described above, in case of directly acquiring an address of a data server from a sensor node, there is an advantage in that a separate device is not required for acquiring an address, but there is a problem in that an overhead may be generated by additionally including a pointer to the sensor node. Therefore, there is a need to use a separate device that can obtain the address of the data server based on the identification code of the sensor node.
그에 따라 주소획득부(120)는 데이터 서버의 주소를 저장하고 있는 네이밍 서버에 접속하여 데이터 서버의 주소를 획득할 수 있다. 즉, 주소획득부(120)는 센서 네트워크를 구성하는 복수의 센서노드의 메타데이터가 저장된 데이터 서버의 접속정보가 각각의 센서노드에 부여된 고유의 식별코드에 대응되어 저장되어 있는 네이밍 서버에 접속하여 검색대상 센서노드의 식별코드에 대응하는 데이터 서버의 주소를 획득한다.Accordingly, the address acquisition unit 120 may obtain the address of the data server by accessing the naming server that stores the address of the data server. That is, the address acquisition unit 120 accesses a naming server in which connection information of a data server storing metadata of a plurality of sensor nodes constituting a sensor network is stored corresponding to a unique identification code assigned to each sensor node. To obtain the address of the data server corresponding to the identification code of the sensor node to be searched.
네이밍 서버를 이용하는 경우에는 데이터 서버의 주소를 획득하기 위해 센서노드에 접속할 필요가 없다. 대신에 주소획득부(120)는 네이밍 서버에 접속하여 센서노드에 부여된 식별코드를 제공함으로써 그에 대응하는 데이터 서버의 주소를 획득한다. 네이밍 서버의 데이터베이스에는 복수의 센서노드 각각에 부여된 각각의 식별코드에 대응하여 데이터 서버의 주소가 저장되어 있다.When using a naming server, it is not necessary to connect to the sensor node to obtain the address of the data server. Instead, the address acquisition unit 120 accesses the naming server and obtains the address of the data server corresponding thereto by providing an identification code assigned to the sensor node. In the database of the naming server, the address of the data server is stored corresponding to each identification code assigned to each of the plurality of sensor nodes.
네이밍 서버 내부에 데이터 서버의 주소를 저장하여 데이터베이스를 구축할 때, 단순히 식별코드와 데이터 서버의 주소를 1대 1로 대응시켜 저장할 수도 있지만, 일정한 분류기준에 의하여 저장하게 되면 뒤에 식별코드를 이용하여 주소를 검색할 때 용이하다. 이를 위해서는 식별코드가 이러한 분류기준을 포함하고 있어야 한다. 예를 들면, 식별코드에 센서노드의 제조사정보 또는 제품정보 등을 포함시켜 복수의 센서노드 중에서 동일한 제조사정보 또는 제품정보를 가지는 센서노드의 식별코드들을 따로 분류하여 저장할 수 있다. 또한 분류기준은 복수개가 될 수도 있으며, 복수의 분류기준이 있는 경우에는 이들을 상위기준과 하위기준으로 나누어 식별코드들을 계층적으로 분류하여 저장할 수 있다.When building a database by storing the address of the data server inside the naming server, you can simply store the identification code and the address of the data server in a one-to-one correspondence. It is easy when searching for an address. For this purpose, the identification code must contain these classification criteria. For example, by including manufacturer information or product information of a sensor node in an identification code, identification codes of sensor nodes having the same manufacturer information or product information among a plurality of sensor nodes may be classified and stored separately. In addition, the classification criteria may be plural, and when there are a plurality of classification criteria, the identification codes may be classified and stored in a hierarchical manner by dividing them into upper and lower standards.
이와 같이 복수의 분류기준을 포함하는 식별코드 중에서 EPC와 같이 전세계적으로 보편적인 코드를 사용하게 되면 식별코드의 고유성을 보장할 수 있으므로 각각의 센서노드에 식별코드를 부여하고 이를 기초로 데이터 서버의 주소를 분류하여 저장하는 것이 용이하다. EPC는 국제조직인 EPCglobal에서 기존의 코드 시스템을 통합하기 위해 만든 코드 체계이다. 도 2에 EPC 구성의 일 예가 도시되어 있다. 도 2를 참조하면, 식별코드는 헤더정보, 센서노드의 제조사정보, 센서노드의 제품정보 및 시리얼코드를 포함한다. 코드에 포함되는 정보는 사용상의 편리 및 코드의 발급과 관리 측면을 고려하여 다양한 형태로 구성할 수 있다. 도 2에 도시된 EPC 구성을 식별코드로 사용하는 경우에는 상위기준으로서 센서노드의 제조사정보를 기초로 복수의 식별코드에 대응하는 데이터 서버의 주소를 분류한 후, 하위기준으로서 센서노드의 제품정보를 기초로 데이터 서버의 주소를 다시 분류할 수 있다. 센서노드의 제조사정보 및 제품정보를 각각 상위기준과 하위기준으로 하여 데이터 서버 중 메타데이터 서버의 주소를 분류하고 저장한 일 예가 다음의 표 2에 나타나 있다.In this way, if the universal code such as EPC is used among the identification codes including a plurality of classification criteria, the uniqueness of the identification code can be guaranteed, so that the identification code is assigned to each sensor node and based on the data server. It is easy to sort and store addresses. EPC is a code system created by the international organization EPCglobal to integrate existing code systems. An example of an EPC configuration is shown in FIG. Referring to FIG. 2, the identification code includes header information, manufacturer information of a sensor node, product information of a sensor node, and a serial code. The information included in the code can be configured in various forms in consideration of convenience of use and issuance and management of the code. When the EPC configuration shown in FIG. 2 is used as an identification code, after classifying addresses of data servers corresponding to a plurality of identification codes based on the manufacturer information of the sensor node as a higher standard, the product information of the sensor node is used as a lower standard. You can reclassify the address of the data server based on. An example of classifying and storing the address of the metadata server among the data servers using the sensor node manufacturer information and the product information as the upper standard and the lower standard is shown in Table 2 below.
표 2
제조사정보 제품정보 메타데이터 서버 주소
A사 온도센서 http://icu.com/aaa
압력센서 http://icu.com/aab
광센서 http://icu.com/aac
B사 온도센서 http://icu.com/bba
압력센서 http://icu.com/bbb
광센서 http://icu.com/bbc
C사 온도센서 http://icu.com/cca
압력센서 http://icu.com/ccb
광센서 http://icu.com/ccc
TABLE 2
Manufacturer Information product information Metadata server address
A company temperature Senser http://icu.com/aaa
Pressure sensor http://icu.com/aab
Light sensor http://icu.com/aac
Company B temperature Senser http://icu.com/bba
Pressure sensor http://icu.com/bbb
Light sensor http://icu.com/bbc
Company C temperature Senser http://icu.com/cca
Pressure sensor http://icu.com/ccb
Light sensor http://icu.com/ccc
주소획득부(120)가 네이밍 서버에 접속하여 메타데이터 서버 주소의 분류기준을 포함하는 식별코드를 제공하면, 네이밍 서버에서는 식별코드로부터 분류기준을 추출하여 표 2와 같이 메타데이터 서버의 주소가 저장되어 있는 데이터베이스에서 주소획득부(120)로부터 입력된 식별코드에 대응하는 메타데이터 서버의 주소를 검색한다. 이때 식별코드에 포함된 분류기준이 복수 개인 경우에는 상위기준에 해당하는 분류기준을 먼저 추출하여 검색을 수행한다. 표 2를 참고하여 예를 들면, B사에서 제조한 온도센서의 메타데이터가 저장된 메타데이터 서버의 주소를 획득하기 위해 해당 센서의 식별코드가 네이밍 서버에 입력되었다면, 네이밍 서버에서는 먼저 상위기준인 제조사정보를 식별코드로부터 추출하여 B사로 분류된 메타데이터 서버 주소의 그룹을 검색한다. 다음으로 하위기준인 제품정보를 식별코드로부터 추출하여 온도센서에 해당하는 메타데이터 서버의 주소를 검색한다.When the address acquisition unit 120 accesses the naming server and provides an identification code including the classification criteria of the metadata server address, the naming server extracts the classification criteria from the identification code and stores the address of the metadata server as shown in Table 2 below. Search the address of the metadata server corresponding to the identification code input from the address acquisition unit 120 in the database. In this case, when there are a plurality of classification criteria included in the identification code, the classification criteria corresponding to the upper criteria are first extracted and searched. Referring to Table 2, for example, if the identification code of the sensor is entered in the naming server to obtain the address of the metadata server in which the metadata of the temperature sensor manufactured by Company B is stored, the naming server is the first manufacturer The information is extracted from the identification code to retrieve a group of metadata server addresses classified as Company B. Next, the product information, which is a lower standard, is extracted from the identification code to search the address of the metadata server corresponding to the temperature sensor.
이와 같이 네이밍 서버로부터 식별코드에 대응하는 데이터 서버의 주소를 획득하는 과정을 리졸빙(resolving)이라 하며, 주소획득부(120)는 위에서 언급한 방법으로 데이터 서버의 주소를 획득할 수도 있고, 종래에 사용되었던 리졸빙 방법을 사용하여 네이밍 서버로부터 데이터 서버의 주소를 획득할 수 있다. 예를 들면, 센서노드의 식별코드가 EPC와 같이 계층적인 구조를 갖는 경우에는 리졸빙의 한 가지 방법으로 ONS(object naming service)를 사용할 수 있다.The process of obtaining the address of the data server corresponding to the identification code from the naming server is called resolving, and the address obtaining unit 120 may obtain the address of the data server by the above-mentioned method. The resolving method used to obtain the address of the data server from the naming server. For example, when an identification code of a sensor node has a hierarchical structure such as an EPC, an object naming service (ONS) may be used as one method of resolving.
ONS는 웹 상에서 컴퓨터의 위치를 지정해주는 DNS(domain name service)와 유사한 방법으로 RFID 태그에 저장되어 있는 EPC에 해당되는 제품의 정보 위치를 제공하기 위한 프레임워크이다. ONS는 DNS 프레임워크 상에서 동작하며, ONS 질의에 대한 일반적인 수행절차가 도 3에 도시되어 있다. 도 3을 참조하면, RFID 리더가 RFID 태그에 저장되어 있는 비트 시퀀스로 이루어진 EPC를 읽어 로컬 서버로 보내면 로컬 서버는 EPC를 URI(Uniform Resource Identifier)로 변경하고, 로컬 ONS 리졸버(resolver)는 URI를 도메인 네임으로 변경하여 DNS 질의를 수행한다. DNS는 저장된 URL 중에서 질의의 결과에 해당하는 URL을 응답으로서 반환한다.ONS is a framework for providing information location of products corresponding to EPCs stored in RFID tags in a manner similar to the domain name service (DNS) that specifies the location of computers on the Web. ONS operates on the DNS framework, and a general procedure for ONS queries is shown in FIG. Referring to FIG. 3, when an RFID reader reads an EPC composed of a bit sequence stored in an RFID tag and sends it to a local server, the local server changes the EPC to a Uniform Resource Identifier (URI), and the local ONS resolver resolves the URI. Perform DNS query by changing to domain name. The DNS returns, as a response, the URL corresponding to the query result among the stored URLs.
위 수행절차를 주소획득부(120)가 네이밍 서버로부터 메타데이터 서버의 주소를 획득하는 과정에 적용하면, 네이밍 서버는 EPC 형태의 식별코드를 URI로 변경하고, 다음으로 URI를 도메인 네임으로 변경하어 저장된 메타데이터 서버의 주소 중에서 매치되는 주소를 찾는다. 다음으로 네이밍 서버는 검색된 메타데이터 서버의 주소를 응답으로 출력하여 주소획득부(120)에 제공한다. 도 4에는 주소획득부(120)가 센서노드에 부여된 식별코드를 네이밍 서버에 제공하여 메타데이터 서버의 주소를 획득하는 과정이 도시되어 있다.When the above procedure is applied to the process of obtaining the metadata server's address from the naming server, the naming server changes the identification code of the EPC type to the URI, and then changes the URI to the domain name. Find the matching address among the stored metadata server's addresses. Next, the naming server outputs the address of the retrieved metadata server as a response and provides the address acquisition unit 120. 4 illustrates a process in which the address obtaining unit 120 obtains an address of the metadata server by providing an identification code assigned to the sensor node to the naming server.
네이밍 서버로부터 출력된 응답이 IP 어드레스만으로 구성되는 A 레코드의 형식으로 출력되는 경우에는 이를 진보된 웹 서비스 리졸빙에 적용할 수 없다. 따라서 네이밍 서버는 프로토콜, 서비스 등을 나타내기 위해 복수의 필드를 가지는 NAPTR 레코드로 응답을 출력한다. 아래의 표 3은 네이밍 서버로부터 출력된 NAPTR 레코드 응답을 나타낸 것이다.If the response output from the naming server is output in the form of an A record consisting solely of IP addresses, it cannot be applied to advanced web service resolving. Therefore, the naming server outputs the response as a NAPTR record having a plurality of fields to indicate a protocol, a service, and the like. Table 3 below shows the NAPTR record response output from the naming server.
표 3
Order Pref Flag Service Regexp Desc.
0 2 u EPC+ws !^.*$!http://icu.com/widget.wsdl! EPC
0 1 u EPC+epcis !^.*$!http://icu.com/epcis.php! EPC
0 3 u EPC+html !^.*$!http://icu.com/things.asp! EPC
0 4 u EPC+mlrpc !^.*$!http://icu.com/example.com! EPC
0 5 u EPC+x+metadata "!^.*$!http://epc.onlinesensors.net/product/000024/index.html!" metadata
0 1 u EPC+x-metadata "!^.*$!http://epc.onlinesensors.net/metadata_exchanges.asmx?WSDL!" metadata
0 2 u EPC+x-metadata "!^.*$!http://epc.onlinesensors.net/metadata_exchanges.asmx/things!" metadata
TABLE 3
Order Pref Flag Service Regexp Desc.
0 2 u EPC + ws ! ^. * $! http: //icu.com/widget.wsdl! EPC
0 One u EPC + epcis ! ^. * $! http: //icu.com/epcis.php! EPC
0 3 u EPC + html ! ^. * $! http: //icu.com/things.asp! EPC
0 4 u EPC + mlrpc ! ^. * $! http: //icu.com/example.com! EPC
0 5 u EPC + x + metadata "! ^. * $! http: //epc.onlinesensors.net/product/000024/index.html!" metadata
0 One u EPC + x-metadata "! ^. * $! http: //epc.onlinesensors.net/metadata_exchanges.asmx? WSDL!" metadata
0 2 u EPC + x-metadata "! ^. * $! http: //epc.onlinesensors.net/metadata_exchanges.asmx/things!" metadata
표 3을 참조하면, 오더(order)필드와 pref필드는 정수값을 가진다. 플래그(flag)필드의 'u'는 응답이 URI를 포함하고 있다는 것을 의미한다. 서비스필드는 서비스의 타입을 나타내며, html, XMLRPC, EPCIS(EPC information service) 및 WS(web service) 등 서버가 지원하는 서비스에 따라 다양한 유형을 가질 수 있다. Regexp는 주소가 정규표현식(regular expression)으로 표현된다는 것을 의미한다. 따라서 검색된 메타데이터 서버의 주소를 나타내는 URL은 정규표현식 형태로 출력된다.Referring to Table 3, the order field and the pref field have integer values. A 'u' in the flag field means that the response contains a URI. The service field indicates a type of service and may have various types according to services supported by a server such as html, XMLRPC, EPC information service (EPCIS), and web service (WS). Regexp means that the address is expressed as a regular expression. Therefore, the URL representing the retrieved metadata server address is output in the form of regular expression.
ONS의 본래 기능은 RFID 리더가 읽은 EPC로부터 RFID 태그가 부착된 상품의 정보가 저장된 서버의 주소를 획득하는 것이다. 그러나 본 발명에서 주소획득부(120)가 네이밍 서버로부터 획득하고자 하는 것은 태그가 부착된 사물의 정보가 아닌 센서노드의 데이터가 저장된 서버의 주소이다.The original function of ONS is to obtain the address of the server that stores the information of the RFID tagged product from the EPC read by the RFID reader. However, in the present invention, what the address acquisition unit 120 wants to acquire from the naming server is the address of the server where the data of the sensor node is stored, not the information of the tagged object.
따라서 이와 같은 혼동을 방지하고 네이밍 서버의 응답이 센서데이터 서버 또는 메타데이터 서버의 주소를 나타내는 것임을 분명하게 하기 위해 NAPTR 레코드의 서비스필드를 구성하는 서비스의 타입으로 데이터 서버의 접속정보를 추가할 수 있다. 따라서 표 3에 나타낸 NAPTR 레코드 응답 중에서 서비스필드에 'EPC+x-metadata'로 표시된 부분은 출력된 응답이 메타데이터 서버의 접속정보를 제공함을 의미하며, 정규표현식으로 기재된 주소는 메타데이터 서버의 주소임을 나타내는 것이다. 또한 서비스필드에 센서데이터 서버의 주소임을 나타내는 서비스 타입을 추가한다면, 출력된 응답이 센서데이터 서버의 접속정보를 제공함을 의미한다.Therefore, in order to prevent such confusion and to clarify that the naming server's response indicates the address of the sensor data server or the metadata server, the access information of the data server may be added as a type of service constituting the service field of the NAPTR record. . Therefore, the part indicated as 'EPC + x-metadata' in the service field among the NAPTR record responses shown in Table 3 means that the outputted response provides the connection information of the metadata server, and the address indicated by the regular expression is the address of the metadata server. It indicates that. Also, if a service type indicating the address of the sensor data server is added to the service field, it means that the outputted response provides connection information of the sensor data server.
주소획득부(120)가 센서노드로부터 직접 데이터 서버의 주소를 획득하거나 네이밍 서버로부터 데이터 서버의 주소를 획득하면, 데이터 획득부(130)는 그 주소에 위치하는 데이터 서버에 접속하여 저장된 데이터를 획득한다. 데이터 서버에는 데이터가 적절한 기준에 의해 그룹으로 분류되어 저장되어 있으며, 전체 데이터 또는 필요에 의해 선택된 그룹의 데이터만을 획득할 수 있다. 그 일 예로서, 도 5에는 데이터 획득부(130)가 메타데이터 서버로부터 획득하고자 하는 메타데이터에 관하여 질의하고 응답받는 인터페이스의 한 예가 도시되어 있다. 메타데이터 서버에 접속하기 위해서 TCP, UDP 등의 통신 프로토콜을 이용하여 질의 메시지를 정의하거나, 인터넷 프로토콜인 HTTP 또는 웹서비스인 SOAP를 사용할 수 있다.When the address obtaining unit 120 obtains the address of the data server directly from the sensor node or obtains the address of the data server from the naming server, the data obtaining unit 130 accesses the data server located at the address to obtain the stored data. do. In the data server, data is classified and stored in groups according to appropriate criteria, and all data or only data of a group selected as needed can be obtained. As an example, FIG. 5 illustrates an example of an interface in which the data obtaining unit 130 queries and responds to metadata to be obtained from the metadata server. In order to access the metadata server, query messages can be defined using communication protocols such as TCP and UDP, or SOAP, an Internet protocol, or HTTP, can be used.
센서노드 관리부(150)는 메타데이터에 포함된 정보를 기초로 검색대상 센서노드에 접속하여 제어 메시지를 전송한다. 제어 메시지를 전송하기 위해서는 검색대상 센서노드에 접속하여야 하는데, 이때 센서노드로부터 전송된 데이터에 포함된 식별코드를 사용할 수 있다.The sensor node manager 150 accesses a sensor node to be searched based on the information included in the metadata and transmits a control message. In order to transmit the control message, the sensor node should be connected to a search target sensor node. In this case, an identification code included in data transmitted from the sensor node may be used.
식별코드를 사용하여 센서노드에 접속할 경우에 대상 식별코드를 포함하는 브로드캐스트 메시지를 전송하여 해당 식별코드에 대응하는 센서노드와 통신할 수 있다. 그러나 각 전송 메시지에 포함되는 식별코드의 길이로 인해서 센서 노드간 통신에 추가적인 오버헤드가 발생할 수 있다는 문제점이 있다. 식별코드는 센서 노드에 고정되어 할당되어 전 세계에서 고유한 값이므로 센서 노드 내부에서만 일시적으로 유일하도록 사용되는 센서 네트워크 주소에 비교할 때 매우 길기 때문에, 센서 노드에서 전송되는 메시지에 포함되어 전송하게 되면 성능 상에 제약이 될 수 있다. 또한 식별코드가 어드레스가 아니기 때문에 센서노드와 직접 유니캐스트 방식의 통신에는 사용할 수 없다.When accessing a sensor node using an identification code, a broadcast message including a target identification code may be transmitted to communicate with a sensor node corresponding to the identification code. However, there is a problem that additional overhead may occur in communication between sensor nodes due to the length of the identification code included in each transmission message. Because the identification code is fixed and assigned to the sensor node and is unique worldwide, it is very long when compared to the sensor network address that is used only temporarily inside the sensor node. Can be a constraint on the phase. Also, because the identification code is not an address, it cannot be used for direct unicast communication with the sensor node.
따라서 실제로 식별코드를 이용하여 센서노드에 접속하기 위해서는 식별코드를 센서 노드 간 라우팅을 위한 네트워크 주소, 예를 들면, ZigBee의 네트워크 어드레스로 변환하거나 센서 노드 간 통신 메시지의 길이를 최대한 줄일 수 있는 짧은 길이의 식별코드로 변환하여 통신하여야 한다. 짧은 길이의 식별코드는 센서 노드에 고정되어 전세계에 고유하게 할당된 식별코드와는 다르게 해당 센서 네트워크 내부에서만 유일하도록 보장된다. 바람직한 실시예로는 센서 노드에 고정되어 부여된 고유 식별코드를 가지는 센서 노드에 대해서 순차적으로 자연수로 구성되는 짧은 식별코드를 할당하고 해당 테이블을 구성함으로써, 실제 센서 네트워크 노드 간 통신을 위해서는 센서 노드에 고정되어 할당된 고유 식별코드 대신에 해당 자연수로 구성된 짧은 길이의 일시적으로 유일한 식별코드를 이용할 수 있다.Therefore, in order to actually connect to the sensor node using the identification code, the identification code is converted into a network address for routing between sensor nodes, for example, a network address of ZigBee, or a short length that can shorten the length of the communication message between sensor nodes as much as possible. It should be converted into the identification code of and communicated. The short length identification code is fixed to the sensor node and, unlike the uniquely assigned identification code around the world, is guaranteed to be unique only within the sensor network. In a preferred embodiment, a short identification code consisting of a natural number is sequentially assigned to a sensor node having a unique identification code fixedly assigned to the sensor node, and a corresponding table is configured, so that the actual communication between the sensor network nodes is performed at the sensor node. Instead of a fixed, uniquely assigned unique identification code, a short, uniquely unique identification code of natural numbers may be used.
이를 위해 본 발명에 따른 센서노드 관리장치(100)는 이를 위해 센서노드 접속정보 저장부(140)를 더 구비할 수 있다. 센서노드 관리부(150)는 검색대상 센서노드에 접속하기 위해 센서노드 접속정보 저장부(140)에서 식별코드에 대응하는 검색대상 센서노드의 접속정보를 획득한다. 센서노드에 고정되어 할당된 고유 식별코드와 그에 해당하는 네트워크 주소 또는 짧은 길이의 식별코드에 대한 접속정보는 베이스 스테이션의 센서노드 접속정보 저장부(140)에 등록되며, 센서노드의 네트워크 주소가 변경되거나 토폴로지가 변경되는 시점마다 센서 노드에 요청에 의해서 동적으로 업데이트된다.To this end, the sensor node management apparatus 100 according to the present invention may further include a sensor node access information storage unit 140 for this purpose. The sensor node manager 150 obtains the connection information of the searched sensor node corresponding to the identification code from the sensor node connection information storage 140 to access the searched sensor node. Access information about the unique identification code and its corresponding network address or short length identification code fixedly assigned to the sensor node is registered in the sensor node access information storage unit 140 of the base station, and the network address of the sensor node is changed. At each point in time, or when the topology changes.
검색대상 센서노드에 질의 메시지 또는 제어명령을 전송하기 위해 센서노드에 접속할 때 센서노드 접속정보 저장부(140)에 저장된 변환테이블로부터 센서노드의 식별코드에 대응하는 접속정보를 획득할 수 있다.When the sensor node is connected to the sensor node to transmit a query message or a control command to the searched sensor node, the connection information corresponding to the identification code of the sensor node may be obtained from the conversion table stored in the sensor node connection information storage 140.
도 6에는 메타데이터 서버로부터 획득한 메타데이터 중에서 센서노드에 전송할 질의 메시지의 포맷의 일 예가 도시되어 있다.FIG. 6 illustrates an example of a format of a query message to be transmitted to a sensor node among metadata obtained from a metadata server.
한편 센서노드가 지그비(zigbee) 장치인 경우의 메타데이터에 포함된 메시지의 일 예는 다음과 같다.Meanwhile, an example of a message included in metadata when a sensor node is a zigbee device is as follows.
<메시지><Message>
<?xml version="1.0" encoding="UTF-8"?><? xml version = "1.0" encoding = "UTF-8"?>
<profile><profile>
<Identifier><Identifier>
<type>SGTIN-96</type><type> SGTIN-96 </ type>
<value>307427D58B0D47C000000001</value><value> 307427D58B0D47C000000001 </ value>
</Identifier></ Identifier>
<NodeDescriptor><NodeDescriptor>
<LogicalType description="ZigBee end device">010</LogicalType><LogicalType description = "ZigBee end device"> 010 </ LogicalType>
<ComplexDescriptorAvailable description="true">1</ComplexDescriptorAvailable><ComplexDescriptorAvailable description = "true"> 1 </ ComplexDescriptorAvailable>
<UserDescriptorAvailable description="true">1</UserDescriptorAvailable><UserDescriptorAvailable description = "true"> 1 </ UserDescriptorAvailable>
<Reserved description="reserved">0</Reserved><Reserved description = "reserved"> 0 </ Reserved>
<APS_Flags description="APS_Flag">0</APS_Flags><APS_Flags description = "APS_Flag"> 0 </ APS_Flags>
<FrequencyBand description="902-928MHz">2</FrequencyBand><FrequencyBand description = "902-928MHz"> 2 </ FrequencyBand>
<MAC_CapabilityFlags description="FFD, main powers, disabled receiver during idle periods,no security">7</MAC_CapabilityFlags><MAC_CapabilityFlags description = "FFD, main powers, disabled receiver during idle periods, no security"> 7 </ MAC_CapabilityFlags>
<ManufacturerCode description="sample manufacturer">0x02</ManufacturerCode><ManufacturerCode description = "sample manufacturer"> 0x02 </ ManufacturerCode>
<MaximumBufferSize description="0x7ff">0x7ff</MaximumBufferSize><MaximumBufferSize description = "0x7ff"> 0x7ff </ MaximumBufferSize>
<MaximumIncomingTransferSize description="0x7fff">0x7fff</MaximumIncomingTransferSize><MaximumIncomingTransferSize description = "0x7fff"> 0x7fff </ MaximumIncomingTransferSize>
<ServerMask description="Primary Trust Center">1</ServerMask><ServerMask description = "Primary Trust Center"> 1 </ ServerMask>
<MaxiumOutgoingTransferSize description="0x7fff">0x7fff</MaxiumOutgoingTransferSize><MaxiumOutgoingTransferSize description = "0x7fff"> 0x7fff </ MaxiumOutgoingTransferSize>
<DescriptorCapabilityField description="0">0</DescriptorCapabilityField><DescriptorCapabilityField description = "0"> 0 </ DescriptorCapabilityField>
</NodeDescriptor></ NodeDescriptor>
<NodePowerDescriptor><NodePowerDescriptor>
<CurrentPowerMode<CurrentPowerMode
description="Receiver synchronized with the receiver on when idel sub-field of the node descriptor.">0000</CurrentPowerMode>description = "Receiver synchronized with the receiver on when idel sub-field of the node descriptor."> 0000 </ CurrentPowerMode>
<AvailablePowerSource description="Disposable battery">2</AvailablePowerSource><AvailablePowerSource description = "Disposable battery"> 2 </ AvailablePowerSource>
<CurrentPowerSource description="Rechargeable battery">1</CurrentPowerSource><CurrentPowerSource description = "Rechargeable battery"> 1 </ CurrentPowerSource>
<CurrentPowerSourceLevel description="33%">0100</CurrentPowerSourceLevel><CurrentPowerSourceLevel description = "33%"> 0100 </ CurrentPowerSourceLevel>
</NodePowerDescriptor></ NodePowerDescriptor>
<SimpleDescriptor><SimpleDescriptor>
<EndPoint description="10">10</EndPoint><EndPoint description = "10"> 10 </ EndPoint>
<ApplicationProfileIdentifier description="Home Automation Profile Specification">0x0104</ApplicationProfileIdentifier><ApplicationProfileIdentifier description = "Home Automation Profile Specification"> 0x0104 </ ApplicationProfileIdentifier>
<ApplicationDeviceIdentifier description="ZCL_HA_DEVICEID_ON_OFF_SWITCH">0x0000</ApplicationDeviceIdentifier><ApplicationDeviceIdentifier description = "ZCL_HA_DEVICEID_ON_OFF_SWITCH"> 0x0000 </ ApplicationDeviceIdentifier>
<ApplicationDeviceVersion description="Ver0.8">0011</ApplicationDeviceVersion><ApplicationDeviceVersion description = "Ver0.8"> 0011 </ ApplicationDeviceVersion>
<ApplicationInputClusterCounter description="one">1</ApplicationInputClusterCounter><ApplicationInputClusterCounter description = "one"> 1 </ ApplicationInputClusterCounter>
<ApplicationInputClusterList description="ZCL_HA_CLUSTER_ID_GEN_BASIC">0x0000</ApplicationInputClusterList><ApplicationInputClusterList description = "ZCL_HA_CLUSTER_ID_GEN_BASIC"> 0x0000 </ ApplicationInputClusterList>
<ApplicationOutputClusterCount description="one">1</ApplicationOutputClusterCount><ApplicationOutputClusterCount description = "one"> 1 </ ApplicationOutputClusterCount>
<ApplicationOutputClusterList description="ZCL_HA_CLUSTER_ID_GEN_ON_OFF">0x0006</ApplicationOutputClusterList><ApplicationOutputClusterList description = "ZCL_HA_CLUSTER_ID_GEN_ON_OFF"> 0x0006 </ ApplicationOutputClusterList>
</SimpleDescriptor></ SimpleDescriptor>
<ComplexDescriptor><ComplexDescriptor>
<LanguageAndCharacterSet><LanguageAndCharacterSet>
<LanguageCode description="Korean">ko</LanguageCode><LanguageCode description = "Korean"> en </ LanguageCode>
<CharacterSetIdentifier description="ASCII character set">0x00</CharacterSetIdentifier><CharacterSetIdentifier description = "ASCII character set"> 0x00 </ CharacterSetIdentifier>
</LanguageAndCharacterSet></ LanguageAndCharacterSet>
<ManufacturerName description="online sensors company">online sensors company</ManufacturerName><ManufacturerName description = "online sensors company"> online sensors company </ ManufacturerName>
<ModelName description="ants-zigbee-98">ants-zigbee-98</ModelName><ModelName description = "ants-zigbee-98"> ants-zigbee-98 </ ModelName>
<SerialNumber description="1">1</SerialNumber><SerialNumber description = "1"> 1 </ SerialNumber>
<DeviceURL description="http://onlinesensors.net">http://onlinesensors.net</DeviceURL><DeviceURL description = "http://onlinesensors.net"> http://onlinesensors.net </ DeviceURL>
<Icond/><Icond />
<IconURL>http://onlinesensors.net/sample/icons</IconURL><IconURL> http://onlinesensors.net/sample/icons </ IconURL>
<presentation/><presentation />
<presentationURL>http://onlinesensors.net/sample/node1.jpg</presentationURL><presentationURL> http://onlinesensors.net/sample/node1.jpg </ presentationURL>
</ComplexDescriptor></ ComplexDescriptor>
<UserDescription/><UserDescription />
</ZigBeeDescriptor></ ZigBeeDescriptor>
<Devices><Devices>
<Clusters><Clusters>
<ServerSide><ServerSide>
<Cluster name="On/Off"><Cluster name = "On / Off">
<option>Mandatory</option> <option> Mandatory </ option>
<Server><Server>
<AttributeSetList> <AttributeSetList>
<AttributeSet><AttributeSet>
<AttributesList> <AttributesList>
<Attributes> <Attributes>
<Identifier>0x0000</Identifier> <Identifier> 0x0000 </ Identifier>
<Name>OnOff</Name> <Name> OnOff </ Name>
<Type>Boolean</Type> <Type> Boolean </ Type>
<Range>0x00-0x01</Range> <Range> 0x00-0x01 </ Range>
<Access>Read only</Access> <Access> Read only </ Access>
<Default>0x00</Default> <Default> 0x00 </ Default>
<Option>Mandatory</Option> <Option> Mandatory </ Option>
<Value description="On">1</Value> <Value description = "On"> 1 </ Value>
<Value description="Off">0</Value> <Value description = "Off"> 0 </ Value>
</Attributes></ Attributes>
</AttributesList></ AttributesList>
<CommandsReceived><CommandsReceived>
<Commands><Commands>
<Identifier>0x02</Identifier> <Description>Toggle</Description> <Option>Mandatory</Option><Identifier> 0x02 </ Identifier> <Description> Toggle </ Description> <Option> Mandatory </ Option>
<Payload></Payload><Payload> </ Payload>
</Commands></ Commands>
</CommandsReceived></ CommandsReceived>
</Server></ Server>
</Cluster> </ Cluster>
</ServerSide></ ServerSide>
</clusters></ clusters>
</devices></ devices>
</profile></ profile>
위 메시지를 참조하면, 메타데이터는 3가지 블록인 <identifier>블럭, <ZigBeeDescriptor>블럭, <device>블럭을 포함한다. <identifier>는 EPC 정보를 나타내며 타입과 센서노드에 할당된 식별자를 보여준다. <ZigBeeDescriptor>블럭은 ZigBee에서 정의하고 있는 모든 정적인 Descriptor의 내용을 포함하고 있다. 기존 ZigBee에서는 Descriptor로 2개의 필수 Descriptor와 3개의 선택적인 Descriptor를 정의하고 있으며, ZigBee에서 제공하는 Service Discovery를 통해서 이들 Descriptor를 특정 센서 노드로 요청하고 Descriptor의 내용을 받아올 수 있다. 그러나 Descriptor 중에서 정적이지 않은 데이터 즉 node power descriptors의 power level 필드와 같은 동적으로 센서노드에서 수집되어야 하는 값은 메타데이터에 포함되지 않는다. <ZigBeeDescriptor>블럭은 센서 노드의 특징적인 내용을 서술하게 되며 특히 profile ID, input cluster 및 output cluster의 List, Endpoint를 포함한다.Referring to the above message, the metadata includes three blocks, an <identifier> block, a <ZigBeeDescriptor> block, and a <device> block. <identifier> represents EPC information and shows type and identifier assigned to sensor node. The <ZigBeeDescriptor> block contains the contents of all the static Descriptors defined in ZigBee. Existing ZigBee defines two mandatory Descriptors and three optional Descriptors as Descriptors. Through Service Discovery provided by ZigBee, these Descriptors can be requested to specific sensor nodes and the contents of Descriptors can be received. However, non-static data among Descriptors, that is, values that should be dynamically collected from the sensor node such as the power level field of node power descriptors, are not included in the metadata. The <ZigBeeDescriptor> block describes the characteristic content of the sensor node. In particular, the <ZigBeeDescriptor> block contains the Profile ID, List, and Endpoint of the input cluster and output cluster.
<device>블럭은 센서노드에서 구현되어 있는 기능명세의 정보를 보여준다. 특히, ZigBee의 예에서 <device> 블록에서는 센서노드에서 구현되어 있는 클러스터를 서술한다. ZigBee cluster library (ZCL)은 응용에서 사용되는 다양한 기능들과 무관하게 재사용될 수 있는 클러스터들의 집합이며, <device> 블록은 속성 (attributes)와 명령어 (commands)를 포함한다. 위 메시지에 해당하는 센서노드는 On/Off 스위치 액츄에이팅 기능을 가지는 센서노드이며, 상태를 표현하는 On/Off 속성을 가지며, 스위치의 상태를 변경하기 위한 Toggle 명령어를 정의하고 있다.The <device> block shows the functional specification information implemented in the sensor node. In particular, in the ZigBee example, the <device> block describes the cluster implemented in the sensor node. ZigBee cluster library (ZCL) is a collection of clusters that can be reused regardless of the various functions used in the application. The <device> block contains attributes and commands. The sensor node corresponding to the above message is a sensor node with On / Off switch actuating function, has On / Off attribute representing the state, and defines a Toggle command to change the state of the switch.
본 발명에 따른 센서노드 관리장치(100)는 선택적으로 메타데이터의 작동 명세를 보여주고 사용자의 입력을 받는 GUI를 구현할 수 있으며, 사용자의 입력 또는 자동화된 스크립트를 통해서 메타데이터의 속성 또는 명령어를 이용할 수 있다. 특히, ZigBee에서는 위 메시지의 On/Off 스위치의 메타데이터에는 속성(attribute)과 각 커맨드(Toggle)마다 고유 커맨드 식별자가 정의되어 있고, ZigBee 스택에서는 이러한 속성을 억세스하고 커맨드를 이용하기 위한 표준 커맨드와 프레임포맷을 제공하고 있어서, 메타데이터 정보를 바탕으로 센서노드와 통신하는 것이 가능하다.Sensor node management apparatus 100 according to the present invention can optionally show the operation specification of the metadata and implement a GUI that receives the user's input, using the attributes or commands of the metadata through the user's input or automated script Can be. In particular, in ZigBee, the metadata of the On / Off switch of the above message defines attributes and unique command identifiers for each command. In the ZigBee stack, standard commands for accessing these attributes and using commands are provided. By providing a frame format, it is possible to communicate with sensor nodes based on metadata information.
도 7은 메타데이터에서 기술하고 있는 속성과 커맨드를 이용해서 센서노드와 통신하기 위한 ZigBee 스팩의 표준 ZCL (ZigBee Cluster Library) 프레임 포맷이다. 표준 프레임 포맷이 정의되어 있고, 각각의 필드의 의미가 표준으로 되어 있기 때문에 ZigBee를 구현하고 있는 센서 노드는 해당 프레임 포맷으로 통신을 할 수 있지만, 프레임 포맷의 내용은 센서노드가 제공하는 기능에 따라서 다르게 되기 때문에, 메타데이터를 디코딩하여서 특정 속성과 커맨드에 맞는 값을 사용하여서, 프레임을 구성하고 센서노드에게 전송을 하게 된다.7 is a ZigBee specification standard ZCL (ZigBee Cluster Library) frame format for communicating with sensor nodes using attributes and commands described in metadata. Since the standard frame format is defined and the meaning of each field is standard, the sensor node implementing ZigBee can communicate in the corresponding frame format. However, the contents of the frame format depend on the functions provided by the sensor node. Because it is different, the metadata is decoded to construct a frame and send it to the sensor node using values appropriate for specific attributes and commands.
도 8은 도 7의 프레임포맷을 따르는 메시지의 예이다. 이는 사용자가 ZigBee 기반의 light 센서노드에게 toggle 명령을 보내주는 예이다. switch 센서노드의 메타데이터를 참고함으로서 light 센서노드가 제공되는 기능명세를 파악하고, 사용자의 입력 또는 자동화된 스크립트에 따라서 ZCL command를 구성한다. 메타데이터를 디코딩함으로써 해당 장치가 light 장치이며, toggle 명령을 제공하는 것을 알 수 있으며, toggle 명령을 이용하기 위해서 toggle 명령어의 식별자 및 기타 정보 (Endpoint, cluster ID, APS profile ID, APS Src Endpint, APS command)의 값을 얻을 수 있다. 따라서, 도 8의 프레임포맷에 맞추어서 toggle 명령어를 가지는 메시지 프레임을 구성할 수 있다. 본 예에서 APS Dest Endpoint=0x0A, APS cluster ID=0x06, APS profile ID=0x0400, APS Src Endpint=0x01이며, APS payload의 command는 0x02 이다.8 is an example of a message that follows the frame format of FIG. This is an example of a user sending a toggle command to a ZigBee-based light sensor node. By referring to the metadata of the switch sensor node, the function specification provided by the light sensor node is identified, and the ZCL command is configured according to user input or automated script. By decoding the metadata, you can see that the device is a light device and provides a toggle command. To use the toggle command, the identifier and other information of the toggle command (Endpoint, cluster ID, APS profile ID, APS Src Endpint, APS). command) can be obtained. Accordingly, a message frame having a toggle command can be configured according to the frame format of FIG. 8. In this example, APS Dest Endpoint = 0x0A, APS cluster ID = 0x06, APS profile ID = 0x0400, APS Src Endpint = 0x01, and the APS payload command is 0x02.
이상에서 설명한 바와 같이 검색대상 센서노드로 보내지는 메시지는 검색대상 센서노드에 고정된 고유 식별코드를 기초로 하여서 전송될 수 있으며, 또한 센서노드 접속정보 저장부(140)가 이용될 경우에는 검색대상 센서노드의 네트워크 어드레스 또는 메시지의 크기를 줄이기 위하여 할당받은 짧은 식별코드를 수신 식별자로 하여 검색대상 센서노드로 전송될 수 있다.As described above, the message sent to the search target sensor node may be transmitted based on a unique identification code fixed to the search target sensor node, and when the sensor node access information storage unit 140 is used, the search target In order to reduce the size of a network address or a message of a sensor node, a short identifier assigned to the sensor node may be transmitted as a receiving identifier to a search target sensor node.
이와 같이 본 발명에 따른 센서노드 관리장치(100)를 이용하면, 센서노드에 부여된 식별코드를 기초로 데이터 서버로부터 메타데이터를 획득하는 것 뿐만 아니라 획득한 메타데이터에 포함된 정보를 기초로 센서노드에 적절한 질의메시지 또는 제어명령을 전송하여 능동적으로 센서 네트워크를 활용할 수 있다.As described above, when the sensor node management apparatus 100 according to the present invention is used, not only the metadata is obtained from the data server based on the identification code assigned to the sensor node, but also the sensor is based on the information included in the acquired metadata. The sensor network can be actively used by sending the appropriate query message or control command to the node.
도 9는 본 발명에 따른 메타데이터에 기반한 센서노드 관리방법의 바람직한 실시예의 수행과정을 도시한 흐름도이다.9 is a flowchart illustrating a preferred embodiment of a method for managing a sensor node based on metadata according to the present invention.
도 9를 참조하면, 센서 네트워크를 구성하는 복수의 센서노드 중 검색대상 센서노드에 부여된 고유의 식별코드가 사전에 저장되어 있지 않은 경우에, 식별코드 추출부(110)는 검색대상 센서노드에서 전송된 데이터로부터 검색대상 센서노드에 부여된 식별코드를 추출한다(S910). 다음으로 주소획득부(120)는 복수의 센서노드의 메타데이터가 저장된 데이터 서버의 접속정보가 각각의 센서노드에 부여된 식별코드에 대응하여 저장되어 있는 네이밍 서버에 접속하여 검색대상 센서노드의 식별코드에 대응하는 데이터 서버의 접속정보를 획득한다(S920).Referring to FIG. 9, when a unique identification code assigned to a search target sensor node is not stored in advance among the plurality of sensor nodes constituting the sensor network, the identification code extracting unit 110 may perform a search on the sensor node. The identification code assigned to the search target sensor node is extracted from the transmitted data (S910). Next, the address acquisition unit 120 accesses a naming server in which connection information of a data server storing metadata of a plurality of sensor nodes is stored corresponding to an identification code assigned to each sensor node to identify a sensor node to be searched. Access information of the data server corresponding to the code is obtained (S920).
이때 식별코드가 센서노드의 제조사정보 또는 제품정보 등을 포함하고 있으면, 네이밍 서버에는 식별코드에 포함된 정보 중에서 적어도 하나를 분류기준으로 하여 데이터 서버의 주소가 저장된다. 분류기준이 복수개인 경우에는 각각의 분류기준을 상위기준 및 하위기준으로 나누어 데이터 서버의 주소를 계층적으로 분류한다.In this case, if the identification code includes manufacturer information or product information of the sensor node, the naming server stores the address of the data server based on at least one of the information included in the identification code as a classification criterion. In the case of multiple classification criteria, the classification of the data server is classified hierarchically by dividing each classification criteria into upper and lower criteria.
다음으로 데이터 획득부(130)는 획득한 데이터 서버의 접속정보에 대응하는 데이터 서버에 접속하여 검색대상 센서노드의 식별코드에 대응하는 메타데이터를 획득한다(S930). 마지막으로 센서노드 관리부(150)는 획득된 메타데이터에 포함된 정보, 즉 통신 메시지 포맷을 이용하여 검색대상 센서노드로 질의메시지 또는 제어명령을 전송한다(S940).Next, the data acquisition unit 130 accesses the data server corresponding to the obtained access information of the data server and acquires metadata corresponding to the identification code of the sensor node to be searched for (S930). Finally, the sensor node manager 150 transmits an inquiry message or a control command to the sensor node to be searched by using information included in the acquired metadata, that is, a communication message format (S940).
본 발명은 또한 컴퓨터로 읽을 수 있는 기록매체에 컴퓨터가 읽을 수 있는 코드로서 구현하는 것이 가능하다. 컴퓨터가 읽을 수 있는 기록매체는 컴퓨터 시스템에 의하여 읽혀질 수 있는 데이터가 저장되는 모든 종류의 기록장치를 포함한다. 컴퓨터가 읽을 수 있는 기록매체의 예로는 ROM, RAM, CD-ROM, 자기 테이프, 플로피디스크, 광데이터 저장장치 등이 있으며, 또한 캐리어 웨이브(예를 들어 인터넷을 통한 전송)의 형태로 구현되는 것도 포함한다. 또한 컴퓨터가 읽을 수 있는 기록매체는 네트워크로 연결된 컴퓨터 시스템에 분산되어 분산방식으로 컴퓨터가 읽을 수 있는 코드가 저장되고 실행될 수 있다.The invention can also be embodied as computer readable code on a computer readable recording medium. The computer-readable recording medium includes all kinds of recording devices in which data that can be read by a computer system is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, and the like, and may also be implemented in the form of a carrier wave (for example, transmission over the Internet). Include. The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.
이상에서 본 발명의 바람직한 실시예에 대해 도시하고 설명하였으나, 본 발명은 상술한 특정의 바람직한 실시예에 한정되지 아니하며, 청구범위에서 청구하는 본 발명의 요지를 벗어남이 없이 당해 발명이 속하는 기술분야에서 통상의 지식을 가진 자라면 누구든지 다양한 변형 실시가 가능한 것은 물론이고, 그와 같은 변경은 청구범위 기재의 범위 내에 있게 된다.Although the preferred embodiments of the present invention have been shown and described above, the present invention is not limited to the specific preferred embodiments described above, and the present invention belongs to the present invention without departing from the gist of the present invention as claimed in the claims. Various modifications can be made by those skilled in the art, and such changes are within the scope of the claims.

Claims (21)

  1. 센서 네트워크를 구성하는 복수의 센서노드의 메타데이터가 저장된 데이터 서버의 접속정보를 보유하고 있는 외부장치로부터 검색대상 센서노드의 식별코드에 대응하는 데이터 서버의 접속정보를 획득하는 주소획득부;An address obtaining unit for obtaining access information of a data server corresponding to an identification code of a sensor node to be searched from an external device having access information of a data server storing metadata of a plurality of sensor nodes constituting a sensor network;
    상기 획득한 데이터 서버의 접속정보에 대응하는 데이터 서버에 접속하여 상기 검색대상 센서노드의 식별코드에 대응하는 메타데이터를 획득하는 데이터 획득부; 및A data acquisition unit accessing a data server corresponding to the obtained access information of the data server and acquiring metadata corresponding to the identification code of the sensor node to be searched; And
    상기 메타데이터에 포함된 정보를 기초로 상기 검색대상 센서노드에 접속하여 제어 메시지를 전송하는 센서노드 관리부;를 포함하는 것을 특징으로 하는 센서노드 관리장치.And a sensor node manager for accessing the searched sensor node and transmitting a control message based on the information included in the metadata.
  2. 제 1항에 있어서,The method of claim 1,
    상기 외부장치는 상기 데이터 서버의 접속정보가 상기 각각의 센서노드에 부여된 고유의 식별코드에 대응되어 저장되어 있는 네이밍 서버인 것을 특징으로 하는 센서노드 관리장치.The external device is a sensor node management device, characterized in that the access information of the data server is stored in correspondence with a unique identification code assigned to each sensor node.
  3. 제 1항에 있어서,The method of claim 1,
    상기 외부장치는 상기 검색대상 센서노드인 것을 특징으로 하는 센서노드 관리장치.The external device is a sensor node management device, characterized in that the search target sensor node.
  4. 제 1항 또는 제 2항에 있어서,The method according to claim 1 or 2,
    상기 검색대상 센서노드의 접속정보가 상기 검색대상 센서노드에 부여된 식별코드에 대응하여 저장되는 센서노드 접속정보 저장부를 더 포함하는 것을 특징으로 하는 센서노드 관리장치.And a sensor node access information storage unit, in which access information of the sensor node to be searched is stored corresponding to an identification code assigned to the sensor node to be searched.
  5. 제 1항 또는 제 2항에 있어서,The method according to claim 1 or 2,
    상기 검색대상 센서노드에서 전송된 데이터로부터 상기 검색대상 센서노드에 부여된 고유의 식별코드를 추출하는 식별코드 추출부를 더 포함하는 것을 특징으로 하는 센서노드 관리장치.Sensor node management apparatus further comprises an identification code extraction unit for extracting a unique identification code assigned to the search target sensor node from the data transmitted from the search target sensor node.
  6. 제 2항에 있어서,The method of claim 2,
    상기 식별코드는 상기 센서노드의 제조사정보 및 상기 센서노드의 제품정보 중에서 적어도 하나를 포함하며,The identification code includes at least one of manufacturer information of the sensor node and product information of the sensor node,
    상기 네이밍 서버에는 상기 데이터 서버의 접속정보가 상기 센서노드의 제조사정보 및 상기 센서노드의 제품정보 중에서 상기 식별코드에 포함되어 있는 정보 중 적어도 하나를 분류기준으로 하여 저장되는 것을 특징으로 하는 센서노드 관리장치.The naming server stores the connection information of the data server based on at least one of information included in the identification code among the manufacturer information of the sensor node and the product information of the sensor node as a classification criteria. Device.
  7. 제 6항에 있어서,The method of claim 6,
    상기 주소획득부는 상기 네이밍 서버로부터 정규표현식으로 표현된 상기 데이터 서버의 접속정보 및 서비스필드를 포함하는 레코드 형식의 응답을 획득하고,The address obtaining unit obtains a response in the form of a record including the access information and the service field of the data server represented by a regular expression from the naming server,
    상기 서비스필드에는 상기 데이터 서버의 접속정보가 기록되는 것을 특징으로 하는 센서노드 관리장치.Sensor node management apparatus, characterized in that the connection information of the data server is recorded in the service field.
  8. 제 2항에 있어서,The method of claim 2,
    상기 식별코드는 상기 센서노드의 제조사정보, 센서종류정보 및 고유코드를 포함하고,The identification code includes manufacturer information, sensor type information and unique code of the sensor node,
    상기 네이밍 서버에는 상기 각각의 센서노드에 대응하는 데이터 서버의 접속정보가 상기 식별코드에 포함되어 있는 제조사정보 및 센서종류정보를 기준으로 분류되어 저장되어 있는 것을 특징으로 하는 센서노드 관리장치.The naming server sensor node management apparatus, characterized in that the access information of the data server corresponding to each sensor node is classified and stored based on the manufacturer information and sensor type information included in the identification code.
  9. 제 1항 또는 제 2항에 있어서,The method according to claim 1 or 2,
    상기 센서노드 관리부는 상기 메타데이터에 포함된 정보들 중에서 상기 검색대상 센서노드와 통신하기 위한 응용 메시지의 포맷을 디코딩하여 상기 검색대상 센서노드로 전송하는 것을 특징으로 하는 센서노드 관리장치.And the sensor node manager decodes a format of an application message for communicating with the search target sensor node among information included in the metadata and transmits the format of the application message to the search target sensor node.
  10. 제 1항 또는 제 2항에 있어서,The method according to claim 1 or 2,
    상기 센서노드 관리부는 상기 메타데이터를 기초로 상기 검색대상 센서노드가 제공하는 기능명세를 파악하고, 사용자의 입력 또는 자동화된 스크립트에 따라 상기 검색대상 센서노드의 동작을 제어하기 위한 상기 제어 메시지를 구성하는 것을 특징으로 하는 센서노드 관리장치.The sensor node manager determines the functional specification provided by the search target sensor node based on the metadata, and configures the control message for controlling the operation of the search target sensor node according to a user input or an automated script. Sensor node management device, characterized in that.
  11. 센서 네트워크를 구성하는 복수의 센서노드의 메타데이터가 저장된 데이터 서버의 접속정보를 보유하고 있는 외부장치로부터 검색대상 센서노드의 식별코드에 대응하는 데이터 서버의 접속정보를 획득하는 주소획득단계;An address acquisition step of acquiring access information of a data server corresponding to an identification code of a sensor node to be searched from an external device having access information of a data server storing metadata of a plurality of sensor nodes constituting a sensor network;
    상기 획득한 데이터 서버의 접속정보에 대응하는 데이터 서버에 접속하여 상기 검색대상 센서노드의 식별코드에 대응하는 메타데이터를 획득하는 데이터 획득단계; 및A data acquiring step of accessing a data server corresponding to the acquired access information of the data server and acquiring metadata corresponding to the identification code of the sensor node to be searched; And
    상기 메타데이터에 포함된 정보를 기초로 상기 검색대상 센서노드에 접속하여 제어 메시지를 전송하는 센서노드 관리단계;를 포함하는 것을 특징으로 하는 센서노드 관리방법.And a sensor node management step of transmitting a control message by accessing the sensor node to be searched based on the information included in the metadata.
  12. 제 11항에 있어서,The method of claim 11,
    상기 외부장치는 상기 데이터 서버의 접속정보가 상기 각각의 센서노드에 부여된 고유의 식별코드에 대응되어 저장되어 있는 네이밍 서버인 것을 특징으로 하는 센서노드 관리방법.The external device is a sensor node management method, characterized in that the access information of the data server is stored in correspondence with a unique identification code assigned to each sensor node.
  13. 제 11항에 있어서,The method of claim 11,
    상기 외부장치는 상기 검색대상 센서노드인 것을 특징으로 하는 센서노드 관리방법.The external device is a sensor node management method, characterized in that the search target sensor node.
  14. 제 11항 또는 제 12항에 있어서,The method of claim 11 or 12,
    상기 센서노드 관리단계에서, 상기 검색대상 센서노드의 접속정보가 상기 검색대상 센서노드에 부여된 식별코드에 대응하여 저장되는 센서노드 접속정보 저장부로부터 획득한 접속정보를 기초로 상기 검색대상 센서노드에 접속하는 것을 특징으로 하는 센서노드 관리장치.In the sensor node management step, the search target sensor node based on the access information obtained from the sensor node access information storage unit in which the connection information of the search target sensor node is stored corresponding to the identification code assigned to the search target sensor node. Sensor node management apparatus characterized in that connected to.
  15. 제 11항 또는 제 12항에 있어서,The method of claim 11 or 12,
    상기 검색대상 센서노드에서 전송된 데이터로부터 상기 검색대상 센서노드에 부여된 고유의 식별코드를 추출하는 식별코드 추출단계를 더 포함하는 것을 특징으로 하는 센서노드 관리방법.And an identification code extracting step of extracting a unique identification code assigned to the searched sensor node from data transmitted from the searched sensor node.
  16. 제 12항에 있어서,The method of claim 12,
    상기 식별코드는 상기 센서노드의 제조사정보 및 상기 센서노드의 제품정보 중에서 적어도 하나를 포함하며,The identification code includes at least one of manufacturer information of the sensor node and product information of the sensor node,
    상기 네이밍 서버에는 상기 데이터 서버의 접속정보가 상기 센서노드의 제조사정보 및 상기 센서노드의 제품정보 중에서 상기 식별코드에 포함되어 있는 정보 중 적어도 하나를 분류기준으로 하여 저장되는 것을 특징으로 하는 센서노드 관리방법.The naming server stores the connection information of the data server based on at least one of information included in the identification code among the manufacturer information of the sensor node and the product information of the sensor node as a classification criteria. Way.
  17. 제 16항에 있어서,The method of claim 16,
    상기 주소획득단계에서, 상기 네이밍 서버로부터 정규표현식으로 표현된 상기 데이터 서버의 접속정보 및 서비스필드를 포함하는 레코드 형식의 응답을 획득하고,In the address acquisition step, obtain a response in the form of a record including a service field and the access information of the data server expressed in a regular expression from the naming server,
    상기 서비스필드에는 상기 데이터 서버의 접속정보가 기록되는 것을 특징으로 하는 센서노드 관리방법.And the access information of the data server is recorded in the service field.
  18. 제 12항에 있어서,The method of claim 12,
    상기 식별코드는 상기 센서노드의 제조사정보, 센서종류정보 및 고유코드를 포함하고,The identification code includes manufacturer information, sensor type information and unique code of the sensor node,
    상기 네이밍 서버에는 상기 각각의 센서노드에 대응하는 데이터 서버의 접속정보가 상기 식별코드에 포함되어 있는 제조사정보 및 센서종류정보를 기준으로 분류되어 저장되어 있는 것을 특징으로 하는 센서노드 관리방법.The naming server is a sensor node management method characterized in that the access information of the data server corresponding to each sensor node is classified and stored based on the manufacturer information and sensor type information included in the identification code.
  19. 제 11항 또는 제 12항에 있어서,The method of claim 11 or 12,
    상기 센서노드 관리단계에서, 상기 메타데이터에 포함된 정보들 중에서 상기 검색대상 센서노드와 통신하기 위한 응용 메시지의 포맷을 디코딩하여 상기 검색대상 센서노드로 전송하는 것을 특징으로 하는 센서노드 관리방법.In the sensor node management step, the sensor node management method, characterized in that for decoding the format of the application message for communicating with the search target sensor node from the information contained in the metadata to the search target sensor node.
  20. 제 11항 또는 제 12항에 있어서,The method of claim 11 or 12,
    상기 센서노드 관리단계에서, 상기 메타데이터를 기초로 상기 검색대상 센서노드가 제공하는 기능명세를 파악하고, 사용자의 입력 또는 자동화된 스크립트에 따라 상기 검색대상 센서노드의 동작을 제어하기 위한 상기 제어 메시지를 구성하는 것을 특징으로 하는 센서노드 관리방법.In the sensor node management step, the control message for grasping the functional specification provided by the search target sensor node based on the metadata and controlling the operation of the search target sensor node according to a user input or an automated script. Sensor node management method comprising the configuration.
  21. 제 11항 또는 제 12항에 기재된 센서노드 관리방법을 컴퓨터에서 실행시키기 위한 프로그램을 기록한 컴퓨터로 읽을 수 있는 기록매체.A computer-readable recording medium having recorded thereon a program for executing the sensor node management method according to claim 11 or 12.
PCT/KR2009/006994 2008-11-25 2009-11-25 Device and method for sensor node management based on metadata WO2010062114A2 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR20080117658 2008-11-25
KR10-2008-0117658 2008-11-25

Publications (2)

Publication Number Publication Date
WO2010062114A2 true WO2010062114A2 (en) 2010-06-03
WO2010062114A3 WO2010062114A3 (en) 2010-08-12

Family

ID=42226257

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2009/006994 WO2010062114A2 (en) 2008-11-25 2009-11-25 Device and method for sensor node management based on metadata

Country Status (2)

Country Link
KR (1) KR101109549B1 (en)
WO (1) WO2010062114A2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200105706A (en) * 2018-01-17 2020-09-08 가부시키가이샤 사이게임스 Systems, programs, methods and servers for conducting communication

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102006219B1 (en) * 2017-11-28 2019-08-02 한국전자통신연구원 SYSTEM AND METHOD FOR AUTO CONFIGURATION OF IoT NODES
KR102040905B1 (en) * 2018-08-20 2019-11-05 (주)지티에이컴 METHOD FOR TRANSFERING DATA BY USING Low-Power Wide-Area Network
KR102580364B1 (en) * 2020-11-24 2023-09-20 한국전자통신연구원 Apparatus and Method for Fuzzing Preprocessing for Automating Smart Network Fuzzing

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060089501A (en) * 2005-02-04 2006-08-09 삼성전자주식회사 Apparatus and method for routing path setting in sensor network
KR20070057597A (en) * 2005-12-01 2007-06-07 한국정보사회진흥원 System and method for providing location-based service using geographical code in usn
KR100786575B1 (en) * 2006-07-21 2007-12-18 경희대학교 산학협력단 Low-powered sensor network management method
KR100789919B1 (en) * 2006-08-16 2008-01-02 한국전자통신연구원 Apparatus for providing usn directory service based on herterogeneous sensor networks and its method
KR20080001585A (en) * 2006-06-29 2008-01-03 한국전자통신연구원 Data structure for managing sensor network using id of sensor node and method using the same

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007041660A (en) * 2005-08-01 2007-02-15 Nec Corp Sensor network, sensor node and its program, and sensor information retrieval method
JP5074216B2 (en) * 2008-01-21 2012-11-14 株式会社日立製作所 Sensor network server and sensor network system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060089501A (en) * 2005-02-04 2006-08-09 삼성전자주식회사 Apparatus and method for routing path setting in sensor network
KR20070057597A (en) * 2005-12-01 2007-06-07 한국정보사회진흥원 System and method for providing location-based service using geographical code in usn
KR20080001585A (en) * 2006-06-29 2008-01-03 한국전자통신연구원 Data structure for managing sensor network using id of sensor node and method using the same
KR100786575B1 (en) * 2006-07-21 2007-12-18 경희대학교 산학협력단 Low-powered sensor network management method
KR100789919B1 (en) * 2006-08-16 2008-01-02 한국전자통신연구원 Apparatus for providing usn directory service based on herterogeneous sensor networks and its method

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200105706A (en) * 2018-01-17 2020-09-08 가부시키가이샤 사이게임스 Systems, programs, methods and servers for conducting communication
KR102374887B1 (en) 2018-01-17 2022-03-16 가부시키가이샤 사이게임스 Systems, programs, methods and servers for conducting communications

Also Published As

Publication number Publication date
KR20100059728A (en) 2010-06-04
KR101109549B1 (en) 2012-02-09
WO2010062114A3 (en) 2010-08-12

Similar Documents

Publication Publication Date Title
WO2010062048A4 (en) Method and apparatus for managing state information of remote user interface
WO2010104267A2 (en) System and method for managing sensor node in rfid/usn infrastructure and gateway system used therefor
WO2011021886A2 (en) Device capable of notifying operation state change thereof through network and communication method of the device
WO2016085180A1 (en) Method of managing cookie information for target advertisement and application for managing cookie information
WO2012026777A2 (en) Method and apparatus for establishing communication
WO2020147396A1 (en) Method for dynamically configuring service domain name, device, apparatus, and storage medium
US20060195613A1 (en) Protocol conversion apparatus, communication apparatus, method and program
WO2010062114A2 (en) Device and method for sensor node management based on metadata
WO2017074034A1 (en) Method and apparatus for interworking between heterogeneous systems
WO2020186773A1 (en) Call request monitoring method, device, apparatus, and storage medium
WO2019078489A1 (en) Method and server device for providing internet of things platform service
WO2021107256A1 (en) Method for providing interface for interoperation between different types of iot platform devices and system for providing interface for interoperation between different types of iot platform devices
WO2010123168A1 (en) Database management method and system
WO2012060669A1 (en) Method for controlling remote device through sms and device therefor
CN103988528B (en) The control method of communicator and the communicator
WO2015199271A1 (en) Method and system for sharing files over p2p
WO2012047074A2 (en) Methods and apparatus for obtaining a service
WO2017048058A1 (en) Method and apparatus for transmitting and receiving data in communication system
WO2014092505A1 (en) Method and device for providing dns service
CN103959827B (en) Communicator and its control method
EP2666256A2 (en) Method and apparatus for phone communication using home network
WO2021107255A1 (en) Management system method and device for identification system interoperability between heterogeneous iot platforms
JP5091217B2 (en) Home device information collecting apparatus and home device information collecting method
WO2012134013A1 (en) System for mobile content advertising and method for mobile content advertising
WO2012068835A1 (en) Method and apparatus for registering in constrained application protocol (coap) network

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09829321

Country of ref document: EP

Kind code of ref document: A2

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09829321

Country of ref document: EP

Kind code of ref document: A2