KR20150003661A - Method and apparatus for managing resource - Google Patents

Abstract

An embodiment of the present invention provides a method and an apparatus for managing a resource. The apparatus for managing a resource generates a first instance with respect to a first community using a first ontology class with respect to a community including at least one resource as a member according to a goal. The apparatus for managing a resource generates a second instance with respect to a first resource using a second ontology class with respect to the resource. The apparatus for managing a resource estimates relationship between the first instance and the second instance.

Description

[0001] METHOD AND APPARATUS FOR MANAGING RESOURCE [0002]

The present invention relates to a method and apparatus for managing resources.

Sensors used in USN (Ubiquitous Sensor Network) have attributes of resources for USN service. In order to make the resources such as the sensors easy to use, it is important not only to connect the sensor to the USN but also to provide a method of efficiently defining the resources and utilizing the resources according to the purpose of the service. Even if an open resource is accessible to all, if the user has to control each resource individually, the system can not provide practical useful services.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a method and apparatus for dynamically and efficiently managing resources.

According to an embodiment of the present invention, a method is provided for a resource management apparatus to manage resources. The resource management method includes: generating a first instance for a first community using a first ontology class for a community that includes at least one resource as a member according to a goal; Generating a second instance of the first resource using a second ontology class related to the resource; And estimating a relationship between the first instance and the second instance.

The step of generating the first instance may include: receiving attribute information of the first community; And generating the first instance through a first template using the attribute information as an input parameter.

Wherein the generating the first instance comprises: receiving first information, which is already generated, representing first instance of a second community; And generating the first instance through a first template using the first information as an input parameter.

The first resource may be a first sensor in a sensor network.

Wherein the property information includes at least one of information on a member of the first community, information on an area of the first community, information on a lifetime of the first community, and information on the purpose of the first community .

The estimating step may include estimating a relationship between the first instance and the second instance using a semantic relation between the first ontology class and the second ontology class.

The resource management method includes: generating a third instance of a first space using a third ontology class related to a space; And estimating a relationship between the first instance and the third instance.

The resource management method includes: generating a fourth instance for a first time using a fourth ontology class related to time; And estimating a relationship between the first instance and the fourth instance.

The resource management method includes: generating a fifth instance for a first purpose using a fifth ontology class related to a purpose of a service; And estimating a relationship between the first instance and the fifth instance.

The resource management method may further include estimating a relationship between at least one of the third instance, the fourth instance, and the fifth instance and the second instance.

Wherein the resource management method comprises the steps of: when a second sensor is added to the sensor network, generating and storing a sixth instance of the second sensor using the second ontology class; Estimating a relationship between each of the instances of the first ontology class and the sixth instance and determining an instance corresponding to the sixth instance out of the instances of the first ontology class.

Wherein the resource management method comprises: deleting the second instance when the position of the first sensor is changed; Generating a sixth instance for the first sensor at the changed location using the second ontology class; And estimating a relation between each of the instances of the first ontology class and the sixth instance and determining an instance corresponding to the sixth instance among the instances of the first ontology class.

The resource management method comprising the steps of: transferring first information on each instance having a semantic relationship with the first instance to a state manager managing the state of the first community; And providing the first information to the application via the status manager in response to a request of the application.

According to another embodiment of the present invention, there is provided a method for a resource management apparatus to manage resources. The resource management method includes: generating a first instance for a first community using a first ontology class representing a community including at least one resource as a member according to an object; Creating a second instance of the first resource using a second ontology class representing the resource if the first resource is added; And estimating a relationship between the first instance and the second instance.

Wherein the resource management method comprises: deleting the second instance when the location of the first resource is changed; Generating a third instance of the first resource at the changed location using the second ontology class; And estimating a relationship between the third instance and the first instance.

Estimating a first semantic relationship between at least one third instance having a semantic relationship with the first instance and the second instance; And determining, based on the first semantic relationship, whether the second instance corresponds to a member of the first instance. The third instance may be any one of an instance of a third ontology class representing a space, an instance of a fourth ontology class representing a time, and an instance of a fifth ontology class representing a purpose of a service.

Further, according to another embodiment of the present invention, a resource management apparatus for managing resources may be provided. Wherein the resource management apparatus comprises: a first instance generation unit for generating a first instance of a first community using a first ontology class representing a community including at least one resource as a member according to the purpose; A second instance creation processing unit for creating a second instance of the first resource using a second ontology class representing a resource when the first resource is added; And an estimation processor for estimating a semantic relation between the first instance and the second instance.

Wherein the second instance creation processing unit updates the second instance based on the changed attribute information when the attribute information of the first resource is changed, and the estimation processing unit updates the second instance based on the updated attribute information, We can estimate the semantic relationship.

Wherein the estimation processing unit estimates a first semantic relationship between at least one third instance having a semantic relationship with the first instance and the second instance, and based on the first semantic relationship, It is possible to judge whether it corresponds to a member of the instance.

The resource management apparatus may further include a management processor for managing first information on each instance having a semantic relation with the first instance and providing the first information to the application in response to a request of the application .

According to an embodiment of the present invention, a community can be created by grouping resources (for example, sensors) according to a purpose or a condition using a semantic ontology scheme so that a user can easily use resources, To manage resources dynamically.

In addition, according to the embodiment of the present invention, it is possible to automatically manage dynamic change factors of resources regardless of services or applications at the system level. With this community-based dynamic management mechanism, any service or application can more easily use resources.

1 is a diagram illustrating a concept of a resource management method according to an embodiment of the present invention.
2 is a diagram illustrating a configuration of a resource management apparatus according to an embodiment of the present invention.
3 is a diagram illustrating an example of data modeling for a community ontology according to an embodiment of the present invention.
4 is a diagram showing an example of a relationship between a community ontology and a resource ontology according to an embodiment of the present invention.
5 is a diagram illustrating an example of a relationship between a community ontology and a spatial ontology according to an embodiment of the present invention.
6 is a diagram illustrating an example of a relationship between a community ontology and a time ontology according to an embodiment of the present invention.
FIG. 7 is a diagram illustrating a relationship between an instance created and an instance different when an instance of a community ontology class is created according to an embodiment of the present invention.
8 is a diagram illustrating an overall process of a resource management apparatus managing resources according to an embodiment of the present invention.
9 is a diagram illustrating a process in which a resource management apparatus according to an embodiment of the present invention creates and manages a community instance.
10 is a diagram illustrating a process of generating and managing a resource instance by a resource management apparatus according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily carry out the present invention. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly illustrate the present invention, parts not related to the description are omitted, and similar parts are denoted by like reference characters throughout the specification.

1 is a diagram illustrating a concept of a resource management method according to an embodiment of the present invention. Specifically, FIG. 1 shows a concept of a method for dynamically managing resources based on a community using an ontology.

In order to drive or use sensor resources connected to USN, USN middleware control function is used in existing USN service. However, in order to efficiently utilize a large number of sensor resources in a ubiquitous environment, a management structure and a service structure that allow a user to efficiently access sensor resources are required. In order to implement such a management structure and a service structure, a community computing method can be used. A community computing approach is a way in which entities (or resources) that execute a service form a community, collaborate, or provide services in order to achieve a particular interest (or goal). The embodiment of the present invention dynamically manages resources through a community computing method using ontology technology. Specifically, the embodiment of the present invention has a dynamic resource management structure (e.g., an ARS (Autonomous Resource Subscription) structure) based on a community ontology. For example, the ARS architecture can be used to dynamically allocate or de-allocate resources to a community for the purpose of the community, in the event that the attributes of the resources included (allocated) in the community in a global open environment are changed or new resources are added . In addition, the ARS structure allows a resource itself to join a community related to its own property when a resource is added, and when the resource property is changed, the resource itself leaves the existing community and joins the community related to the changed property Structure.

The embodiment of the present invention can easily interpret the attributes such as purpose of forming a community, spatial information, local information, etc. through a dynamic resource management mechanism. In addition, embodiments of the present invention can maintain and manage all of the data in a global environment through a dynamic resource management mechanism and allocate resources to communities associated with the attributes of resources. For example, the embodiment of the present invention may be used to determine whether a coordinate value is used to indicate a position where a resource (e.g., a sensor, an actuator, etc.) is installed, And can be easily mapped. Further, the embodiment of the present invention can obtain relationship data by inferring a relationship that is not given.

On the other hand, an ontology is an explicit and formal specification of a conceptualization of a domain of interest to conceptualize a field of interest. Specifically, an ontology can include a class, an instance, a relation, and a property as components. Standardization and research on ontology related technologies are mainly conducted by W3C (www.w3c.org). RDF (RDF Schema), OWL (Ontology Web Language), SPARQL (Simple Protocol and RDF Query Language), and so on are standard technologies related to ontology. This ontology related technology is an underlying technology for constructing and utilizing ontology. Depending on how the ontology is modeled (eg, class, attribute, relationship assignment, etc.), the nature of the service may vary.

An embodiment of the present invention relates to a mechanism for constructing a community based on a combination of a goal and space-time information, and dynamically managing sensor resources based on a community in order to efficiently manage various sensor resources in the USN. In the present invention, dynamic management refers to community management that can automatically accommodate changes in sensor resources due to new installation, movement, and discarding of sensors, and this means that functions such as community assignment / revocation of sensors are autonomously performed And the ontology mechanism that enables them to do so.

A community can have at least one resource (eg, USN sensor) as a member and associate with time information (eg, lifetime information) or spatial information (eg, local information) depending on the purpose. The dynamic resource management (eg, ARS) mechanism refers to a resource management mechanism that allows resources to autonomously subscribe and release themselves to the community, depending on the attribute changes (eg, new installations, location moves, etc.) of the resources do. A resource ontology class is an ontology class that expresses the concept of a resource. It represents a resource's attributes (eg, purpose, characteristics) and can be used for other ontology classes (eg, a community ontology class, a time ontology class, a space ontology class, ) Is expressed through a schema. The community ontology class is an ontology class for the community and can have various attributes such as member, purpose, lifetime, region, and so on. One of the properties of the community ontology class, the member property is related to the resource ontology class for community based dynamic resource management. The space ontology class is an ontology class for space and represents a space by administrative area (eg city, county, district, etc.), POI (Point of Interest, . A spatial ontology class can have an instance of various local information and can express spatial information of a resource. Purpose The ontology class is an ontology class for the purpose of the community and represents the purpose of the community. An instance is a fact with an attribute of an ontology class, and each ontology class can be a set of instances having the same attributes. For example, the community ontology class may include at least one community instance, the resource ontology class may include at least one resource instance, the spatial ontology class may include at least one spatial instance, The ontology class may include at least one time instance, and the destination ontology class may include at least one destination instance.

The community management layer L40 manages the community. Specifically, the community management layer L40 can create, discard, or change the community, or manage the life cycle of the community. For example, when the community management layer L40 creates a community instance, the community management layer L40 transmits the created community instance to the community ontology database 10 in order to store the generated community instance. The community management layer L40 provides information on the community to the dynamic resource management layer L30.

The community ontology database 10 provides inferred relationship data between the ontology classes (e.g., resource ontology class, space ontology class, time ontology class, destination ontology class, etc.) to the dynamic resource management layer L30. Specifically, the community ontology database 10 can provide the dynamic resource management layer L30 with inferred relationship data (e.g., relationship data between the community instance and the resource instance) between instances of different ontology classes.

The dynamic resource management layer (L30) manages resources dynamically. Specifically, the dynamic resource management layer L30 enables the resource itself to perform the join, the revocation, or the change to the community. The dynamic resource management layer L30 can provide information related to the community (e.g., information on resources belonging to the community) to the service / application.

The community state management layer L20 manages the state of the community through the state manager 20. [ Specifically, the state manager 20 receives and manages information related to the community from the dynamic resource management layer L30, and provides information related to the community to the service / application in response to the service / application request. Meanwhile, the embodiment of the present invention may be designed without the community state management layer L20.

The service execution layer L10 executes a service through an application. Specifically, the service execution layer L10 may request the state manager 20 for information related to the community. On the other hand, when there is no state manager 20, the service execution layer L10 can request information related to the community to the dynamic resource management layer L30.

2 is a diagram illustrating a configuration of a resource management apparatus 200 according to an embodiment of the present invention.

The resource management apparatus 200 includes a community instance definition module 210, an ontology agent 220, an ontology data speculation processing unit 230, a data storage processing unit 240, a resource management processing unit 250, and a state management processing unit 260 .

The community instance definition module 210 specifies (abstracts) the identification information (e.g., member, lifetime, resource, time, space, etc.) of the community for dynamic resource management through description logic. The created information is used to create a community instance.

The data storage processor 240 stores an ontology data model. The ontology data model determines the resources to achieve the purpose of the community by using the attribute information of the community. Specifically, the data storage processing unit 240 may store information on a community instance, a resource instance, a space instance, a time instance, or a target instance.

The resource management processing unit 250 communicates with the resources through the communication means. The resource management processor 250 recognizes the dynamic change of the resource when the dynamic change factor of the resource (e.g., when a new resource is installed and the location of the existing resource is changed) .

The ontology agent 220 receives the dynamic change information of the resource from the resource management processor 250. Also, the ontology agent 220 receives the attribute information of the community instance from the community instance definition module 210. The ontology agent 220 converts the received information according to the structure and format of the ontology data model, and stores the converted information in the data storage processing unit 240. In addition, the ontology agent 220 may inquire information stored in the data storage processing unit 240 in response to a service or application request, and provide the service or application. On the other hand, the ontology agent 220 may be designed to include a first instance creation processing unit for creating a community instance and a second instance creation processing unit for creating a resource instance.

The ontology data speculation processor 230 deduces a semantic relation between the newly input information (e.g., dynamic change information of resources and attribute information of the community instance) and other information stored in the data storage processor 240 Or estimated). Information having a semantic relationship is linked to each other.

The state management processor 260 manages the state of the community. The state management processor 260 corresponds to the state manager 20 in Fig. Meanwhile, the resource management apparatus 200 may be designed not to include the state management apparatus 260.

Now, it is assumed that the resource management apparatus 200 has a function of modeling data of the community ontology, a method of generating a community instance, a method of managing a community instance, a dynamic resource management mechanism in the case where a new resource is installed, And connection with the service will be described.

1. Data on community ontology modelling

How to define community ontology is very important in community based dynamic resource management method applying ontology technology. The data modeling for the community ontology can be changed according to the person who defines the ontology data model, and the type and the attribute of the ontology class for dynamic resource management can also be changed according to the requirement range. Hereinafter, for convenience of explanation, the community ontology data modeling will be described on the assumption that the resource is a USN sensor. Of course, if the type of resource is changed, the relationship between the resource attribute and the concept of the ontology class may be changed. However, the embodiment of the present invention can operate in a form including a variety of ontology data modeling. 3 to 6, the community ontology data modeling will be described in detail.

3 is a diagram illustrating an example of data modeling for a community ontology according to an embodiment of the present invention. In FIG. 3, it is assumed that the community ontology class has a Member attribute, a Goal attribute, a Lifetime attribute, and a Space attribute.

Figure 3 shows the semantic relationships required to construct a community. One community instance has semantic relations with the instant of each ontology class (eg resource instance, destination instance, spatial instance, time instance).

4 is a diagram showing an example of a concrete relationship between a community ontology and a resource ontology according to an embodiment of the present invention.

Specifically, FIG. 4 illustrates a semantic relationship between a sensor node attribute, which is one of the attributes of the resource ontology class, and an attribute of the community ontology class (for example, a member attribute and a Goal attribute) . In FIG. 4, the members of the community are the sensor nodes of the resource ontology, and the sensor nodes have the resource goals through the relationship with the subclasses.

5 is a diagram illustrating an example of a concrete relationship between a community ontology and a spatial ontology according to an embodiment of the present invention.

Specifically, FIG. 5 illustrates an ontology data structure representing a space attribute of the community ontology class. In FIG. 5, the community ontology class has a semantic relation with the attributes of the space ontology class (e.g., a region class, a POI class, and a location coordinate class) And how it can be interpreted in relation to. In other words, a community can be classified into three categories: spatial (eg, State, City, Gu, dong), POI (eg, Geographical Space, Fixed Structure such as a building) Location Coordinate, and the like. As illustrated in FIG. 5, the attributes of each spatial ontology class have an association relationship, and through this association, spatial attribute information (e.g., location coordinates) may include other spatial attribute information (e.g., POI) Lt; / RTI >

6 is a diagram illustrating an example of a relationship between a community ontology and a time ontology according to an embodiment of the present invention.

Specifically, FIG. 6 illustrates an ontology data structure that indicates a lifetime attribute of a community ontology class. As illustrated in FIG. 6, the attributes related to time that people refer to include time, attribute, duration, or semantic time of a time ontology class, , Daytime, nighttime, etc.). The Yeartime (year, month, day, hour, minute, and second) attributes and the daytime attributes can be used to specify the most basic time. An Actiontime attribute, a Period attribute, a Duration attribute, and a Semantic Time attribute may be used to specify (create) a resource lifetime of a resource.

FIG. 7 is a diagram illustrating a relationship between an instance created and an instance different when an instance of a community ontology class is created according to an embodiment of the present invention.

Specifically, FIG. 7 shows how the generated community instance can be interpreted based on the ontology data model when an instance belonging to the community ontology class is created. 7, the community instance includes a spatial instance (e.g., R, P, L) of a spatial ontology class, a time instance (e.g., ST, AT, D, P) of a time ontology class, Instance (e.g., Goal), and resource instance of the resource ontology class (e.g., R1). In addition, as illustrated in Fig. 7, in the case where a sensor is newly installed or a mounting position of the sensor is changed, a resource instance R1 for the sensor is generated. The generated resource instance R1 is a time instance of a time ontology class (e.g., ST, AT, D, P) and a target instance of a target ontology class (e.g., R, Yes, Goal). On the other hand, the community instance may be specified (written) through a semantic presentation language (e.g., OWL-DL).

Meanwhile, one community instance can be defined through a template API (Application Program Interface) or the like. Specifically, the attributes of the community ontology class in the ontology data model can be defined through a template API or the like. The ontology data model defined as shown in FIG. 3 to FIG. 7 is stored in the data storage processing unit 240. Specifically, the ontology data model can be stored in the data storage processing unit 240 as an RDF triple structure (Subject, Predicate, Object).

2. Community Instance  produce

The community instance definition module 210 allows the user or application to specify (create) the basic attribute information of the community for dynamic resource management. To this end, the community instance definition module 210 may include an interface. Specifically, the community instance definition module 210 is a template-based API (hereinafter, referred to as a 'template API') that allows a user or an application to input attribute information (eg, space, purpose, It may contain a program interface of a similar type to the API.

The Template API is an input interface provided to a user or application to define a community instance. Specifically, the template API can specify a resource for a community instance through logical logic (e.g., AND operation, OR operation, etc.) of the input information. The template API includes a Basic template and a Composite template.

The basic template defines the community instance through logical operations between input parameters, using the attributes of the community to be created as input parameters. For example, as shown in the following Equation 1, 'space' is used as space attribute information, 'sensor' is used as member attribute information, 'temperature' is used as objective attribute information, and 'From 1' to ' The community instance C1 can be defined as a sensor community that operates from 1:00 to 9:00 and measures the temperature of the charging area through the basic template.

The complex template defines the community instance through the operation between the input parameters, using the already created community instance as the input parameter. Specifically, the complex template can define a new community instance through operations between at least two community instances, or define a new community instance through an operation between attribute information of a community to be created and at least one community instance. For example, when the information indicating the community instance C1 and the 'humidity' as the object attribute information are input as parameters as shown in the following Equation 2, the community instance C2 is transmitted through the complex type template, "Sensor community that operates from 1 to 9 o'clock and measures the temperature and humidity of the Taejon area".

As another example, when the information indicating the community instance C1 and the information indicating the community instance C3 as the sensor community for measuring the humidity in the Seoul area are inputted as parameters as shown in the following Equation 3 , And the community instance C4 can be defined as a sensor community that measures the temperature of the Daejeon area and the humidity of the Seoul area through a hybrid template.

On the other hand, the attribute information input as a parameter of the template API includes local information (eg, city, county, district, coordinates, etc.), community goals (eg, temperature measurement, humidity measurement, pollution measurement, ), Or lifetime information of the community (e.g., when the community instance is created and destroyed, the service period of the resource, etc.).

Meanwhile, the community instance specified (created) by the community instance definition module 210 may include information for constructing a semantic relationship with an instance of another ontology class (e.g., resource instance, spatial instance, etc.) on the ontology. The information for constructing such a semantic relationship should be expressed in a specific rule or language that can be understood by a computer. The template API for defining a community instance has a structure in which a user or an application can specify (create) various attribute information .

3. Community Instance  management

The attribute information of the community input through the community instance definition module 210 can be expressed in a language (a semantic expression language such as OWL-DL) that specifies (creates) one community instance according to the designed logic. The ontology agent 220 converts the attribute information of the community received from the community instance definition module 210 according to the community ontology schema in a form that can be linked to the defined ontology data model and stores the data as a community instance of the community ontology class And stores it in the processing unit 240. The new community instance stored in the data storage processing unit 240 is associated with an instance of each ontology class through a relationship between pre-built ontology classes for dynamic resource management purposes. The ontology data speculation processor 230 may additionally deduce a semantic relationship between the new community instance stored in the data storage processor 240 and the instance of each ontology class.

The process of processing a community instance will be described in detail with reference to the embodiment shown in FIG. For example, in a case where a community instance (C1) is generated having a lifelong attribute of '1' to 9 ', a purpose attribute of' temperature ', and so on, A space instance corresponding to the attribute 'competition' is created. The generated spatial instance inherits the semantic relationship schema between the spatial ontology class model and the community ontology class model. Thus, the generated spatial instance has a semantic relationship with the community instance C1. Further, in addition to this semantic relationship, an additional semantic relationship between the community instance C1 and an instance of another ontology class may be inferred (or interpreted) by the ontology data inference processing unit 230. [ In this way, a semantic relationship structure between the community instance C1 and an instance of another ontology class can be created. On the other hand, when the resource management apparatus 200 manages the sensor resources located in the 'competition' area based on the attributes of the community related to the 'competition' area as a member of the community, the sensor located in the 'competition' There is a need. The resource management apparatus 200 grasps sensor instances related to 'competition' which is a local attribute of the community instance C1 generated among all resource instances belonging to the resource ontology class. To this end, the sensor instance, which is a resource instance of the resource ontology class, has location information (e.g., coordinates, etc.) in which it is installed as attribute information. With this relationship structure, the sensor instances associated with the community attribute 'action' of the community can be associated with the community instance C1 as a member of the created community instance C1. Likewise, the time instance corresponding to the lifetime attribute '1:00 to 9:00' and the target instance corresponding to the target attribute 'temperature' have a semantic relationship with the community instance C1. In particular, the purpose attribute of a community instance is an important attribute for determining the members of the community as well as the local attributes. For example, if the purpose attribute of the community instance C1 is for locating the temperature of the area, the resource management device 200 selects a sensor instance having the temperature measurement function among the sensor instances of the previously determined ' Instances can be grasped again as members of the community instance (C1).

4. Dynamic resource management mechanism in case of dynamic change of resources

A process of managing resources by the resource management apparatus 200 will be described with reference to FIGS. 8 to 10. FIG. 8 is a diagram illustrating an overall process of managing resources by the resource management apparatus 200 according to an embodiment of the present invention.

First, a case where the resource management apparatus 200 generates a new community instance (e.g., C1) will be briefly described. As described above, the community instance definition module 210 receives attribute information (e.g., a local attribute called 'competition', a desired attribute called 'temperature', a ' Quot; from 1 to 9 "). The community instance definition module 210 requests the ontology agent 220 to generate the community instance C1 corresponding to the input information. The ontology agent 220 creates the community instance C1 and stores it in the data storage processing unit 240. [

Hereinafter, the dynamic resource management mechanism of the resource management apparatus 200 will be described in the case where a resource dynamic change factor occurs. The resource management apparatus 200 determines, for a dynamic resource management mechanism, when a dynamic change factor of a resource occurs, which community instance corresponds to the changed resource. Specifically, the ontology data speculation processor 230 determines which community instance the resource in the changed state corresponds to. For example, the ontology data speculation processor 230 may perform a judgment operation when a service or an application using the community instance requests inference execution. Alternatively, the ontology data speculation processor 230 may perform a judgment operation when the ontology agent 220 that has reported the dynamic change factor of the resource requests the speculation execution.

For convenience of explanation, a dynamic resource management mechanism of the resource management apparatus 200 will be described taking as an example a case where a new sensor resource is installed or a position of a sensor installed in the existing sensor is changed. In the case where one sensor, which is represented by 'first coordinate value' and the object information 'temperature', is installed in the USN, the resource management processor 250 calculates a first coordinate value, which is attribute information of the installed sensor, Etc. can be automatically reported from the installed sensor or can be requested and reported to the installed sensor. The resource management processor 250 transmits the information reported from the installed sensor to the ontology agent 200. The ontology agent 220 generates a resource instance R2 corresponding to the received information using the resource ontology class and stores the resource instance R2 in the data storage processing unit 230. [

When the position of the installed sensor is changed, the sensor can automatically report the changed position information to the resource management processor 250 or report it in response to the request of the resource management processor 250. [ The resource management processor 250 transmits information (changed position information) reported from the sensor to the ontology agent 220. [ The ontology agent 220 updates the resource instance for the sensor based on the received information. Specifically, the ontology agent 220 can delete a resource instance for the corresponding sensor at the pre-change position, which is stored in the data storage processing unit 240. The ontology agent 220 may generate a resource instance for the corresponding sensor at the changed location and store the resource instance in the data storage processing unit 240.

As a result, the resource storage unit 240 newly stores a resource instance (e.g., R2) of the resource ontology class based on the ontology data model. On the other hand, for dynamic resource management, each ontology class (eg, a time ontology class, a resource ontology class, a community ontology class, a space ontology class, etc.) already has a semantic relationship with each other according to schema by ontology data modeling. For example, the semantic relationship between the resource ontology class and the community ontology class and the semantic relationship between the resource ontology class and the space ontology class are already stored. On the other hand, if necessary for dynamic resource management, a new ontology class may be defined, or predefined ontology classes may be connected and used.

Meanwhile, '3. According to the dynamic resource management mechanism of the resource management apparatus 200, as described in the section " Community Instance Management ", the position coordinate value of the resource instance (e.g., R2) for the newly installed or repositioned sensor Value) can be associated with the POI attribute or Region attribute of the spatial ontology class. Accordingly, the position coordinate value of the updated resource instance (e.g., R2) can be converted into POI attribute information or region attribute information and interpreted. This interpretation process is performed by the ontology data speculation processor 230. The reasoning point of the ontology data speculation processor 230 can be designed to be suitable for providing a smooth service. Specifically, the ontology data speculation processor 230 determines whether the resource instance (e.g., R2) is stored in the data storage processor 230, when the community instance is stored (e.g., C1) , And can perform inferences.

As a result, the relationship between the resource instance (e.g., R2) and the community instance (e.g., C1) is expressed by the information structure connected to each other by the ontology data speculation processor 230, Associated with the ontology class, it is associated with the related local information. Through the inference function based on the information structure connected to the linked information structure on the ontology, the resource management apparatus 200 can acquire a newly created resource instance (e.g., a resource instance for a new sensor, or a resource instance Can automatically determine which community instance among the currently existing community instances. Accordingly, a method for generating a community instance having various attributes according to an embodiment of the present invention, a method for inferring a resource instance related to a generated community instance, and a method for inferring a community instance corresponding to the generated resource instance , A dynamic resource management mechanism based on a community having various properties can be efficiently supported. 9 and 10, the dynamic resource management mechanism according to the embodiment of the present invention will be described in more detail.

9 is a diagram illustrating a process in which the resource management apparatus 200 according to an embodiment of the present invention creates and manages a community instance.

The community instance definition module 210 receives the attribute information of the community to be created through the input interface and requests the ontology agent 220 to create a community instance corresponding to the input information (S110).

The ontology agent 220 creates a community instance based on the community ontology schema, and stores the community instance in the data storage processing unit 240 (S120).

The ontology data speculation processor 230 analyzes the semantic relationship between the community instance generated in step S120 and instances of other ontology classes stored in the data storage processor 240 (e.g., resource instance, spatial instance, time instance, (S130). Specifically, the ontology data speculation processor 230 may perform the process of S130 in response to the speculation execution request from the ontology agent 220. [ Alternatively, the ontology data processing unit 230 may perform step S130 in response to the inference execution request from the service or the application.

The state management processor 260 receives the inferred result from the ontology data inference processor 230 in step S130 and manages the received result (S140). Specifically, the state management processor 260 can manage information on an instance (e.g., a resource instance, a space instance, a time instance, a target instance, and the like) of another ontology class related to the community instance.

In response to the community information inquiry request from the service or application, the state management processor 260 provides information on the community to the service or the application (S150). Here, the information provided to the service or the application may include information on resources related to the community, or service information (e.g., measured temperature information, etc.) provided by the community.

On the other hand, if the resource management apparatus 200 is designed not to include the state management processing unit 260, steps 140 and 150 are omitted. Specifically, when the resource management apparatus 200 does not include the state management processing unit 260, the ontology agent 220 responds to the community information inquiry request from the service or application, Application.

10 is a diagram illustrating a process in which the resource management apparatus 200 according to the embodiment of the present invention creates and manages a resource instance.

When a new resource is installed or a previously installed resource is moved, the resource reports its attribute information (e.g., ID, location information, purpose, etc.) to the resource management processing unit 250 (S210). In Fig. 10, for convenience of explanation, it is assumed that resources are sensors.

The resource management processor 250 receives the attribute information of the sensor from the sensor (S220). The resource management processor 250 registers the sensor that transmitted the attribute information. The resource management processor 250 transmits the received attribute information of the sensor to the ontology agent 220 (S230).

The ontology agent 220 converts the attribute information of the received sensor into resource instance data according to the resource ontology schema stored in the data storage processing unit 240. Then, the ontology agent 220 stores the converted resource instance data in the data storage processing unit 240 (S240).

The ontology data speculation processor 230 analyzes the semantic relation between the resource instance generated in step S240 and the instance of another ontology class stored in the data storage processor 240 (e.g., a community instance, a spatial instance, a time instance, a target instance, (S250). Specifically, the ontology data speculation processor 230 may perform the inference process from the ontology agent 220 or the inference execution request from the service (or application), and perform the process of step S250. Through the process of S250, the ontology data speculation processor 230 can determine which community instance among the community instances in which the generated resource instance is stored.

The state management processor 260 receives the inferred result from the ontology data inference processor 230 in step S250 and manages the received result in step S260. Specifically, the state management processor 260 can manage information on an instance (e.g., a resource instance, a space instance, a time instance, a target instance, and the like) of another ontology class related to the community instance.

In response to the community information inquiry request from the service or application, the state management processor 260 provides information on the community to the service or the application (S260).

On the other hand, if the resource management apparatus 200 is designed not to include the state management processing unit 260, steps S250 and S260 are omitted. Specifically, when the resource management apparatus 200 does not include the state management processing unit 260, the ontology agent 220 responds to the community information inquiry request from the service or application, Application.

5. Connection with service

According to the embodiment of the present invention, even if a dynamic change of resources occurs such as a new installation of a sensor or a movement of a sensor, an application receiving a service through a community needs to directly manage the dynamic change none. Specifically, the dynamic resource management mechanism according to the embodiment of the present invention can automatically reflect factors of dynamic change of resources in a community instance associated with each service. Eventually, the service or application that wants to use the community does not need to manage the dynamic changes in resources occurring within each community. Therefore, as shown in FIG. 1, a service or an application can manage only the state of a community, and thus can utilize resources efficiently.

Meanwhile, for more efficient, community-based dynamic resource management, the resource management apparatus 200 may include the state management processing unit 260 as described above. 1, a service or an application may not acquire the update information of the community from the ontology data storage processing unit 240 or the ontology agent 220, and may not acquire the update information of the community from the state management processing unit 260 or the state manager 20 ). ≪ / RTI > In other words, the performance of the service can be improved through the state management processor 260 serving as a cache memory.

Specifically, in FIG. 1, the state manager 20 continuously receives change information of a resource belonging to a community from the dynamic resource management layer L30, and can efficiently transmit the reported information to a service or an application. In this regard, the state manager 20 or the state management processor 260 may be designed to have a structure and a capability to inquire community related information more quickly and accurately than the data storage processor 240. The data storage processor 240 stores data of the RDF triple format and stores various semantic relations for processing the semantic data. Thus, the inquiry of the data set having a specific semantic relationship is performed every time in the data storage processor 240 The performance of the resource management apparatus 200 may be degraded. Therefore, when a data set having a specific semantic relation for community configuration is determined, the resource management apparatus 200 can construct a database for more efficiently inquiring the data set. The state manager 20 or the state management processor 260 can manage the database.

Meanwhile, although the case where the embodiment of the present invention manages resources of the USN has been described, it is only an example. Embodiments of the present invention can be applied not only to a system using a sensor but also to all systems using a resource.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, It belongs to the scope of right.

Claims (20)

A method for a resource management device to manage resources,
Creating a first instance for a first community using a first ontology class for the community that includes at least one resource as a member according to a goal;
Generating a second instance of the first resource using a second ontology class related to the resource; And
Estimating a relationship between the first instance and the second instance
The resource management method comprising: The method according to claim 1,
The step of creating the first instance
Receiving attribute information of the first community; And
And generating the first instance through a first template using the attribute information as an input parameter
Resource management method. The method according to claim 1,
The step of creating the first instance
Receiving first information representing a third instance for a second community already generated; And
And generating the first instance through a first template using the first information as an input parameter
Resource management method. 3. The method of claim 2,
The first resource is a first sensor in the sensor network
Resource management method. 5. The method of claim 4,
The attribute information
Wherein the first community includes at least one of information on members of the first community, information on an area of the first community, information on a lifetime of the first community, and information on the purpose of the first community
Resource management method. 6. The method of claim 5,
The estimating step
Estimating a relationship between the first instance and the second instance using a semantic relation between the first ontology class and the second ontology class,
Resource management method. The method according to claim 6,
Creating a third instance of the first space using a third ontology class for the space; And
Further comprising estimating a relationship between the first instance and the third instance
Resource management method. 8. The method of claim 7,
Generating a fourth instance for a first time using a fourth ontology class on time; And
Further comprising estimating a relationship between the first instance and the fourth instance
Resource management method. 9. The method of claim 8,
Creating a fifth instance for a first purpose using a fifth ontology class related to the purpose of the service; And
Further comprising estimating a relationship between the first instance and the fifth instance
Resource management method. 10. The method of claim 9,
Further comprising estimating a relationship between at least one of the third instance, the fourth instance, and the fifth instance and the second instance
Resource management method. 11. The method of claim 10,
Creating and storing a sixth instance of the second sensor using the second ontology class when a second sensor is added to the sensor network;
Estimating a relationship between each of the instances of the first ontology class and the sixth instance and determining an instance corresponding to the sixth instance out of the instances of the first ontology class
Resource management method. 11. The method of claim 10,
Deleting the second instance when the position of the first sensor is changed;
Generating a sixth instance for the first sensor at the changed location using the second ontology class; And
Estimating a relationship between each of the instances of the first ontology class and the sixth instance and determining an instance corresponding to the sixth instance out of the instances of the first ontology class
Resource management method. The method according to claim 1,
Transmitting first information about each instance having a semantic relationship with the first instance to a state manager managing the state of the first community; And
Further comprising providing the first information to the application via the status manager in response to an application request
Resource management method. A method for a resource management device to manage resources,
Creating a first instance for a first community using a first ontology class representing a community that includes at least one resource as a member according to the purpose;
Creating a second instance of the first resource using a second ontology class representing the resource if the first resource is added; And
Estimating a relationship between the first instance and the second instance
The resource management method comprising: 15. The method of claim 14,
If the location of the first resource is changed, deleting the second instance;
Generating a third instance of the first resource at the changed location using the second ontology class; And
Estimating a relationship between the third instance and the first instance
Further comprising the steps of: 15. The method of claim 14,
The attribute information of the first instance is
At least one of information on a member of the first community, information on an area of the first community, information on a lifetime of the first community, and information on the purpose of the first community,
The estimating step
Estimating a first semantic relationship between at least one third instance having a semantic relationship with the first instance and the second instance; And
Determining whether the second instance corresponds to a member of the first instance based on the first semantic relationship,
The third instance
An instance of a third ontology class representing a time, an instance of a fourth ontology class representing a time, and an instance of a fifth ontology class representing a purpose of a service
Resource management method. A resource management apparatus for managing resources,
A first instance creation processor for creating a first instance for a first community using a first ontology class representing a community including at least one resource as a member according to the purpose;
A second instance creation processing unit for creating a second instance of the first resource using a second ontology class representing a resource when the first resource is added; And
And an estimation processor for estimating a semantic relation between the first instance and the second instance
Resource management device. 18. The method of claim 17,
Wherein the second instance creation processing unit updates the second instance based on the changed attribute information when the attribute information of the first resource is changed,
Wherein the estimation processing unit estimates a semantic relation between the updated second instance and the first instance
Resource management device. 18. The method of claim 17,
The estimation processing unit
Estimating a first semantic relationship between at least one third instance having a semantic relationship with the first instance and the second instance and determining whether the second instance corresponds to a member of the first instance based on the first semantic relationship And,
The third instance
An instance of a third ontology class representing a time, an instance of a fourth ontology class representing a time, and an instance of a fifth ontology class representing a purpose of a service
Resource management device. 18. The method of claim 17,
Further comprising a management processor for managing first information for each instance having a semantic relation with the first instance and providing the first information to the application in response to a request of the application
Resource management device.

Images