KR101743731B1 - Method and apparatus for processing quary based on ontology generated by collaborating distributed data - Google Patents

Abstract

The present invention relates to a method and an apparatus for processing a query based on an ontology generated by integrating distributed data. The present invention relates to a method and an apparatus for processing a query based on an ontology generated by integrating distributed data according to an embodiment of the present invention The method comprising receiving data for at least one of a terminal, a service and a user from a plurality of terminals in the same network or within a short range, generating a proximity user data table containing the received data, receiving a query, Processing the query and providing the processed result data by accessing the user data table, and integrating and associating the data generated in each terminal with one another, so that users can share data with each other through a query To create distributed data that can be There is an effect that it is possible to provide a method and apparatus for handling a query based on an ontology

Description

TECHNICAL FIELD The present invention relates to a method and apparatus for processing a query based on an ontology generated by integrating distributed data,

The present invention relates to a method and apparatus for processing a query based on an ontology generated by integrating distributed data, and a method and an apparatus for processing a query based on an ontology generated by integrating distributed data among devices.

Recently, the use of smart terminals such as smart phones and object devices and the spread of applications have rapidly increased, and smart terminals are providing various services to users. Personal information such as personal schedule management, contact management, etc. can be managed with a smart terminal easily from services that can handle very large information.

As a result, users' dependence on smart devices and their needs have increased greatly and are expected to grow steadily. In addition, the range of services available to smart terminals will continue to expand.

Accordingly, there is a growing need for information and service sharing among users. The present invention relates to a need for a service between a plurality of smart terminals and a plurality of users as well as information exchange and service between one smart terminal and its users by establishing a connection relationship of various information. In addition, users want to integrate vast amounts of information to obtain deeper and wider processed information.

This is related to meta-knowledge, which refers to knowledge based on a meta-knowledge model as knowledge to discover and access distributed data and terminal services between connected terminals. In order to utilize the meta knowledge, a meta knowledge base, which is a database capable of storing and searching meta knowledge for accessing data and terminal services, is needed.

However, each piece of information based on this meta-knowledge has difficulty in accessing and retrieving relevant data because the information is distributed in a local database. In addition, since data is distributed, it is difficult to provide data with a connection relation to a user.

Accordingly, it is necessary to discuss a method of applying a method and apparatus for convergence and synthesis of distributed knowledge to a smart terminal as well as a method of providing a personal service in accordance with the development of a smart terminal and an application service.

[Related Technical Literature]

Resource technology framework using ontology schema combined with object name dictionary and mining rules Network construction apparatus and method (Korean Patent No. 10989581)

The present invention is directed to an ontology that integrates various services and data generated by each terminal into one, processes queries, and allows users to share the processed queries. And to provide a method and apparatus for processing a query.

Another problem to be solved by the present invention is to collectively generate distributed data that correlates various services and data generated in each terminal, processes the user's query and provides data corresponding to the user's query, A method and apparatus for processing a query based on an ontology.

The problems of the present invention are not limited to the above-mentioned problems, and other problems not mentioned can be clearly understood by those skilled in the art from the following description.

According to an aspect of the present invention, there is provided a method for processing a query based on an ontology generated by integrating distributed data according to an embodiment of the present invention includes: Receiving data for at least one of the users, generating a proximity user data table containing the received data, processing the query by receiving a query, accessing a proximity user data table, The method comprising the steps of:

According to another aspect of the present invention, a query is input as characters or voices.

According to still another aspect of the present invention, there is provided a method of transmitting data to a terminal, comprising the steps of: receiving updated or new data from at least one of a plurality of terminals and updating a neighboring user data table.

According to another aspect of the present invention, the step of receiving data and updating the proximity user data table further comprises converting the data into a language in which the proximity user data table is created.

According to another aspect of the present invention, the step of providing result data is a step of converting result data into JSON form and providing the result data.

According to another aspect of the present invention, the step of providing the result data is characterized by selecting and providing common data equal to or greater than a predetermined number of terminals in accordance with a predetermined priority order.

In order to solve the above problems, a query processing apparatus according to an embodiment of the present invention receives data for at least one of a terminal, a service, and a user from a plurality of terminals existing in the same network or a short distance, An initialization module for generating a proximity user data table including the proximity user data table; And

And a query module that receives the query, accesses the proximity user data table, processes the query, and provides the processed result data.

According to another aspect of the present invention, a query is input as characters or voices.

According to still another aspect of the present invention, there is provided a data management module for receiving updated or new data from at least one of a plurality of terminals and updating a neighboring user data table.

According to another aspect of the present invention, the data management module converts data into a language in which the proximity user data table is created.

According to another aspect of the present invention, the query module converts the result data into a JSON format and provides the resultant data.

According to another aspect of the present invention, the query module is characterized by selecting and providing common data in accordance with a predetermined priority or a predetermined number of terminals or more.

The details of other embodiments are included in the detailed description and drawings.

The present invention has the effect that users can share processed queries by processing various services and data generated from each terminal into a single unit and processing a query.

The present invention has an effect of associating various services and data generated in each terminal, processing data of a user, and providing data corresponding to a user's query.

The effects according to the present invention are not limited by the contents exemplified above, and more various effects are included in the specification.

1 is a diagram illustrating a relationship between a plurality of terminals and an apparatus for processing a query according to an embodiment of the present invention.
2 shows a schematic configuration of an apparatus for processing a query according to an embodiment of the present invention.
FIG. 3 illustrates a procedure of processing a query according to a method of processing a query based on an ontology generated by integrating distributed data according to an embodiment of the present invention.
4 schematically illustrates an apparatus for processing queries according to an embodiment of the present invention.
FIG. 5 illustrates a structure of a proximity user data table according to another embodiment of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS The advantages and features of the present invention and the manner of achieving them will become apparent with reference to the embodiments described in detail below with reference to the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Is provided to fully convey the scope of the invention to those skilled in the art, and the invention is only defined by the scope of the claims.

The shapes, sizes, ratios, angles, numbers, and the like disclosed in the drawings for describing the embodiments of the present invention are illustrative, and thus the present invention is not limited thereto. In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail. Where the terms 'comprises', 'having', 'done', and the like are used herein, other parts may be added as long as '~ only' is not used. Unless the context clearly dictates otherwise, including the plural unless the context clearly dictates otherwise.

In interpreting the constituent elements, it is construed to include the error range even if there is no separate description.

Although the first, second, etc. are used to describe various components, these components are not limited by these terms. These terms are used only to distinguish one component from another. Therefore, the first component mentioned below may be the second component within the technical spirit of the present invention.

Like reference numerals refer to like elements throughout the specification unless otherwise specified.

It is to be understood that each of the features of the various embodiments of the present invention may be combined or combined with each other partially or entirely and technically various interlocking and driving is possible as will be appreciated by those skilled in the art, It may be possible to cooperate with each other in association.

The embodiments of the present disclosure have been carried out and studied as part of the information communication and broadcasting R & D projects of the future creation science department and the information and communication technology research promotion center. [R0101-15-0144, (Exobrain-4 detail) Development of autonomous intelligent knowledge / device collaboration framework technology]

Hereinafter, terms used in this specification will be defined.

In the present specification, the term " query " is used in the same meaning as a query, and means a search term input by a user. Through the query, the data existing in the data table can be searched through the condition desired by the user, and the retrieved result can be inquired. Here, the query can be input as a character or a voice.

As used herein, " ontology " means a formalization and specification of shared conceptualization of each field in an information system. In other words, ontology is a conceptual and computer-mediated representation of what people have seen, heard, felt and thought about the world through discussions. The meta - knowledge that is designed using the ontology can be extended and connected indefinitely, making it possible to make knowledge unique.

1 is a diagram illustrating a relationship between a plurality of terminals and an apparatus for processing a query according to an embodiment of the present invention.

Referring to FIG. 1, a host terminal 111 and a plurality of terminals 112 and 113 exist in the same network or in a short distance. The host terminal 111 collects data of the plurality of terminals 112 and 113 and stores the collected data in the local database 111a of the host terminal 111. [ The stored data is stored in the form of a table in the local database 111a.

The host terminal 111 stores the data from the plurality of terminals 112 and 113 into the local database 111a in the form of meta-knowledge classified into terminals, services, and users. In a conventional portable terminal, when a query is input to a program such as a siri, a query is processed using data of the terminal itself and information accessible via the Internet. The host terminal 111 according to an embodiment of the present invention collects data, i.e., meta knowledge, of a plurality of terminals 112 and 113 that are in the same network or are communicatively connected, stores the collected data in the local database 111a, Process queries based on knowledge.

That is, terminals located in the same network or in a short distance can share data, retrieve and access data, and process queries with ontology-based meta-knowledge generated based on the data.

2 shows a schematic configuration of an apparatus for processing a query according to an embodiment of the present invention.

2, the query processing apparatus 200 in the host terminal includes an initialization module 210, a data management module 220, a query module 230, and a proximity user data table 240.

The initialization module 210 receives data from a plurality of terminals existing in the same network or in a short distance. Specifically, the initialization module 120 receives data on at least one of a terminal, a service provided from the terminal, and a terminal user.

The initialization module 210 includes a conversion module 211, a table generation module 212, and an input module 213. The conversion module 211 converts data received from a plurality of terminals into a language in which the proximity user data table 240 is to be created. For example, the language in which the proximity user data table 240 is to be created may be SQL. The table generation module 212 generates a table for storing data received from a plurality of terminals. Here, the table generated by the table generation module 212 is the proximity user data table 240, and may be written in, for example, SQL. The data stored in the proximity user data table 240 is data for at least one of a terminal, a service, and a user. The input module 213 inputs data for at least one of the terminal, the service, and the user to the proximity user data table 240 generated by the table generation module 212. The specific proximity user data table 240 will be described later with reference to FIG.

The data management module 220 updates the proximity user data table 240 by receiving changed or new data from a plurality of terminals. Specifically, when the data already stored in the neighboring user data table 240 generated by the initialization module 210 is changed, the data management module 220 receives the changed data from at least one of the plurality of terminals . The data management module 220 receives new data not stored in the proximity user data table 240 generated by the initialization module 210 from at least one of the plurality of terminals.

The data management module 220 includes a conversion module 221, an input module 222, a deletion module 223, and a modification module 224. The conversion module 221 converts the received changed data or new data into the language in which the proximity user data table 240 is created. The input module 222 inputs the data converted by the conversion module 221 into the language in which the proximity user data table 240 is created into the proximity user data table 240. The data input by the input module 222 to the proximity user data table 240 is new data received from at least one of the plurality of terminals that the initialization module 210 has not stored in the proximity user data table 240 . The deletion module 223 deletes the data that the initialization module 210 has entered in the proximity user data table 240. [ The modification module 224 modifies the data stored in the proximity user data table 240 by the initialization module 210. Specifically, the modification module 224 modifies the data stored in the proximity user data table 240 by the initialization module 210 into changed data received from at least one of the plurality of terminals.

The query module 230 receives the query and accesses the proximity user data table 240 to process the query. The query module 230 then provides the processed result data. The result data represents the results for the query processed by the query module 230. Specifically, the query module 230 receives the query from the host terminal and accesses the proximity user data table 240 to provide the result data present in the proximity user data table 240.

The query module 230 includes a transformation module 231, a user query module 232, a terminal query module 233, an input and output value query module 234, a service query module 235, and a provision module 236 do. The conversion module 231 converts the received query into the JSON format of the result data retrieved by the user query module 232, the terminal query module 233, the input and output value query module 234, and the service query module 235 Conversion. Here, the JSON type is a format using a user-readable text. In other words, the JSON form means a form that expresses a character. The conversion module 231 can recognize the type of the query and transmit it to the appropriate module of the user query module 232, the terminal query module 233, the input and output value query module 234, and the service query module 235 have. The user query module 232 queries the data of the service related to the user existing in the proximity user data table 240 based on the converted query. The terminal query module 233 inquires data of a service related to a terminal existing in the proximity user data table 240 based on the converted query. The input and output value query module 234 queries the data of a service having a specific input value and a result value existing in the proximity user data table 240 based on the converted query. The classification query module 235 queries the data of the service having the specific classification existing in the proximity user data table 240 based on the converted query. The user query module 232, the terminal query module 233, the input and output value query module 234 and the service query module 235 may receive the query and inquire the data at the same time, Only one of the modules of the user query module 232, the terminal query module 233, the input and output value query module 234, and the service query module 235 inquires the data. You may. The providing module 236 outputs the result data retrieved by the user query module 232, the terminal query module 233, the input and output value query module 234 and the service query module 235 to the host terminal Provided through the Department. The providing module 236 may also provide the retrieved result data to at least one of the plurality of terminals. The result data provided by the providing module 236 is transferred to the converting module 231 and converted into a JSON form.

Accordingly, the query processing apparatus 200 stores and manages data received from a plurality of terminals, and provides the user with data of other users so that necessary data can be shared with each other.

FIG. 3 illustrates a procedure of processing a query according to a method of processing a query based on an ontology generated by integrating distributed data according to an embodiment of the present invention. For convenience of explanation, the components will be described with reference to FIG. 1 and reference numerals.

A method of providing a query according to an embodiment of the present invention is initiated by the initialization module 210 receiving data for at least one of a terminal, a service, and a user (S310).

The initialization module 210 receives data for at least one of a terminal, a service, and a user from a plurality of terminals existing in the same network or a short distance. Here, the data on the terminal refers to a terminal type such as a tablet PC or a smart phone, a specification of a terminal, a terminal name, and a terminal ID. A service is a program installed in a terminal and providing a specific function to a user, that is, an application. The data for the service is the name of the service, the input value, the output value, the classification, the data contained in the service, and the service URI. The data for the user is the name of the terminal user. The data for at least one of the terminal, service, and user is converted into the language in which the proximity user data table is created.

Next, the initialization module 210 creates a proximity user data table (S320).

The initialization module 210 generates a proximity user data table including data received from a plurality of terminals. Accordingly, the proximity user data table 240 includes a terminal ID, a user ID, a user name, terminal name information, a terminal type, a terminal specification, service name information, service input, service output, service classification, . The structure of the detailed proximity user data table will be described later with reference to FIG. The initialization module 210 may generate the proximity user data table 240 in SQL.

If the data contained in the proximity user data table 240 is changed or new data is added to the proximity user data table 240, the data management module 220 may update the new or changed data from at least one of the plurality of terminals And may update the proximity user data table 240. [ Here, the received new data or changed data is converted into a language in which the proximity user data table is created and stored in the proximity user data table 240.

The query module 230 then receives the query and accesses the proximity user data table to process the query (S330).

The query module 230 receives the query from the host terminal and processes the query by accessing the proximity user data table 240 to perform the query. The query includes a search word for receiving data of a service related to a user, a search word for receiving data of a service related to the terminal type, a search word for receiving data of a service having an input value and an output value, It may be a search word for receiving the service. For example, a query for receiving data of a service associated with a user may be a name of the user. A query for receiving data of a service related to a terminal type may be a terminal type, i.e., a smart phone or a tablet PC. A query for receiving data of a service having an input value and an output value may be a type of a service input value and a type of a service output value. For example, a query for a calendar application can be an event, which is the date value of the calendar application and the service output value. Here, the date and the event indicate that the type of the input value of the service is not the actual event such as actual date and meeting such as 2015.12.23, the type of the input value of the service is the date, and the type of the output value of the service is the event. A query for receiving data of a service having a classification may be a category of an application, such as a calendar, a contact, a weather, and the like. Because the query is of JSON type, the proximity user data table is converted into the created language to access the proximity user data table. Accordingly, the query module 230 accesses the proximity user data table to provide data associated with the query.

Subsequently, the query module 230 provides the processed result data (S340).

The query module 230 includes a query for receiving data of a service related to a user, a query for receiving data of a service related to a terminal type, a query for receiving data of a service having an input value and an output value, And provides result data that is data associated with at least one of the queries for receiving data of the service. Here, the result data may be a service name and a URI.

The query module 230 may select and provide common data according to a predetermined priority or over a predetermined number of terminals. Specifically, when there are a plurality of pieces of data associated with the query, the query module 230 may select and provide data according to a predetermined priority order. For example, if the data associated with the query is a XXX calendar, a YYY calendar, a ZZZ calendar, or an AAA calendar, the predefined priority of the data to provide is YYY calendar followed by ZZZ calendar, AAA calendar, and XXX calendar. Accordingly, the query module 230 provides the service name and URI in the following order: YYY calendar, ZZZ calendar, AAA calendar, and XXX calendar. In addition, when there are a plurality of pieces of data related to the query, the query module 230 can select and provide common data equal to or larger than a predetermined number of terminals. For example, when a service query called calendar is received in the query module 230, the calendar service is accessed in the proximity user data table 240 to retrieve the name of the terminal and the calendar service using the calendar service. Accordingly, when data indicating that five terminals use the XXX calendar and two terminals use the YY calendar exists, the query module 230 can select and provide the XXX calendar, which is common data of four or more terminals, which is a predetermined number of terminals. The result data provided by the query module 230 is converted into a JSON form and provided. A detailed description of the result data will be given later with reference to FIG.

Accordingly, the query processing device stores data received from a plurality of terminals and provides the user with data according to priority or common data equal to or greater than a predetermined number of terminals, so that the user can obtain accurate and various data.

4 schematically illustrates an apparatus for processing queries according to an embodiment of the present invention.

4, the query processing apparatus includes a user name 410, a terminal type 420, a service name 430, a service classification 440, a service input value 450, (460), and stores the received data in the proximity user data table. The data are semantically matched to each other. Here, semantic matching means that data is matched so that the device understands the meaning of data and can logically infer.

Referring to FIG. 4, when a user name 410 is received, a query processing unit provides a service name and a URI used by Hong Kil Dong. In addition, when the terminal type 420 receives a query that is a smart phone, the query processing device provides the service name and the URI being used in the smartphone. When the query is received that the service classification 430 is a calendar, the query processing device provides the name and URI of the calendar service being used and receives the query that the service input value 450 and the service output value 460 are date and event The query processing device provides the name and URI of the service using the date and event as the service input value 450 and the service output value 460. Additionally, the query processing device may provide the result data for the query, as well as the service name and URI, as well as all the data associated with the query, i.e., meta-knowledge. For example, upon receiving a query for service classification 430, it may provide all user names 410, terminal types 420 and service names 440 that use the service of the classification corresponding to the query. Upon receipt of the query for the service input value 450 and the service output value 460, a service classification 430 using the service input value 450 and the service output value 460 corresponding to the query, (440), user name (410) and terminal type (420) using the corresponding service.

Accordingly, the query processing apparatus collects a user name, a terminal type, a service name, a service classification, a service input value, and a service output value using a semantic-matched terminal from a plurality of terminals, and provides query result data to the user do.

FIG. 5 illustrates a structure of a proximity user data table according to another embodiment of the present invention.

Referring to FIG. 5, the proximity user data table 500 includes data for at least one of a terminal, a service, and a user from a plurality of terminals. Specifically, the data for the terminal includes a terminal ID, a terminal name, and a terminal type. The data for the service includes a service name, a service input value, a service output value, a service classification, and a service URI, and the data for the user includes a user ID and a user name. Therefore, the proximity user data table 500 is composed of 10 columns, and may be written in SQL.

Referring to FIG. 5, the proximity user data table 500 includes first data 510, which is data on a terminal, a service, and a user received from a terminal having a terminal ID of '0'. The first data 510 includes a terminal ID value of 0, a user ID value of 0, a user name value of Hong Kil Dong, a terminal type value of a smart phone, and a terminal name value of Galaxy X4. The first data 510 includes date data such as service input value 2015.12.23 input to the XXX calendar, which is a service name value used by the user Hong Kil Dong, XXX calendar, service output value output according to the service input value, The same event data, the calendar of the XXX calendar, and the URI of the XXX calendar. The first data 510 includes a contact list which is another service name value used by the user Hong Kil Dong, name data such as Kim Young Hee, which is a service input value input to the contact list, and service output value 010-1234-5678 A URI value of a contact list and a contact list, which are classified values of a contact list.

Referring to FIG. 5, the proximity user data table 500 includes second data 520, which is data on a terminal, a service, and a user received from a terminal having a terminal ID value of 1. The second data 520 includes a terminal ID value of 1, a user ID value of 1, a user name value of Chul-soo, a terminal type value of a smartphone, and a terminal name value GalaxyY6. The second data 520 includes date data such as 2015.12.12, a service input value input in the YY weather, YY weather, which is a service name value used by the user Kim, and cloud data and weather data , The UY value of the YY weather and the YY weather value.

The proximity user data table 500 may additionally include data according to the service regardless of the type of service and the size of data when another service is used by the user. In addition, the terminal ID and the user ID may be given in the order of data input to the proximity user data table 500, or they may be given in random numbers.

Accordingly, the query processing apparatus receives data for a terminal, a service, and a user from a plurality of terminals, and generates a proximity user data table including the received data, thereby providing the user with expanded data including a plurality of user- That is, the result data generated based on the meta-knowledge, and the data can be provided at a high speed because the data is classified according to the reference.

In this specification, each block or each step may represent a part of a module, segment or code that includes one or more executable instructions for executing the specified logical function (s). It should also be noted that in some alternative embodiments, the functions mentioned in the blocks or steps may occur out of order. For example, two blocks or steps shown in succession may in fact be performed substantially concurrently, or the blocks or steps may sometimes be performed in reverse order according to the corresponding function.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, which is capable of reading information from, and writing information to, the storage medium. Alternatively, the storage medium may be integral with the processor. The processor and the storage medium may reside within an application specific integrated circuit (ASIC). The ASIC may reside within the user terminal. Alternatively, the processor and the storage medium may reside as discrete components in a user terminal.

Although the embodiments of the present invention have been described in detail with reference to the accompanying drawings, it is to be understood that the present invention is not limited to those embodiments and various changes and modifications may be made without departing from the scope of the present invention. . Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. Therefore, it should be understood that the above-described embodiments are illustrative in all aspects and not restrictive. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

111 host terminal
111a local database
112, 113 terminal
200 Query processing device
210 initialization module
211, 221, 231 conversion module
212 Table creation module
213 input module
220 data management module
222 input module
223 Delete module
224 Modification module
230 Query Modules
232 User Query Module
233 Terminal Query Module
234 Input and Output Value Query Module
235 Classification Query Module
236 Providing module
240 proximity user data table
410 User Name
420 Terminal type
430 Service Classification
440 Service Name
450 Service input value
460 Service output value
500 proximity user data table
510 first data
520 second data

Claims (12)

Receiving data for a terminal, a service and a user from a plurality of terminals existing in the same network;
Wherein the neighboring user data table includes a terminal ID, a user ID, a user name, a terminal name information, a terminal type, a terminal specification, a service name information, Input data, output of service, classification of service, and service URI;
Processing the query by receiving a query and accessing the proximity user data table;
If the processed query is a query for the type of service, searches for the type of the service used by a plurality of terminals existing in the same network, and searches for the type of the most used service among the types of the searched services Selecting data as result data; And
And providing the selected result data based on the ontology generated by integrating the distributed data. The method according to claim 1,
Wherein the query is based on an ontology generated by integrating distributed data, which is input as a character or voice. The method according to claim 1,
Further comprising: receiving updated or new data from at least one of the plurality of terminals to update the proximity user data table, wherein the method further comprises processing the query based on an ontology generated by incorporating distributed data. The method of claim 3,
Receiving the data and updating the proximity user data table comprises:
And converting the data into a language in which the proximity user data table is created. A method for processing a query based on an ontology generated by incorporating distributed data. The method according to claim 1,
The step of providing the selected result data comprises:
And converting the selected result data into a JSON form and providing the converted result data to a JSON form. delete An initialization module for receiving data for a terminal, a service and a user from a plurality of terminals existing in the same network and generating a proximity user data table including the received data; And
Receiving a query and accessing the proximity user data table to process the query and if the processed query is a query for the type of service, And a query module that selects data as the result data and provides the selected result data based on the kind of the most used service among the types of the searched services,
The proximity user data table includes a table classified by terminal ID, user ID, user name, terminal name information, terminal type, terminal specification, service name information, service input, service output, service classification and service URI , Which is a device that processes queries based on an ontology that is generated by integrating distributed data. 8. The method of claim 7,
Wherein the query is based on an ontology that is generated by integrating distributed data, which is input as a character or voice. 8. The method of claim 7,
Further comprising a data management module for receiving updated or new data from at least one of the plurality of terminals and updating the proximity user data table, . 10. The method of claim 9,
The data management module includes:
Converting the data into a language in which the proximity-user data table is created; and processing the query based on the ontology generated by integrating the distributed data. 8. The method of claim 7,
The query module comprising:
And converting the result data into a JSON form to provide a query based on an ontology generated by integrating distributed data. delete

Images