KR101966548B1 - Sensor meta data generating system for multi heterogeneous sensor network platform - Google Patents

Abstract

The present invention relates to a sensor metadata generation system for a plurality of heterogenous sensor network platforms. According to the present invention, the sensor metadata generation system comprises: a sensor/middleware data storage unit storing sensor-related data of a plurality of sensor networks and information about sensor middleware for collecting sensing data of each sensor network; and a sensor metadata generation tool generating sensor metadata for a sensor content service based on the data of the sensor/middleware data storage unit, and storing the sensor metadata in a sensor network platform. The sensor metadata generation tool comprises: a sensor information management unit including a sensor information generator for generating sensor information; a middleware management unit including a middleware information generator to generate information about sensor middleware and a middleware access management unit to determine access permission to the sensor middleware; a sensor service information issuing unit including a service information generator for generating and registering service information to a remote service registration server; and a viewer forming and displaying a metadata generation and execution window for sensor and sensor middleware management functions and sensor service registration. Accordingly, sensor-related content of each of a plurality of sensor networks is easily generated by using the sensor metadata generation tool, thereby simply constructing a sensor network platform for providing a sensor information content service of each sensor network.

Description

TECHNICAL FIELD [0001] The present invention relates to a sensor metadata generation system for a plurality of heterogeneous sensor network platforms,

The present invention relates to a sensor web service system, and more particularly, to a sensor metadata generation system for forming service data of a sensor network platform constituting a sensor web service.

The sensor network collects sensing data such as temperature, humidity, pressure, vibration, and motion from various sensor nodes constituting the sensor network, analyzes and processes the collected sensing data, and provides the information service to the user through the application program ≪ / RTI > The sensor network is a core technology of ubiquitous computing and corresponds to an underlying technology that is indispensable for context aware computing technology aimed at providing variable services by recognizing changes in the environment surrounding the user .

A large number of sensor networks having different purposes and functions are installed in a wide area, and sensor nodes constituting each sensor network collect information of the surrounding environment in real time while being attached to objects or placed or moved in places.

The sensor network platform is connected to the sensor middleware that collects status data such as temperature, humidity, wind velocity, airflow, and illumination from the sensor network. The sensor network platform monitors the environment in which the sensor network is constructed and controls the sensor network using the sensing data collected by the sensor middleware. In addition, the sensing data is processed to generate event and environment situation information desired by the application (client computer), and the information service is provided by the application.

1 is a conventional sensor web service system model. The sensor web service system includes a sensor network 120, a sensor network platform 140, a service registration server 150, and a client 160.

The sensor network 120 collects sensing data sent from each of the external sensor nodes and transmits the collected sensing data to the sensor network platform 140. The sensor network platform 140 generates service content and registers its service information in the service registration server 150. [ The service registration server 150 stores and manages service information of various sensor web network platforms and provides a search service to the client 160.

The client 160 requests sensor node information to the sensor network platform 140, and the sensor network platform 140 performs a role of visualizing the information.

In order to create the above-described sensor network platform, a sensor network platform for forming sensor-related contents including sensor information and sensing data using sensor data sensed for each sensor network and providing sensor-related contents must be separately constructed .

The present invention has been proposed in order to solve the above problems, and it is an object of the present invention to provide a sensor information content service for each sensor network by easily generating sensor-related content data for each of a plurality of sensor networks using a sensor meta data generation tool And to provide a sensor content generation system for a plurality of heterogeneous sensor network platforms that can easily construct a sensor network platform.

In addition, the present invention can facilitate editing of sensor information of a sensor network using a sensor meta data generation tool, easily add middleware information for collecting sensor information and sensing data, And to provide a sensor metadata generation tool capable of updating the sensor metadata.

According to an aspect of the present invention, there is provided a sensor metadata generation system for a plurality of heterogeneous sensor network platforms for providing a sensor content service to an app client, A sensor / middleware data storage unit for storing information on sensor middleware for collecting sensing data of the sensor / middleware data storage unit; and sensor metadata for sensor content service based on the data of the sensor / A sensor meta data generation tool; The sensor metadata generation tool includes a sensor information management unit having a sensor information generator for generating sensor information (sensor name, sensor ID, sensing type, etc.), a middleware information generator for generating information about the sensor middleware, And a service information generator for generating service information (search keyword, service name, web address, and the like) and registering the service information in a remote service registration server, the middleware management part having a middleware access right management part for allowing access to the sensor service information And a viewer for forming a metadata generation execution window for performing sensor service registration and displaying the metadata on the remote application client computer.

The sensor metadata generation tool may further include an overall map information management unit and a map image file processor for converting the entire map image into a plurality of map images of different sizes, An overall map information generator for generating overall map information, and an image load for generating and loading an entire map in the form of a mini-map or a divided map through the map image file processor.

The sensor metadata generation tool may include a position information generator for generating map position information of the sensor, a position information generator for generating a map image through a mini-map and a division map through the map image file processor, It is preferable to further include a management unit.

The sensor information management unit may further include a sensor mark generator for marking a position of a sensor to be sensed on a map image.

In the metadata creation execution window, a sensor management button is provided. When the sensor management button is selected, the viewer forms and displays a sensor management window for inputting information such as a sensor name, a sensor ID, a sensor type, .

In the metadata creation execution window, a middleware management button may be provided. When the middleware management button is selected, the viewer may include a middleware ID for inputting middleware IDs, adding or deleting middleware IDs, middleware management for enabling or disabling middleware access rights It is preferable to form and display a window.

In the metadata creation execution window, a sensor service registration button is provided. When the sensor service registration button is selected, the viewer registers a service registration for entering service related information such as a service name and a service address in the service registration server It is preferable to form and display a window.

Here, the sensor network platform may include a service interface unit for communicating with the sensor metadata generation tool and the application client; A content service unit for managing sensor middleware configuration and managing sensor information; A sensor information unit, a provider service unit for searching for a sensor requested to be searched and supplying sensing data; A service control unit for controlling the content service unit or the provider service unit; A sensor database for storing sensor information and sensor middleware information as sensor metadata generated by the sensor metadata generation tool; And a service status viewer for displaying an operation status of the sensor content service.

Here, the content service unit may include a middleware configuration management unit and a sensor information management unit; Wherein the provider service unit has a sensor search unit, a sensor information supply unit, and a sensor sense data supply unit; The service control unit preferably includes a provider service control unit and a content service control unit, respectively, for controlling the start or end of the operation of the provider service or the content service.

The sensor database preferably stores map data, sensor-related map position data installed in a predetermined area, and map-related service contents generated by the sensor metadata generating tool.

The content service unit may further include a map data management unit that manages detailed data of the map and a location information management unit that manages data related to the sensor location. The detailed data of the map includes a building, a floor, a room, a latitude, and a longitude.

Here, the service status viewer creates a sensor network platform execution window for providing a sensor content service, and the sensor network execution window includes a sensor provider service start button, a sensor content service start button, .

Here, the sensor network platform preferably performs RESTful API communication with the sensor metadata generation tool and the sensor middleware.

Here, sensor related data and sensor middleware information in a plurality of sensor networks of the sensor / middleware data storage unit are previously stored in a system manager computer, and the sensor metadata generating tool is preferably a software program implemented in the system manager computer Do.

With this configuration, it is possible to easily generate sensor-related content data for each of a plurality of sensor networks using the sensor meta data generation tool, thereby providing a plurality of sensor network platforms A metadata generation system for heterogeneous sensor network platforms is provided.

1 is a block diagram of a conventional sensor web system,
FIG. 2 is a connection diagram of a sensor meta data generation tool and a sensor network platform according to the present invention;
FIG. 3 is a diagram showing the configuration of the sensor metadata generation tool of FIG. 2;
FIG. 4 is a block diagram showing the configuration of the sensor network platform of FIG. 3;
FIG. 5 is an operation flowchart of each component of the sensor metadata generation tool of FIG. 3,
FIG. 6 shows an execution window for the user interface of the sensor network platform of FIG. 4,
7A to 7D show an execution window for a user interface of the sensor metadata generation tool of FIG. 3,
8 is a flow chart of sensing data collection in the sensor web service system.

BRIEF DESCRIPTION OF THE DRAWINGS The advantages and features of the present invention, and how to accomplish it, will be described with reference to the embodiments described in detail below with reference to the accompanying drawings. However, the present invention is not limited to the embodiments described herein but may be embodied in other forms. The embodiments are provided so that those skilled in the art can easily carry out the technical idea of the present invention to those skilled in the art.

In the drawings, embodiments of the present invention are not limited to the specific forms shown and are exaggerated for clarity. In addition, like reference numerals designate like elements throughout the specification. The expression "and / or" is used herein to mean including at least one of the elements listed before and after. Also, singular forms include plural forms unless the context clearly dictates otherwise. Also, components, steps, and operations that are referred to in the specification as " comprises "or" comprising " refer to the presence or addition of one or more other components, steps, operations, and devices.

The sensor web service manages sensor-related information in the sensor network and provides sensor-related information to the app client. For sensor web service, sensor network platform that provides sensor information according to app client request, sensor metadata generation tool to generate sensor situation data to be served, sensor middleware to collect sensor data in sensor network, And a sensor / middleware data storage unit in which middleware information is stored.

The sensor metadata generation tool has a function of generating sensor-related service content data and a function of registering sensor content service information. The sensor network platform performs a service content storage function and a function of providing sensor-related contents to an app client.

In the present embodiment, it is assumed that the system administrator computer has both sensor meta data and middleware information data. The sensor metadata generation tool of the system administrator computer provides information suitable for many kinds of sensor network platforms. The sensor status metadata (hereinafter referred to as " sensor metadata ") includes sensor data such as temperature, humidity, wind speed, airflow, and illumination.

It is therefore a feature of the present invention to provide a sensor metadata generation tool that easily generates sensor related service content for a plurality of heterogeneous sensor network platforms.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

2 is a configuration diagram of a sensor web service system based on a sensor metadata generation tool according to the present invention. 2, the sensor web service system includes a sensor network 20, a sensor metadata generation tool 30, a sensor network platform 40, a service registration server 50, and an application client 60 . Here, the app client 60 means all client computers that use the sensor data supply service.

In the present embodiment, the sensor metadata generation tool 30 is implemented as a software program executed on a system administrator computer.

The sensor network platform 40 uses the RESTful API to interface with the sensor middleware 23, the sensor metadata generation tool 30, and the application client 60.

In the present invention, a socket is used for communication between the sensor middleware 23 and the sensor network 20. The sensor network 20 transmits the sensed data to the sensor middleware 23 through a socket. Typically, a socket consists of a node address and a port number that identifies the service.

The sensor network platform 40 provides stable real-time sensing data support to the app client 60.

The sensor middleware 23 transmits the received sensing data to the sensor network platform 40 and stores the sensed data in the sensor database to be described later through a RESTful API (Application Programming Interface) in the sensor network platform 40. The RESTful API refers to a Web service that uses a REST (Representational State Transfer) structure. REST is a structural format used to develop a Web service. It is created, read, ), And a Web service API used to manage resources that can be deleted.

The sensor metadata generation tool 30 manages sensor information, sensor middleware information, and service information through the RESTful API of the sensor network platform 40.

In the present embodiment, the sensor metadata generation tool 30 manages sensor information, middleware information, and service information. To do this, sensor middleware connected between wireless sensor network and sensor network platform was used.

The sensor metadata generation tool 30 as described above is a COST (Content Support Tool). This is because the functions of the app client, the service registration server, and the sensor network are unchanged and the service content registration role and the service registration role in the sensor network platform are compared with the configuration of the conventional sensor web system. ). With this structure, COST separates content generation from SOA (Service Oriented Architecture) based sensor web, and it is easy to collectively manage sensor network platform and can produce professional contents. In addition, since the burden of content creation is reduced in the service provider, the service provider can concentrate on providing the service, thereby providing an environment for providing the service more stably.

The sensor network platform 40 is connected to a plurality of the field sensor middleware 23 and the sensor network 20. We also used three RESTful APIs in the sensor network platform to support communication between the other modules.

The sensor network platform 40 functions as a sensor data storage / processing / provisioning function in addition to a user interface of a system administrator computer. Each sensor middleware 23 is installed in the field and collects situation (sensor) data from each sensor network, / Perform error data processing.

The sensor network platform 40 provides stable real-time sensing data support to the app client 60, and the app client 60 shows the data results to the user.

On the other hand, the collection of the sensing data in the sensor network 23 is performed as follows. The sensor middleware 23 transmits sensing data received from the sensor network 20 to the sensor network platform 40 and stores the sensing data.

The manager computer (app client) requests the sensor network platform 40 for sensing data. The sensor middleware 23 receives the sensing data from the sensor nodes operating in the sensor network 20. The sensor middleware 23 transmits the sensing data collected in the sensor network 20 to the sensor network platform 40.

3 is a configuration block diagram of the sensor metadata generation tool 30 according to the present invention. The sensor meta data generation tool 30 generates sensor information, and performs access management and service information registration to the middleware.

The sensor metadata generation tool 30 generates information of the sensor nodes through the sensor web contents API and stores them in the sensor database 47 of the sensor network platform 40 to be described later. The sensor meta data generation tool 30 generates configuration information of the sensor middleware 23 and registers the configuration information in the sensor network platform 40.

The sensor metadata generation tool 30 registers service information of the sensor network platform 40 in the service registration server 50 as middleware access management and service information issue support function.

The sensor metadata generation tool 30 registers the service information of the sensor network platform 40 in the service registration server 50 so that the sensor list information provided by the sensor network platform 40 is transmitted to the app client 60 Can be displayed and provided.

3, the sensor metadata generation tool 30 includes an overall map information management unit 31, a map image file processor 32, a middleware management unit 33, a sensor information management unit 34, a position information management unit 35 A sensor service information issuing unit 36, and a viewer 37.

The overall map information management unit 31 includes an image load 311 and an overall map information generator 312 for generating overall map information.

The image load 311 of the overall map information management unit 31 generates and loads an entire map through a map image file processor 32 that generates a plurality of map images of different sizes. For example, the image load 311 loads the entire image of the map on which the sensor is located. Then, the overall map information generator 312 generates and stores information (map size, etc.) of the entire map.

The middleware information generator 331 of the middleware management unit 33 generates middleware information (ID and IP address) and stores the generated middleware information in the sensor database 47 of the sensor network platform 40.

The middleware access right management unit 332 of the middleware management unit 33 manages the access right to the sensor middleware 23 by the sensor network platform 40. The meaning of the middleware access right means the access right to the sensor middleware.

The sensor information management unit 34 includes a sensor information generator 341 and a sensor mark generator 342.

The sensor information generator 341 of the sensor information management unit 34 generates sensor information (sensor name, sensor ID, sensing type, etc.) and stores the generated sensor information in the sensor database 47 of the sensor network platform 40 .

The sensor mark generator 342 of the sensor information management unit 34 functions to mark the position of the sensor to be sensed on a map.

The location information management unit 35 includes an image load 351 and a location information generator 352. [ The location information management section 35 provides a map visualization and provides a control set (control screen) for adjusting the map view to the user.

The image load 351 of the position information management unit 35 generates and stores a map image in the form of a mini-map or a divided map through the map image file processor 32. The position information generator 352 generates position information of the sensor do.

The sensor service information issuer 36 generates service information (a search keyword, a service name, an address, and the like) through the service information generator 361 and stores the service information in an XML temporary file 362, 50).

In the past, the sensor network platform directly registered the service in the sensor service registration server 50, but in the present invention, the sensor metadata generation tool 30 registers the service in the sensor service registration server 50.

The viewer 37 constitutes a sensor management window 70 of a sensor metadata generation tool, a middleware management window 80 of a sensor metadata generation tool, and a service registration management window 90 of a sensor metadata generation tool, which will be described later.

4 is a configuration block diagram of the sensor network platform 40 of FIG.

4, the sensor network platform 40 includes a service interface unit 41, a content service unit 42, a provider service unit 43, a service control unit 44, a service status viewer 45, An XML configuration unit 46, and a sensor database 47.

First, the sensor database 47 of the sensor network platform 40 stores sensor-related information such as a sensor name, a sensor ID, and sensing data. Map data and service contents generated by the sensor metadata generation tool 30 are stored in the sensor database 47. In addition, the sensor database 47 stores position information of sensors installed in a predetermined area (building, etc.). To this end, the sensor database 47 further includes map data to provide a map data service indicating the location of the sensor.

The service interface unit 41 of the sensor network platform 40 includes a content service interface 411 for communicating with the sensor meta data generation tool 30 and a provider service interface 412 for communicating with the app client 60 ).

The content service unit 42 of the sensor network platform 40 includes a middleware information management unit 421, a sensor information management unit 422, a map data management unit 423, and a location information management unit 424.

The middleware configuration management unit 421 of the content service unit 42 stores and manages the middleware ID, the IP address, and the service access right information.

The sensor information management unit 422 of the content service unit 42 generates and manages sensor information such as a sensor node name, a sensor ID, and a sensing type (sensing type).

The map data management unit 423 of the content service unit 42 manages a map image stored in the map database.

The location information management unit 424 of the content service unit 42 manages the data of the sensor location and the detailed data of the map. The detailed data of the map may include information such as area, building, floor, room, latitude, and longitude.

The provider service unit 43 of the sensor network platform 40 includes a sensor search unit 431, a sensor information supply unit 432, a sensed data supply unit 433, and a position information supply unit 434 of the sensor.

The sensor search unit 431 of the provider service unit 43 searches the sensor database 47 for a sensor requested to be searched from the outside and returns a sensor ID list for a specific search keyword.

The sensor information supply unit 432 of the provider service unit 43 provides related information such as the sensor node name and the type of detection for the sensor ID.

The detection data supply unit 433 of the provider service unit 43 provides the detection sensor ID and the real-time detection data of the detection sensor.

The location information supply unit 434 of the provider service unit 43 provides location information of the sensor.

The service control unit 44 of the sensor network platform 40 determines the start and end of the operation of the sensor network platform 40. [ The service control unit 44 includes a provider service control unit 441 and a content service control unit 442.

The service status viewer 45 of the sensor network platform 40 functions to manage the operation status of the data collection service from the sensor.

The service status viewer 45 shows the operation status of the service to the system administrator.

The XML component 46 of the sensor network platform 40 provides a Window Communication Foundation (WCF) service state that provides data transmission in a window.

The XML configuration unit 46 arranges the operating environment of the WCF (Window Communication Foundation) service. WCF is a Web services-based communication framework, also called a messaging framework. A client is called a service (server) that provides a certain function, and a caller that calls to receive a function is called a client. A client and a service send a functional request to a service (server) while exchanging XML / JSON messages And the service (server) returns the result.

At the heart of WCF components are Address, Binding, and Contact. The address is a URI indicating the location of the service on the Internet. Binding is a collection of various elements to consider when invoking a WCF service over the network. A contract is an interface that describes the functions provided by a WCF service. The core of WCF addresses, bindings, and contracts are collectively called the endpoint of the service. The client must invoke the service only through the endpoint, which can be thought of as an access point to the service.

According to the present embodiment, the XML configuration unit 46 constitutes an execution window 50 of the sensor network platform 40 to be described later.

The operation of each functional block when the sensor metadata generation tool 30 for generating the sensor information and the middleware information for constituting the execution window of the sensor network platform 40 is described as follows.

5, when the user operates the sensor metadata generating tool 30, the sensor information generator 341 manages the sensor information and transmits an operation message or sensor information data to the sensor network platform 40 do. In response, the sensor network platform 40 returns a fact or a false to inform the user whether the operation is completed.

When the user operates the sensor metadata generation tool 30, the middleware information generator 331 can manage the middleware information and transmit the operation message or the middleware information data to the sensor network platform 40. [ In response, the sensor network platform 40 returns a fact or a false to inform the user whether the operation is completed.

When the user operates the sensor meta data generation tool 30, the service information generator 361 can manage the sensor service information and transmit the service information data to the sensor service registration server 50. [ The sensor service registration server 50 returns a fact or a false to inform the user whether the operation is completed.

The operation sequence of the sensor metadata generation tool 30 is as follows. When the user edits sensor information or middleware information in the sensor meta data generation tool, the sensor information generator 341 or the middleware information generator 331 sends a message to the sensor network platform 40 to change sensor information or middleware information do. At this time, the sensor network platform 40 stores the changed sensor information or middleware information in the sensor database 47. The sensor network platform 40 returns true or false to the sensor information generator 341 or the middleware information generator 331.

When the user edits the service information in the sensor meta data generation tool 30, the service information generator 361 sends a message to the sensor network platform 40 to change the service information.

The sensor network platform 40 stores the changed service information in the database 47 and then returns true or false to the service information generator 361. [

6 is an execution window 48 for the user interface of the sensor network platform 40. [ 6, the user interface execution window 48 of the sensor network platform 40 includes a service status viewer area (A) 481 showing a service status, a service service control block including a provider service control block and a content service control block A control area (B) 482, and a service load viewer area (C) 483 indicating the start state of the service are displayed.

It provides the role of controlling start and end of service in the sensor network platform interface window of system administrator. The service status viewer area (A) 481 shows the status of the service. The control area (B) 482 plays a role of controlling the service. The service load viewer area (C) 483 shows service control record information.

Accordingly, the system administrator can confirm the start status of the content service or the provider service through the service status viewer area (A) 481, and transmit the content service and the provider service through the control area (B) 482 You can start or end.

FIG. 7A is an execution window 68 for the user interface of the sensor metadata generation tool 30. FIG. When the user executes the sensor meta data generation tool, the main page of the user interface execution window 68 shows the current time and the number of sensors.

The sensor metadata generation tool 30 functions to generate and manage sensor information, middleware information, generation and management, and service information generation and management functions. 6, the user interface execution window 68 of the sensor meta data generation tool 30 displays current time information, a 'sensor management' button 681, a 'middleware management' button 682, Sensor service registration 'button 683, and a' close 'button are provided.

7B is a sensor management window 70 displayed when the 'sensor management' button 681 of FIG. 7A is clicked.

In the sensor list area (A) 71 located on the left side of the sensor management window 70, a sensor list is displayed and a function of searching the sensor list is performed.

The sensor information area (B) 72 of the sensor management window 70 functions to generate sensor information. The sensor information includes the sensor name, ID, description, and sensor type. The system administrator can edit sensor information.

The category zone (C) 73 of the sensor management window 70 functions to generate sensor category information by classifying the sensors into categories. At the bottom of the category list block of the category zone (C) 73, there are provided an 'add' button for adding to the category and a 'delete' button for deleting from the category as buttons for editing.

At the bottom of the category editing button, there are provided an 'add' button for adding a sensor, an 'update' button for updating the sensor, a 'delete' button for deleting the sensor, and a 'cancel' button for closing the sensor management page.

7C is a middleware management window 80 displayed when the 'sensor management' button 681 of FIG. 7A is clicked. When the system manager clicks the 'middleware management' button 682 in the interface window 68 of the sensor metadata generation tool 30, the middleware management window is displayed. The middleware management window displays a list of middleware information.

Area A 81 of the middleware management window 80 functions as a middleware list. The system administrator can select middleware from the middleware list.

The B zone 82 of the middleware management window 80 functions to add and delete middleware information. At the bottom of the list, there is an input block for the user to input the middleware ID, an 'add' button for adding middleware, and a 'delete' button for deleting middleware.

The C zone 83 of the middleware management window 80 functions to designate a server access right of the middleware.

The C zone 83 is provided with an 'enable' button for setting the middleware access right to the enable state and a 'disable' button for setting the middleware access right to the disable state.

7D is a service information management window 90 displayed when the 'sensor service registration' button 683 of FIG. 7A is clicked. The service information management window shows the result of the sensor service registration part.

When the 'sensor service registration' button in the interface window 68 of the sensor metadata generation tool 30 is clicked, a sensor service registration information management window is displayed. The system administrator can input information into a service name, whether or not a Web Services Description Language (WSDL) is provided, a service description (Service Explain), a service address (Service Uri), and a search keyword block. Then, after inputting each information, the service information can be stored by clicking the 'Save Service Information' button.

Here, 'service address' is the access address of the sensor network platform. The 'search keyword' is a keyword for searching the sensor network platform.

According to the present invention, the sensor metadata generation tool 30 supports a sensor network platform having a RESTful API for a wireless sensor network. Through the sensor metadata generation tool, the system administrator can easily manage sensor information, middleware information, and service information.

The sensor metadata generation tool supporting the sensor network platform is designed to collect sensing data from the wireless sensor network through the sensor middleware. The sensor network platform will be extended by the implementation of a complete IoT system. Accordingly, the user can control the smart device based on the sensing data supported by the sensor network platform.

The features of the present invention will be briefly described as follows.

In the present invention, it is assumed that the middleware is installed in a site (for example, a district, a building, etc.) where a sensor network is installed. The system administrator computer has the sensor network information and the middleware information, and generates the middleware information and the sensor information by using the sensor metadata generating tool and transmits it to the sensor network platform.

It is a sensor metadata generation tool that system administrator has relevant situation meta information and middleware information and provides information suitable for various platforms. Situation metadata refers to situation data such as temperature, humidity, wind speed, air volume, and illumination.

The sensor metadata generation tool according to the present invention can easily generate and manage sensor contents provided by the sensor network platform.

Accordingly, the sensor metadata generation tool of the present invention can easily generate a plurality of heterogeneous sensor network platforms by applying different sensor data to each sensor network.

In addition, by separately generating the sensor-related contents by the sensor meta data generation tool, it is possible to manage the sensor network platform collectively and to produce professional contents. In addition, since the burden of content creation is reduced in the service provider, the service provider can concentrate on providing the service, thereby providing an environment for providing the service more stably.

According to the present invention, it is possible to provide an indoor sensor web design and implementation using a sensor network platform that provides various real-time context data managed through a sensor metadata generation tool.

10: Manager computer 20: Sensor network
30: Sensor Metadata Generation Tool 33: Middleware Management Unit
34: sensor information management unit 36: sensor service information issuance unit
40: sensor network platform 41: service interface unit
42: Content service part 43: Provider service part
44: service control unit 47: sensor database
50: service registration server

Claims (15)

A sensor metadata generation system for a plurality of heterogeneous sensor network platforms for providing sensor content services to an app client,
A sensor / middleware data storage unit for storing information on sensor middleware that collects sensor-related data and sensing data of each sensor network in a plurality of sensor networks, and a sensor / middleware data storage unit for storing sensor- A sensor metadata generation tool for generating sensor metadata and providing the generated sensor metadata to the sensor network platform;
Wherein the sensor metadata generation tool comprises:
A sensor information management unit having a sensor information generator for generating sensor information (sensor name, sensor ID, sensing type)
A middleware management unit having a middleware information creator for generating information on the sensor middleware, a middleware access right management unit for allowing access to the sensor middleware,
A service information generator for generating service information (search keyword, service name, web address) and registering the service information in a remote service registration server;
A sensor metadata generation system for a plurality of heterogeneous sensor network platforms, including a viewer for forming a metadata generation execution window for performing sensor management function, sensor middleware management function, and sensor service registration and displaying the generated metadata on a remote application client computer . The method according to claim 1,
The sensor metadata generation tool may further include an overall map information management unit and a map image file processor for converting the entire map image into a plurality of map images of different sizes,
Wherein the overall map information management unit comprises an overall map information generator for generating overall map information in which the sensors are located, and an image load for generating and loading the entire map in a mini-map or a divided map form through the map image file processor Sensor Metadata Generation System for Heterogeneous Sensor Network Platforms. 3. The method of claim 2,
The sensor metadata generation tool includes a position information generator for generating map position information of the sensor, a position information manager having an image load for generating and loading a map image in the form of a mini-map and a division map through the map image file processor Further comprising: a sensor metadata generation system for a plurality of heterogeneous sensor network platforms. The method according to claim 1,
Wherein the sensor information management unit further comprises a sensor mark generator for marking a position of a sensor to be sensed on a map image. The method according to claim 1,
A sensor management button is provided in the metadata generation execution window;
When the sensor management button is selected, the viewer forms and displays a sensor management window for inputting information including a sensor name, a sensor ID, and a sensor type. The method according to claim 1,
Wherein the metadata generation execution window is provided with a middleware management button;
Wherein when the middleware management button is selected, the viewer forms and displays a middleware management window for enabling or disabling middleware IDs, adding or deleting middleware IDs, and enabling or disabling middleware access rights. Metadata generation system. The method according to claim 1,
Wherein the metadata generation execution window is provided with a sensor service registration button;
Wherein when the sensor service registration button is selected, the viewer forms and displays a service registration window for inputting service related information including a service name and a service address to the service registration server, Metadata generation system. The method according to claim 1,
The sensor network platform includes:
A service interface unit for communicating with the sensor metadata generation tool and the application client;
A content service unit for managing sensor middleware configuration and managing sensor information;
A sensor information unit, a provider service unit for searching for a sensor requested to be searched and supplying sensing data;
A service control unit for controlling the content service unit or the provider service unit;
A sensor database storing sensor information and sensor middleware information as sensor metadata generated by the sensor metadata generation tool;
And a service status viewer for indicating an operational state of the sensor content service. 9. The method of claim 8,
Wherein the content service unit has a middleware configuration management unit and a sensor information management unit;
Wherein the provider service unit has a sensor search unit, a sensor information supply unit, and a sensed data supply unit for supplying sensed data sensed by the sensor;
Wherein the service control unit comprises a provider service control unit and a content service control unit for controlling the start or end of the operation of the provider service or the content service, respectively, and a content service control unit. 10. The method of claim 9,
Wherein the sensor database stores map data, sensor-related map position data installed in a predetermined area, and service contents generated by the metadata generation tool. 11. The method of claim 10,
Wherein the content service unit further comprises a map data management unit for managing detailed data of the map and a location information management unit for managing data on the sensor location. 12. The method of claim 11,
Wherein the detailed data of the map includes information such as a building, a floor, a room, latitude, and longitude. 9. The method of claim 8,
The service status viewer generates an execution window of a sensor network platform for providing a sensor content service,
Wherein the sensor network platform execution window displays a sensor provider service start button, a sensor content service start button, and a service providing status are displayed in the sensor network platform execution window. 9. The method of claim 8,
Wherein the sensor network platform performs RESTful API communication with the sensor metadata generation tool and the sensor middleware. The method according to claim 1,
Sensor-related data and sensor middleware information in a plurality of sensor networks of the sensor / middleware data storage unit are previously stored in a system manager computer,
Wherein the sensor metadata generation tool is a software program implemented in the system administrator computer.

Images