KR20100088432A - Semantic service system and method thereof - Google Patents

Abstract

PURPOSE: A system for searching a semantic service is provided to implement various services by sharing service concepts between a user and a developer after establishing sensor ontology and service ontology. CONSTITUTION: A USN(Ubiquitous Sensor Network) ontology module(11) includes actual data depending on the metadata of both a sensor ontology(11A) and a service ontology(11B). A semantic DBMS(DataBase Management System)(13) stores the metadata of both the sensor ontology and the service ontology. A semantic DB utility module(15) transfers the metadata to the semantic DBMS. The semantic DB utility model transfers the received query to the semantic DBMS.

Description

Semantic Service Search System and Method {SEMANTIC SERVICE SYSTEM AND METHOD THEREOF}

The present invention relates to a semantic service retrieval system and method for a ubiquitous sensor network (USN) service.

USN attaches electronic tags to all things to recognize things and the environment and to build and utilize real-time information through the network. USN service refers to a service using various sensors. That is, it is an application program for operating a specific device by inputting and analyzing values output from various sensors.

However, since there is no general sensor interface for USNs, it is not easy for service providers to write services related to numerous sensors. Also, it is not easy for a user to search for a desired service among numerous USN services.

Accordingly, an aspect of the present invention is to provide an apparatus and method for easily writing a service related to a number of sensors that are the basis of a USN.

In addition, the present invention provides an apparatus and method for allowing a user to easily search for a desired service among USN services.

The first invention is a semantic service search server for the ubiquitous sensor network service, the ubiquitous sensor network ontology module having the actual data according to the metadata of the sensor ontology and service ontology, and the metadata of the sensor ontology and service ontology The metadata transmitted from the semantic database management system and the ubiquitous sensor network ontology module is delivered to the semantic database management system, and the query is received and delivered to the semantic database management system to access the loaded metadata. And a semantic database utility module for receiving the query from the user device, and transmitting the query statement to the semantic database utility module, and sending the response to the user device. It characterized in that it comprises a communication module for communication.

The second invention relates to a SPARQL transform module for generating a query for a sensor search or a service search by a semantic service search user device for a ubiquitous sensor network service, and sending the query to the semantic service search server. A communication module for transmitting and receiving the response from the semantic service search server, and a graphical user interface module for allowing the user to input or confirm a desired search result.

According to the third aspect of the present invention, a method for building a ubiquitous sensor network ontology in a semantic service search server for ubiquitous sensor network service includes the steps of creating a schema for sensor ontology and service ontology, and after creating the schema, a new sensor or service. Adding a sensor or service instance according to the schedule if the new sensor or service is added, converting a ubiquitous sensor network ontology to triple after adding the instance, and Uploading the converted triples to the semantic database management system.

According to the fourth aspect of the present invention, a semantic service search method for a semantic service search user device for ubiquitous sensor network service includes: checking whether a search condition is input while a search term ontology is up to date; And converting the SPARQL query to the server after converting the SPARQL, and receiving a search result from the server and selecting a desired service and downloading it from a corresponding Uniform Resource Locator (URL). do.

The fifth invention is a semantic service search system for ubiquitous sensor network service, create a schema for the sensor ontology and service ontology, add a sensor or service instance according to the schema when a new sensor or service is added, ubiquitous sensor A server that converts network ontology into triples and uploads the triples to semantic database management system to build a ubiquitous sensor network ontology, and creates a SPARQL query based on the entered search conditions while the search term ontology is up-to-date. And a user device which receives a search result from the server and selects a desired service and downloads it from a corresponding Uniform Resource Locator (URL).

As described above, the present invention builds a sensor ontology and a service ontology so that all users and developers can share USN service-related concepts, so that service authors do not have to make exceptions for each sensor. More services can be easily implemented. In addition, the user can more easily and accurately search for the desired sensor from the sensor ontology. The user can more easily and accurately search for the desired USN service from the sensor ontology and service ontology.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description, specific matters such as a specific kind or location of a sensor or a service are shown, which are provided to help a more general understanding of the present invention, and the present invention may be practiced without these specific matters. It will be obvious to those skilled in the art. In the following description of the present invention, 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.

1 is a diagram showing the configuration of a semantic service search system according to an embodiment of the present invention.

The semantic service search system is divided into a server 100 and a user device 200.

The server 100 is composed of USN ontology 11, semantic DBMS 13, semantic database utility module 15 and communication module 17, and communicates with the user device 200.

USN Ontology 11 is a Web Ontology Language (OWL) file that defines the concepts and relationships between them. USN ontology 11 stores sensor data, that is, metadata (real metadata) and real data (instance) of the sensor, and USN service application data, that is, metadata and real data about services. Meta data that can explain the relationship between the stored real data and the actual data can be converted into a triple (triple) form. A triple consists of three data elements: subject, predicate, and object. A plurality of triples can be combined to form concepts and relationships.

In other words, metadata of the USN ontology 11 is stored in the sensor ontology 11A and the service ontology 11B. The sensor ontology 11A summarizes the concepts of type, location, company, etc. The service ontology 11B summarizes the concepts of operation, input, and output.

Semantic Database Management System (DBMS) 13 is a system software that provides a convenient and efficient environment for storing and retrieving massive amounts of triple data. That is, tens of thousands of triples are systematically stored to enable effective searching and inference. SPARQL (S PARQL P rotocol a nd R DF Q uery anguage L) is a semantic query language can be used to extract the desired data from the SPARQL semantic database.

Data loaded into semantic DBMS 13 is accessible through semantic database utility module 15.

The user device 200 includes a communication module 22, a SPARQL conversion module 24, and a graphical user interface (GUI) module 26. The user device 200 provides a desired search result to the user through interaction with the server 100.

FIG. 2 is a diagram illustrating a configuration example of the USN ontology of FIG. 1.

Sensor ontology 11A defines the relationship between sensor-related metadata and metadata. That is, metadata (schematic) of sensor-related data is designed. The sensor ontology 11A consists of metadata such as sensor type S1, position S2, manufacturer S3, identification S4, and the like, and actual data (instances) thereof.

Service ontology 11B defines the relationship between service-related metadata and metadata. That is, metadata (schema) of service-related data is designed. The service ontology 11B consists of metadata such as USN service type S5, operation type S6, sensor type S1, and the like, and actual data (instances) thereof.

3 is a flowchart illustrating a method of building the USN ontology of FIG. 1.

In step 3a, a schema for sensor ontology and a service ontology are created. After creating the schema, check if a new sensor or service is added in step 3b. If a new sensor is added, add a sensor instance according to the scheme in step 3c. If a new service is added, add a service instance according to the schedule in step 3d. After adding an instance in step 3c or 3d, the USN ontology data is converted into triples in step 3e. In step 3f, the triple is uploaded using the semantic DB utility module 15.

Referring back to FIG. 1, as an example of an instance of a sensor ontology 11A (hereinafter referred to as a sensor instance), information on an oxygen amount measuring sensor called 'Oxygen_Senser_118' is stored in an OWL form as follows.

<owl: Class rdf: ID = "Chemical_proportion">
<rdfs: subClassOf><owl: Class rdf: ID = "Sensor"/></ rdfs: subClassOf>
</ owl: Class>
<owl: Class rdf: ID = "oxygen_sensor">
<rdfs: subClassOf><owl: Class rdf: ID = "Chemical_proportion"/></ rdfs: subClassOf>
</ owl: Class>
<oxygen_sensor rdf: ID = "oxygen_sensor_118">
<hasID>"sa0045"</hasID>
<madeBy rdf: resource = "# allsensing"/>
<hasLocation> 3633.2108, N, 12847.6608, E </ hasLocation>
</ oxygen_sensor>

Based on metadata of grade (sensor grade, company grade) and attributes (rdf: type, hasID, hasLocation, madeBy), it is a chemical proportional sensor, manufactured by AllSensing, 3633.2108, N, You can see that it is installed at position 12847.6608, E.

4 is a diagram illustrating an example of such a sensor instance as a triple graph structure.

Referring back to FIG. 1, as an example of an instance of a service instance 11B (hereinafter referred to as a service instance), information about a service called 'USNService_12' is stored in an OWL form as follows.

<USNService rdf: ID = "USNService_12">
<hasDescription>
As you climb high mountains, you analyze the oxygen levels in the air as the altitude rises.
</ hasDescription>
<hasOperation>
<Oneway rdf: ID = "Oneway_13">
<hasInput rdf: resource = "# oxygen_sensor_118"/>
<hasInput rdf: resource = "# altimeter_37"/>
</ Oneway>
</ hasOperation>
</ USNService>

Based on metadata of class (USN service class, operation class) and properties (rdf: type, hasDescription, hasOperation, hasInput), it has one-way operation and inputs 'oxygen_sensor_118' and 'altimeter_37' It can be seen that the sensor value is used.

5 is a diagram illustrating an example of the service instance as a triple graph structure (however, information on the altimeter sensor 'altimeter_37' is omitted).

When searching for a USN service, USNService_12 could be searched only by searching for a service using a specific sensor called oxygen_sensor_118. However, if the above-described USN ontology is used, a general sensor type such as chemical_proportion or oxygen_sensor can be searched without adding a special description to the USN service.

For example, a user can easily retrieve a USN service associated with a sensor without knowing the specific serial number oxygen_sensor_118 without detailed knowledge of the sensor. In addition, the same USN services operate in multiple regions, so you can search for USN services that are readily available in a particular region.

6 is a flowchart illustrating a method of searching for a desired service through a semantic service search system according to an exemplary embodiment of the present invention.

In step 6a, it is checked whether the search term ontology is up to date. In this case, if the search term ontology is up-to-date, it is checked whether a search condition is input in step 6b. The search condition may be input from the user. On the other hand, if it is determined in step 6a that the search term ontology is not up-to-date, in step 6c, the server searches for the latest search term from the server, and then proceeds to step 6b.

After detecting the input of the search condition in step 6b, the search condition is converted to SPARQL in step 6d. In step 6e, the SPARQL query is sent to the server. In step 6f, the server receives a search result (USN service list) from the server, and then checks whether a desired service is selected in step 6g. If the desired service is selected, it is downloaded from the URL (Uniform Resource Locator) in step 6h. If the desired service is not selected, the operation is terminated.

FIG. 7 is a diagram illustrating a graphical user interface for user-friendly SPARQL transformation occurring in the user device of FIG. 1.

The illustrated user-friendly SPARQL transformation can be executed from a user PC or a mobile terminal. This makes it easier for users to search for sensors and services. The sensor search refers to a search for sensor information stored in the USN ontology 11 of the server 100 illustrated in FIG. 1. The service search refers to a search for service information (USN service application) stored in USN ontology 11.

To search for ontology, Simple Protocol and RDF Query is a resource description framework (RDF) query language created by the World Wide Web Consortium (W3C), an international standardization organization for the Web. Language) is required. That is, SPARQL is used to find desired data from triples stored in the semantic DBMS 13 of the server 100 as shown in FIG. 1. However, it is difficult for a user to write SPARQL himself. Thus, the user device 200 shown in FIG. 1 includes a SPARQL conversion module 24 and a GUI module 26 to help a user easily search for a USN service. The SPARQL conversion module 24 and the GUI module 26 may be implemented in the form of a user-friendly SPARQL conversion program.

The GUI module 26 automatically converts user-created search conditions into SPARQL. The transformation finds the actual data of the USN service, that is, the instance, and contains the actual URL where the service operates. The user search condition refers to a type of service or a sensor used in a service or a location of the sensor.

The SPARQL transformation module 24 creates a query statement and sends it to the semantic DB utility module 15. This allows you to get accurate search results from a lot of data. Access the USN service application URL provided as a result of the search and download the service. The query made by SPARQL conversion module 24 is largely divided into sensor search query and service search query.

The following query is written to find a thermal sensor, for example.

PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX MySensor: <http://www.owl-ontologies.com/MySensor.owl#>
SELECT? Subject WHERE {
? subject rdf: type MySensor: Heat_Sensor
}

In the above query, after WHERE, write the condition that the desired data must satisfy in triple format. To solve the above triple form, "subject is rdf: type MySenser: Heat_Senser".

Sensor search query can be made by combining features of {type of sensor, manufacturer, installed location, etc}. In addition, when a new schema is added to the sensor ontology, new features can be directly combined to create more kinds of queries.

The following query is written to find USN service related to oxygen measurement, for example.

PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX MySensor: <http: //www.owl=ontologies.com/MySensor.owl#>
SELECT? Subject WHERE {
? subject rdf: type MySensor: USNService.
? subject MySensor: hasOperation? x.
{? x MySensor: hasOutput? y.} UNION {? x MySensor: hasInput? y.}
? y rdf: type MySensor: oxygen_Sensor
}

Describing the triple form in the above query, "The object is a USN service, and includes an operation that has an oxygen sensor as an input or an output."

The service search query can be made by combining features of {action type, input / output type, location, keyword, etc.}. In addition, when a new schema is added to the service ontology, new features can be directly combined to create more kinds of queries.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by the equivalents of the claims.

1 is a diagram illustrating a configuration of a semantic service search system according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating a configuration example of the USN ontology of FIG. 1. FIG.

3 is a flowchart illustrating a method of building the USN ontology of FIG.

4 is a triple graph structure illustrating an example of a sensor instance according to an exemplary embodiment of the present invention.

5 illustrates a triple graph structure of an example of a service instance according to an embodiment of the present invention.

6 is a flowchart illustrating a method of searching for a desired service through a semantic service search system according to an exemplary embodiment of the present invention.

FIG. 7 illustrates a graphical user interface for user-friendly SPARQL transformation taking place in the user device of FIG.

Claims (15)

In the semantic service search server for ubiquitous sensor network service, A ubiquitous sensor network ontology module having actual data according to metadata of a sensor ontology and a service ontology, A semantic database management system for storing metadata of the sensor ontology and service ontology; A semantic database utility that delivers and loads metadata transmitted from a ubiquitous sensor network ontology module to the semantic database management system, receives a query, and delivers it to the semantic database management system to access the loaded metadata. Module, And a communication module for receiving the query from the user device and delivering the query to the semantic database utility module, and sending a response to the user device. The method of claim 1, The ubiquitous sensor network ontology module is a semantic service search server comprising a web ontology language file. The method of claim 2, Meta data delivered from the ubiquitous sensor network ontology module is a semantic service search server, characterized in that the triple form. The method according to any one of claims 1 to 3, wherein The sensor ontology defines a relationship between the metadata related to the sensor and the metadata, and includes at least one metadata of the type, location, manufacturer, or identification of the sensor and corresponding data. Semantic Service Search Server. The method according to any one of claims 1 to 3, wherein The semantic service is characterized in that the service ontology defines a relationship between the metadata related to the service and the metadata, and includes at least one metadata of the type of service, the type of operation, or the type of sensor and the corresponding data. Search server. In the semantic service search user device for ubiquitous sensor network service, SPARQL conversion module for creating a query for sensor search or service search in response to a user input, A communication module for transmitting the query to the semantic service search server and receiving the response from the semantic service search server; And a graphical user interface module for allowing the user to input or confirm a desired search result. The method of claim 6, The semantic service search user device, characterized in that the query form is triple. The method according to claim 6 or 7, The semantic service search user device characterized in that the query for the sensor search is made by combining the features of the sensor. The method of claim 8, The features are semantic service search user device, characterized in that the type of sensor, the manufacturer, the location installed. The method according to claim 6 or 7, And the query for the service search is made by combining the features of the service. The method of claim 10, The features are semantic service search user device, characterized in that the type of operation, type of input / output, location, keywords. In the method for building ubiquitous sensor network ontology in semantic service search server for ubiquitous sensor network service, Creating a schema for sensor ontology and service ontology, After creating the schema, and checking whether a new sensor or service is added, Adding the sensor or service instance according to the schedule when the new sensor or service is added, Converting the ubiquitous sensor network ontology to triple after adding the instance; And uploading the converted triple into a semantic database management system. A semantic service search method for ubiquitous sensor network service Checking whether a search condition is entered while the search term ontology is up-to-date; Converting the input search condition into SPARQL; Transmitting the SPARQL query to the server after the SPARQL conversion; And receiving a search result from the server, selecting a desired service, and downloading the corresponding service from a corresponding URL (Uniform Resource Locator). The method of claim 13, Before performing the process of checking whether the search condition is input, Checking whether the search term ontology is up to date; And if the search term ontology is not up to date, updating the latest search term from the server. In the semantic service search system for ubiquitous sensor network service, Create a schema for sensor ontology and service ontology, add a sensor or service instance according to the schema when a new sensor or service is added, convert ubiquitous sensor network ontology to triple, and upload the triple to semantic database management system. Server to build ubiquitous sensor network ontology, In the state that the search term ontology is up-to-date, a SPARQL query is made and transmitted to the server based on the input search condition. A semantic service search system comprising a user device.

Images