KR20070010230A - Intelligent home network service system using ontology - Google Patents

Abstract

An intelligent home network service system based on ontology is provided to clarify relations among entities, such as a user, a device, a service, and space, and examine relations between context information of various forms collected from plural sensors, thereby clearly reasoning information necessary for providing a service which the user requests in a ubiquitous home network and providing an intelligent home network service without having ambiguity. A system for providing an intelligent home network service based on ontology comprises the followings: a user ontology which stores an ID(Identification) of a user and obtains location information of the user by referring to location sensor ontology; the location sensor ontology which stores information about a location, where a location sensor is installed, and stores location information of a measured object; device ontology which includes an ID of a device and location information where the device is installed; space ontology which obtains information about the location sensor and the device which are installed within the space by referring to the location sensor ontology and the device ontology; and service ontology which configures and manages contents of the home network service.

Description

Intelligent Home Network Service System Using Ontology {Intelligent Home Network Service System using Ontology}

1 is a view showing the configuration of an overall ontology model for a home network service according to an embodiment of the present invention;

2 is a view showing the configuration of an ontology model for storing information associated with a user using a home network service according to an embodiment of the present invention;

3 is a diagram illustrating a configuration of an ontology model associated with an apparatus for home network service according to an embodiment of the present invention;

4 is a diagram illustrating a configuration of an ontology model for configuring and managing contents of a home network service according to an embodiment of the present invention;

FIG. 5 is a diagram illustrating a configuration of an ontology model for storing and managing a matter of a policy of a home network service according to an embodiment of the present invention; FIG.

6 is a diagram illustrating a configuration of an ontology model for providing a home network service corresponding to a specific event according to an embodiment of the present invention;

7 is a diagram illustrating a configuration of an ontology model for managing time-related information occurring in a home network according to an embodiment of the present invention;

8 is a diagram illustrating a configuration of an ontology model for storing and managing place-related information in a home network service according to an embodiment of the present invention;

9 is a view showing the configuration of an ontology model for storing, managing, and managing user behavior patterns according to an embodiment of the present invention;

10 is a view showing the configuration of an ontology model for providing a knowledge service according to a user's schedule according to an embodiment of the present invention;

FIG. 11 is a diagram illustrating a configuration of an ontology model for dynamically configuring a service by a user according to an embodiment of the present invention.

* Explanation of symbols for the main parts of the drawings

200: PersonRelative 300: EntityRelative

400: Service 500: Policy

600: Even Relative 700: Time

800: Space 900: UserActivity

1000: Schedule 1100: UserComandRelative

The present invention relates to a home network service system, and more particularly, to a system for providing an intelligent home network service based on an ontology.

Home network technology, a leader in digital convergence, has recently emerged as a cutting-edge item in the telecommunications and electronics industries. The home network is a key component of the 'digital home', the future home environment where the information in the home is connected to the network and service is provided regardless of the device, time and place.

However, a realistic model for providing knowledge services using such home network technology is very weak. First, CoBrA (Context Broker Architecture) has been developed as a prior study for efficiently managing and sharing various knowledge or information and making context inference. The CoBrA was developed for a broker agent that manages a context sharing model for all computing entities existing in the intelligent space. In addition, SOUPA (Standard Ontology for Ubiquitous and Pervasive Applications) has been developed with the aim of a common ontology supporting ubiquitous computing environments.

However, there are many problems in applying such existing models to the actual home network service. First of all, there is no solution in case of a conflict between multiple users for a single device, which implies the risk of service failure. In the case of providing multiple services, there is a similar risk in the event of a conflict between services.

In addition, there is no practical model to represent the actual device does not provide the scalability for the increasingly diversified digital home appliances, and there is no model for configuring a dynamic service according to the user's request.

The present invention has been proposed to solve the above problems, by clearly defining the resources necessary for providing a home network service as an ontology, interworking with each other, and suggesting a priority policy model, providing scalability to various services and providing services. The purpose of the present invention is to provide an intelligent home network service system that can solve the problem of collision between users.

Other objects and advantages of the present invention can be understood by the following description, and will be more clearly understood by the embodiments of the present invention. Also, it will be readily appreciated that the objects and advantages of the present invention may be realized by the means and combinations thereof indicated in the claims.

According to an aspect of the present invention, there is provided a system for providing an intelligent home network service based on an ontology, the system comprising: a user ontology storing an ID of a user and obtaining location information of the user by referring to a location sensor ontology; A position sensor ontology storing an ID of a position sensor, position information on which the position sensor is installed, and position information of the object to be measured; A device ontology including an ID of the device and location information on which the device is installed; A space ontology that stores a name of a space constituting a home network and obtains information about the position sensor and the device installed in the space by referring to the position sensor ontology and the device ontology; And a task ontology including information about a service user, a name of a service task, information on a space in which the task is serviced, and information on a subtask referenced in providing a service, and information on a device related to an operation to be performed to provide a service. And a service ontology having a subtask ontology containing information on the operation contents of the device as a subclass. The present invention may further include a device access level ontology for storing and managing information on a device access level as to whether the device can be used, wherein the device ontology refers to the device access level ontology. It may be characterized in that to obtain information about the availability of the. The method may further include a privacy ontology for storing and managing information on the degree of disclosure of personal information, wherein the user ontology obtains information on whether to disclose personal information by referring to the privacy ontology. can do. Meanwhile, the present invention further includes a user priority ontology for storing and managing information on the priority of a plurality of users, wherein the user ontology is provided between the services provided to the plurality of users by referring to the user priority ontology. It may be characterized by acquiring user priority information for solving a conflict problem occurring in the. The method may further include a task priority ontology for storing and managing information on a priority of a plurality of tasks, wherein the task ontology resolves a conflict problem between a plurality of tasks by referring to the task priority ontology. It may be characterized in that the task priority information for obtaining.

The above-described contents of the present invention will become more apparent through the following detailed description with reference to the accompanying drawings, and thus, those skilled in the art to which the present invention pertains may easily implement the technical idea of the present invention. will be. In addition, in describing the present invention, when it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a view showing the configuration of an overall ontology model for home network service according to an embodiment of the present invention. The arrow in FIG. 1 shows an example of the relationship through the reference of each ontology. However, since it is difficult to display all of the relationships between the ontology, FIG. 1 shows only a part of the relationship, and specific interworking between the ontology will be described with reference to other drawings in which the configuration of each ontology is shown in more detail. do.

First, as shown in FIG. 1, the home network service model according to the present invention is' PersonRelative ',' EntityRelative ',' Service ',' Policy ',' EvenRelative ',' Time ',' Space ',' UserActivity ',' Schedule 'and' UserCommandRelative 'include ontology classes, and the ontology can interoperate to provide intelligent services.

The ontology class has an ontology subclass, and each class is composed of various properties. A property refers to a relationship between objects or data values of an object, and is composed of two types: an object property referring to an object of a class, and a data type property having a specific data value.

The ontology model for home network service according to the present invention provides a knowledgeable home network service by clearly defining a relationship between a device, a user, and an object such as a space required in a home using the above components. In particular, the object property (ObjectProperty) includes information about which class of objects it refers to, the relationship between each object in the ontology model for home network services according to the present invention through the object property (ObjectProperty) Can be clearly defined.

Hereinafter, each of the ontology classes constituting the ontology model for home network service according to the present invention and the relationship between the classes will be described with reference to the accompanying drawings.

2 is a diagram illustrating a configuration of an ontology model for storing information associated with a user using a home network service according to an embodiment of the present invention.

As shown in Figure 2, the ontology model 'PersonRelative (200)' 'Person (210)', 'Profile (220)', 'Contact (230)', 'Health (240)', 'Nick (250)' , Ontologies of 'Group 260' and 'Interest 270' are subclasses.

First, 'Person (210)' is an ontology for comprehensively including information about a user, and includes 'personID', 'locationInfo', 'hasProfile', 'contact', 'health', 'hasNick', 'belongTo', Contains properties of 'preference', 'interest', 'deviceAccessLevel', 'privacyLevel', and 'userPriority'. Only 'personID' for storing a unique identification number (ID) assigned to a user among the properties corresponds to a data type property, and all other properties correspond to object properties. First, 'locationInfo' refers to a 'LocationSensor 315' ontology that has location sensor information to obtain location information of a user. 'hasProfile' refers to the 'Profile (220)' ontology containing personally identifiable information, 'contact' refers to the 'Contact (230)' ontology containing information about the user's contact, and 'health' refers to the user's health status. 'Health (240)' ontology with information on 'hasNick' means 'Nick (250)' ontology with information about the user's nickname, and 'belongTo' means 'Group' with information about the group to which the user belongs (260) 'ontology', 'preference' is 'Task (420)' ontology which has information about user's preference environment, 'interest' is 'Interest (270)' which has information about user's interest or interest See Ontology. Meanwhile, 'privacyLevel' refers to an 'PrivacyLevel 514' ontology that includes information on the degree of disclosure of user information as an ObjectProperty that determines whether a user's personal profile is disclosed. In addition, 'deviceAccessLevel' is an object property (ObjectProperty) for determining a degree of accessibility to a device, and refers to 'DeviceAccessLevel 512' which is an ontology including information on a level accessible to the device. In addition, 'userPriority' is an object property (ObjectProperty) for determining a user priority, and refers to 'UserPriority 522', which is an ontology including information about priority between users.

'Profile 220' is an ontology for storing basic information about a user and includes properties of 'privacyLevel', 'name', 'age', 'birth', and 'job'. 'privacyLevel' is an object property for determining whether a user's personal profile is disclosed or not, and refers to a 'privacylevel 514' ontology that includes information on the degree of privacy disclosure. Meanwhile, 'name', 'age', 'birth', and 'job' are data type properties (DataTypeProperty), which store information on a user's name, age, date of birth, and occupation, respectively.

'Contact 230' is an ontology for storing a user's contact information, and includes a datatype property of 'cellularPhoneNum' for storing the user's mobile phone number and 'email' for storing the user's email address. .

'Health (240)' is an ontology for storing information about the user's health status, and includes 'privacyLevel', 'disease', 'bloodType', 'heartbeat', 'height', 'weight', and 'bodyTemperature' Contains properties. 'privacyLevel' is an object property that determines whether or not the health status information of a user is disclosed. The 'privacylevel' refers to a 'privacylevel 514' ontology that includes information on the degree of privacy disclosure. Meanwhile, 'disease', 'bloodType', 'heartBeat', 'height', 'weight', and 'bodyTemperature' are data type properties, each of which has a disease, a blood type, and a heart rate of the user. Information about related attributes, height, weight and body temperature is stored.

'Nick (250)' is an ontology for storing information about a user's nickname. The nickname, which is a data type property for storing the user's nickname, and the nickname (name) Contains an object property called calledBy to indicate whether it is called. The calledBy stores the user calling the corresponding nickname (name) as a nickname, and refers back to the ontology 'Nick 250' to know the user calling the nickname. Therefore, the ontology 'Nick (250)' is separated and defined differently according to the human relationship, and by using a passive (transive) technique to support the classification and storage in bidirectional titles rather than unidirectional.

'Group 260' is an ontology for storing information about a group to which a user belongs. The data type property 'groupName' for storing a group's name and an object for storing information for users belonging to a group Contains the property 'hasMember'. The object property 'hasMember' refers to the ontology 'Person 210' when it is necessary to know more information about users belonging to the group. That is, the 'Group 260' is an ontology model for a name for two or more members, and supports easy user classification and integrated management through grouping according to attributes.

'Interest 270' is an ontology for information about a user's interest or interest, and includes an object property 'privacyLevel' and a data type property 'field' and 'detailedField'. 'privacyLevel' is an object property that determines whether a user's personal interest or interest is disclosed. The 'privacylevel' refers to a 'privacylevel 514' ontology that includes information on the degree of privacy disclosure. On the other hand, 'field' and 'detailedField', which are data type properties (DataTypeProperty), store user's interests and detailed interests, respectively. For example, when the user's field of interest is 'movie', the detail field of the user may be 'action', 'drama', 'thriller' and the like.

The ontology model 'PersonRelative (200)' for storing information related to a user configured as described above includes an a property object 'privacyLevel' in an ontology for storing information related to an individual's personal information to prevent leakage of personal information. In addition, the ontology of the group to which each individual belongs may be defined as a subclass to facilitate service management for multiple users. In addition, it is possible to provide a knowledge service according to a title by defining an ontology for a nickname between each user or a group collectively for two or more users.

3 is a diagram illustrating a configuration of an ontology model associated with a device for home network service according to an embodiment of the present invention.

As shown in FIG. 3, the ontology model 'EntityRelative (300)' subclasses ontology of 'Sensor 310', 'Device 320', 'Exclusive' 330 ', and' Actuator 340 '. Have

First, 'Sensor 310' is an ontology for collecting information through a sensor, and may include ontology about various sensors such as a position sensor, a temperature sensor, a light sensor, and the like as a subclass. In the embodiment of the present invention will be described taking 'LocationSensor 315' for collecting location information as an example. As shown in Figure 3, 'LocationSensor 315' is an ontology for collecting and managing location information through a location sensor, 'sensorID' for storing the sensor unique identification number, 'coordinate' for storing the sensor location, It includes a data type property of 'sensingDataType' for storing the data type of information collected through the sensor, 'sensing Time' for storing the information collection time, and 'location_Status' for storing location status information. In addition, ontology (EtcSensor) for collecting and managing information through other sensors are also composed of data type properties such as 'LocationSensor 315'.

'Device 320' is an ontology for storing and managing information related to a device providing a home network service, and includes' deviceID ',' deviceName ',' actuator ',' deviceDefault ',' owner ',' hasSensor ',' alternativeDevice ',' deviceAccessLevel ',' coordinate ',' remainBattery ', and' isWork 'as properties. 'deviceID' and 'deviceName' are data type properties (DataTypeProperty) for storing a unique identification number (ID) and a name of a device, respectively. 'actuaor' is an object property (ObjectProperty) for storing properties of a device, and when information on the property of the device is needed, it refers to the 'Actuator 340' ontology. 'deviceDefault' and 'owner' are object properties to store information about the default value and owner of the device after the service is finished, respectively. 'hasSensor' is an object property for storing information about sensors mounted inside the device. If necessary, 'hasSensor' refers to the ontology of the corresponding 'Sensor'. In addition, 'deviceAccessLevel' is an ontology for storing information on whether the user can use the device. When the user intends to use the device, the 'deviceAccessLevel' (512) 'ontology is referred to. 'AlternativeDevice' is an object property for storing information about a device that can be replaced when the corresponding device is unavailable, and may refer to the corresponding 'Device 320' ontology. Meanwhile, 'coordinate', 'remainBattery' and 'isWork' are data type properties (DataTypeProperty) for storing information about device position coordinates, battery level and device availability.

'Exclusive 330' is an ontology for defining devices that should not be operated at the same time, and includes a data type property 'device' that stores information about devices that should not be operated at the same time. Meanwhile, the 'device' may refer to the 'Device 320' ontology having information on a corresponding device, if necessary.

'Actuator 340' is an ontology for defining the properties of devices used for home network services. It includes 'OperationLevel (341)', 'Temperature (342)', 'Light (343)' and 'Communication (344)' Subclasses of 'Player (345)', 'OpenClose (346)', 'Display (347)', 'Sound (348)', 'Power (349)', 'Broadcast (350)', etc. . 'OperationLevel 341' has a data type property 'operationlevel' that contains information about an operation level (ex. Strong, medium, weak). 'Temperature 342' has data type properties of 'degree' and 'humidity' in order to store information on attributes related to temperature and attributes related to humidity. 'Light (343)' contains data type properties 'bight' and 'color' for storing brightness and color, and 'Player (345)' shows track information and current player status (ex. Play, FFD, RWD). Data type properties 'track' and 'playerStatus' for storing (such as, Stop, Pause, etc.). Meanwhile, 'Display (347)' includes data type properties such as 'mode', 'brightness' 'controlColor', 'contrass', and 'menuDisplayTime' to store information such as screen mode, brightness color, and contrasts. do. In addition, the 'Sound (348)' ontology includes 'volume' for adjusting the volume, 'soundType' for storing sound expression methods such as wav or mid, rock, classic, or surround. Contains datatype properties such as 'modeEQ' for selecting the mode. In addition, the 'Power 349' includes a 'powerStatus' data type property for storing an on-off operation state and a power state, and the 'Broadcast 350' includes a broadcaster and a channel for selecting a channel. Includes 'station' and 'channel' datatype properties.

The ontology 'EntityRelative 300' configured as described above may store and manage information on various devices for providing a home network service. More specifically, first, the 'Sensor 310' defines all the ontology-related ontology in the same format so that it is easy to add a necessary sensor later to provide a scalability to configure a faulty network service, while the 'Device (320)' In order to utilize sensor information in various devices, the object property 'hasSensor' that can refer to the 'Sensor 310' is included in the. In addition, 'Device 320' provides a basis for inferring alternative services when it is impossible to provide necessary services by designating a substitute device through 'alternativeDevice' when the corresponding device is not available. 330 'can prevent a service collision by defining a device that cannot be used at the same time. In addition, by defining the attributes of the devices used for home network services in the 'Actuator (340)', each device (device) to selectively select a corresponding actuator (actuator), the device (device) used for home network services Can provide scalability suitable for ubiquitous environments.

4 is a diagram illustrating a configuration of an ontology model for configuring and managing contents of a home network service according to an embodiment of the present invention.

As shown in Figure 4, 'Service (400)' is an ontology model for configuring and managing the content of the home network service, 'Session (410)', 'Task (420)', 'SubTask (430), And an ontology of 'Operation 440' as a subclass.

Looking specifically at the subclass of 'Service (400)', first, 'Session (410)' is an ontology for storing and managing matters related to session use, and 'person' and corresponding information for storing session user information. An object property includes 'hasTask' for storing information about a service operating in a session (hereinafter, interpreted in the same meaning as a task in the ontology structure according to the present invention). If the 'person' needs detailed information about the session user, the 'person' may refer to the 'Person (210)' ontology, and the 'hasTask' refers to the 'Task (430)' ontology for obtaining information of the corresponding service (task). Reference may be made.

'Task 420' is an ontology for storing and managing matters related to services (tasks) and includes 'taskName', 'hasSubTask', 'timeInterval', 'space', and 'taskPriority' as properties. 'taskName' is a data type property (DataTypeProperty) for storing the name of a task (service). 'hasSubTask' is an object property (ObjectProperty) for designating a sub task constituting the task. When the information of the sub task is needed, the hasSubTask may refer to the ontology 'SubTask 430' of the sub task. 'timeInterval' and 'space' are object properties for storing information about when and where the task is served.The 'TimeInterval (710)' and 'Space (800)' ontology are used to obtain the specific information. See. 'taskPriority' refers to the 'TaskPriority 524' ontology that defines the priority between tasks as an ObjectProperty for specifying the priority of the task.

'SubTask 430' is an ontology for storing and managing matters related to subtasks constituting a task, and has an ontology of 'SerchSubTask 432' and 'DeviceSubTask 434' as a subclass. 'SerchSubTask (432)' is an ontology for storing and managing matters about search subtasks. It is a data type property 'searchWord' for storing words to be searched and an object property for storing time to search. It includes 'timeInterval', which can refer to 'TimeInterval (710)', and 'order', which is a data type property that stores information about search order. Meanwhile, 'DeviceSubTask 434' is an ontology for storing information related to a device to perform a subtask, and includes 'device', 'hasOperation', 'timeInterval', and 'order' as properties. 'device' is an object property for designating a target device of a subtask related to the operation of the device, and when information on the target device is needed, the 'device 320' ontology is referred to. 'hasOperation' is an object property for storing the operation information of the device, and may refer to the 'Operation 440' ontology for the corresponding operation information. 'timeInterval' may refer to 'TimeInterval 710' as an object property for specifying an operation time of the device. On the other hand, 'order' is a data type property for storing information about the order of execution between subtasks.

'Operation 440' is an ontology for storing and managing information related to the operation of the device, 'targetProperty' for storing information about a desired operation property of the device, and 'propertyValue for storing a value for the device's operation. Contains' as a data property.

Service (400), which is an ontology model for configuring and managing the contents of the home network service configured as described above, can provide various services by clearly defining service units such as sessions, tasks, and subtasks. Provides scalability In addition, when there is a user's request, a service set may be configured through a combination of the above-described service units, thereby providing a base for providing various services according to the user's request. In addition, by including the user information in the 'Session 410', it is possible to resolve the userPriority by referring to the 'priority' of the 'Person 210' when a collision between users occurs, and the 'Task 420'. In addition, by including information on the task priority (taskPriority), it is possible to resolve by the priority (TaskPriority) even when a conflict between tasks. On the other hand, the configuration of the ontology as described above may provide a basis for providing a default service according to the user preset content or user's behavior pattern in the future, and the convenience and convenience in future addition and management of dynamic services Provide ease.

FIG. 5 is a diagram illustrating a configuration of an ontology model for storing and managing a matter of a policy of a home network service according to an embodiment of the present invention.

The home network service policy according to the present invention is largely composed of a 'level policy' for managing a degree of access to a device or personal information and a 'priority policy' for resolving a conflict between a user or a task. Accordingly, the ontology 'Policy (500)', which stores and manages the matters related to the policy of the home network service, is the ontology of the level policy (Level 510) and the ontology of the priority policy as shown in FIG. Include 'Priority (520)' as a subclass.

'Level (510)' is an ontology 'DeviceAccessLevel (512)' which manages matters related to access to the device and 'Only Privacy Level (514)' which is an ontology which manages matters about access to personal information. Included in a subclass. The 'DeviceAccessLevel 512' includes 'level' as a data type property for storing the level information on the level of access to the device, and the 'PrivacyLevel 514' indicates the level information on the level of access to personal information. Include 'level' as a datatype property for storing.

'Priority (520)' is an ontology 'UserPriority (522)' to suggest a solution when a conflict occurs between users, and 'TaskPriority (524)' an ontology to suggest a solution when a conflict occurs between tasks. Include 'as a subclass. 'UserPriority (522)' includes data type property 'level' for storing information about priority among users, and 'TaskPriority (524)' stores information about priority between tasks. The datatype property 'level' is included.

The 'Policy (500)' ontology, configured as described above, can define the 'DeviceAccessLevel (512)' ontology as a subclass and not only control whether the user is allowed to access the device, but also to particularly dangerous devices. More stringent access can support the construction of risk management policies in home network services. In addition, the subclass 'PrivacyLevel 514' can support a privacy policy by providing a configuration that can specify a user's information protection level. In addition, 'UserPriority 522' and 'TaskPriority 524' support to configure an optimal service according to a specified priority level when a conflict occurs between users or tasks.

6 is a diagram illustrating a configuration of an ontology model for providing a home network service corresponding to a specific event according to an embodiment of the present invention.

'EventRelative (600)' is an ontology model that defines a service corresponding to a specific event, and has 'Event (610)' and 'EventTerms (620)' as subclasses.

'Event 610' is an ontology that defines an event occurrence condition and a service to be provided when the condition occurs, 'terms' for storing information on the event occurrence condition and provided when the event occurrence condition is established. 'Task' for storing information about service task to be performed is included as an object property. 'terms' refers to 'EventTerms 620' for detailed information on event occurrence conditions. In addition, 'task' refers to the 'Task 420' ontology to obtain information about a service task to provide when an event occurrence condition is met.

'EventTerms 620' is an ontology defining matters related to event conditions, and includes' timeInterval ',' person ',' space ', device', 'operation', and 'order' as properties. 'timeInterval' is an object property (ObjectProperty) for storing information about the time of occurrence of an event, and can refer to 'TimeInterval (710)', and is an object property for storing information on the subject of the 'person' event. Person 210 may be referred to, and 'spacce' may refer to 'Space 800' as a property for storing information on an event occurrence location. In addition, 'device' may refer to 'Device 320' as an object property for storing information on an operation device, and 'operation' is an object property for storing information on operation information of a device. (440) '. On the other hand, 'order' is a data type property (DataTypeProperty) for storing information about the order of event conditions.

The ontology 'EventRelative (600)' having the above configuration includes 'EventTerms (620)' as an ontology for event conditions for operating a task and 'Event (610)' as an ontology for the resultant service. Based on the history stored by the (900) 'model, the service operation conditions and service contents are learned and the knowledge service is dynamically provided accordingly. Meanwhile, the object property 'terms' of the 'Event (610)' class may refer to a plurality of 'EventTerms 620', and accordingly, a 'task' refers to a plurality of 'Tasks 420' to refer to multiple services. Can provide. In addition, 'EventTerms 620' includes 'order' as a data type property, so that an order of event conditions for which a service is provided can also be specified.

7 is a diagram illustrating a configuration of an ontology model for managing time-related information occurring in a home network according to an embodiment of the present invention.

'Time 700' is an ontology model for managing time-related information. As shown in FIG. 7, 'Time 700' has subclasses 'TimeInterval 710', 'TimeRelation 720' and 'TimeWordMean 730'.

First, 'TimeInterval (710)' is an ontology model for supporting the time of a service that must be provided repeatedly, 'from' which means start time (from), and 'to' which means end time (to). For example, the data type property has 'at' for a specific time and 'serviceInterval' for a service interval such as once or daily. The 'TimeInterval 710' supports inferring and recording the actual time based on the 'TimeRelation 720'.

In addition, 'TimeRelation 720' is an ontology model for specifying the time interval or time interval of the requested time, 'before' meaning a previous time (before), 'at' meaning a specific time, and a later time. It has 'after' which means ',' which means 'during' which means time interval, 'from' which means start time, and 'to' which means end time.

Lastly, 'TimeWordMean' (730) is an ontology model that enables semantic reasoning of words related to time. 'WordWord' is used to define words related to time frequently used in real life. It has 'before', 'at' defining a specific time, 'after' defining a later time, and 'serviceInterval' defining a service interval. The 'TimeWordMean 730' provides clarity of a time relationship, thereby supporting storage and management of time-related terms that users can use on a daily basis. In addition, each time-related term is composed of an instance of a single class, thereby providing ease and convenience in managing such time as adding or deleting the term-related term.

8 is a diagram illustrating a configuration of an ontology model for storing and managing place-related information in a home network service according to an embodiment of the present invention.

'Space 800' is an ontology model for managing a home network space. As shown in FIG. 8, 'Space 800' has an 'HomeSpace 810' ontology as a subclass and ontology for managing space other than home (for example, For example, 'OfficeSpace 820') for managing an office space may be an additional subclass.

'HomeSpace 810' has a data type property 'spaceName' for storing a place name such as a living room or a bedroom and 'owner', 'location', 'etcSensor', and 'device' as object properties. 'owner' is an object property for storing information about an owner of a corresponding place, and may refer to 'Person 210' to obtain information about the owner. 'locationSensor' and 'etcSensor' are object properties for storing information about location sensors or other sensors in the place. In order to obtain information about sensors, 'LocationSensor (315)' and other ontology of location sensors are acquired. You can refer to 'EtcSensor', the ontology for the sensor. 'device' is an object property for storing information about a device in a corresponding place, and when it is desired to obtain detailed information about the device, it may refer to 'Device 320'. In addition, ontologies (eg, 'OfficeSpace 820') for managing a space other than home may also take the same structure as the 'HomeSpace 810'.

Ontology 'Space 800' of the configuration as described above provides the optimal home network service based on the location information by including information about various sensors and devices, including the name of the internal space of the house and the sensor located in the space Support it. In other words, it supports the user's location tracking through linkage with the location sensor. In addition, it is possible to configure a service optimized for a user by interworking with various sensors such as a temperature or humidity sensor, and supports to efficiently provide the optimized service by interworking with devices located in each space. . On the other hand, the 'Space 800' includes an ontology for managing a space other than the home as an additional subclass to provide expandability that can be linked to the external space.

9 is a diagram showing the configuration of an ontology model for storing, managing, and managing user behavior patterns according to an embodiment of the present invention.

'UserActivity (900)' is an ontology model for storing a user's behavior as a history. That is, the 'UserActivity 900' is an ontology model for sequentially recording and storing the user's actions, and includes 'person', 'timeInterval', 'device', 'operation', 'contents', and 'contentsInfo'. Contains a property.

The 'person' is an object property for storing information on the acting subject. When the detailed information on the acting subject is required, the 'person' is referred to as 'Person 210'. 'timeInterval' refers to 'TimeInterval 710' as an object property for storing information about an active time. 'device' may refer to 'Device 320' as an object property for storing information on the device operated, and 'operation' as an object property for storing information on the operation history of the operated device. (440) '. In addition, 'contents' is an object property for storing a user's preferred service contents such as music, movie, or preferred site, and 'contentsInfo' is a data type property for storing detailed information of the service. Meanwhile, in the construction of the overall ontology model according to the present invention, 'Contents' may be set as a separate ontology for managing contents related to various contents, and the object property 'contents' may cause the separate ontology 'Contents'. Can be configured to reference.

'UserActivity (900)' of the configuration as described above, by storing the user's behavior as a history (history) by patterning the user's behavior based on the behavior stored in the history (history), learning according to the user's behavior pattern Dynamic configuration of home network services is supported. That is, the intelligent home according to the user pattern is configured by configuring the event conditions and the service provided when the condition occurs in the 'EventRelative 600' according to the user's behavior pattern recognized through the 'UserActivity 900'. It can provide network services. Meanwhile, the behavior pattern includes not only a person, a time, a place, a device and an operation, but also a pattern of information related to content to be used.

FIG. 10 is a diagram illustrating a configuration of an ontology model for providing a knowledge service according to a user schedule according to an embodiment of the present invention.

'Schedule (1000)' is an ontology model for storing and managing the user's schedule matters. The 'who', 'title', 'where', 'withWhom', 'timeInterval', and 'briefingContents' are properties. Include. 'who' is an object property for storing information about the schedule subject. If more information about the schedule subject is required, 'who' may refer to 'Person (210)'. In addition, the remaining 'title', 'where', 'withWhom', timeInterval ', and' briefingContents' are datatype properties, respectively, which store information about the schedule title, place to perform, participant, schedule time, and the content you want to brief on. do.

The ontology model 'Schedule 1000' configured as described above manages a user's schedule and enables a knowledgeable home network service such as a briefing. Meanwhile, the ontology model 'Schedule 1000' may be configured as a subclass of 'Person 210' to receive a service.

FIG. 11 is a diagram illustrating a configuration of an ontology model for dynamically configuring a service by a user according to an embodiment of the present invention.

'UserCommandRelative' 1100 is an ontology model for dynamically configuring a service requested by a user, and includes 'UserCommand 1110', 'ServiceTimeRelative 1120', and 'TaskType 1130' as subclasses.

First, 'UserCommand' 1110 is an ontology for storing information about a user command, and has' personID ',' macID ', IPAdd', 'requestTime', 'hasServiceTime', and 'hasTaskType' as properties. 'personID' is a datatype property for storing a unique identification number assigned to a person, and 'macID' and 'IPAdd' are datatype properties for storing a MAC Add and an IP Add of a user PDA. . In addition, 'requestTime' is a data type property for storing information about the time when a user requests a service. Meanwhile, 'hasServiceTime' refers to 'ServiceTimeRelative 1120' as an object property for storing information on a service execution time when a user reserves a time to perform a request service. In addition, 'hasTaskType' refers to 'TaskType 1130' as an object property for storing information on the type of service requested by a user.

'ServiceTimeRelative (1120)' is an ontology for managing the information related to the time when the user schedules the request service. The 'Time' defining the start time and the 'to' defining the ending time and the requesting service are performed. It has a data type property of after that defines the previous service.

'TaskType (1130)' is an ontology of the type of service, 'DeviceTask (1132)' that defines the related service on the device, 'RequestInformation (1134)' and the specific service that defines the information request service Subclass 'BatchTask (1136)' which defines the information about. First, 'DeviceTask 1132' is a data type property for storing a device's unique identification number and device name when a user directly selects a device and requests a service. The device task 1132 includes deviceID and deviceName. It stores information about the operation of the device and, if necessary, includes 'hasOperation' as an object property referencing 'Operation 440'. In addition, 'RequestInformation (1134)' includes 'queryLiteral' for storing actual words of information to be searched for, 'nodeType' for specifying a search type such as news search or encyclopedia search, and 'nodeType' for more detailed classification. Include a 'catagory' as a datatype property to store additional information about it. Finally, 'BatchTask 1136' has a 'taskName' and a 'parameter' as data type properties for storing a service task name when a user requests a specific service and necessary information when the task is requested.

Hereinafter, a home network service provided by learning a user pattern as an embodiment of the present invention will be described. For convenience of explanation, suppose that User B uses the treadmill for one hour in the living room at 8 o'clock every evening and at the same time watches a certain TV channel.

First, 'UserActivity' provides a basis for supporting a certain pattern learning by storing a user's behavior pattern as a history. 'EventRelative' creates an Event object according to the learned pattern. That is, every night at 8 pm (timeInterval), user B person, treadmill and TV (device), etc. are registered as an event value of 'EventTerms', and 'TV power on' and 'preferred channel switching' Etc. are registered as a task 'Task' corresponding to the above conditions. In addition, an event object composed of object properties 'terms' and 'task' referring to the 'EventTerms' and 'Task' is created. When the event object is created as described above, a service task corresponding to the event condition defined by 'EventTerms' is executed accordingly.

In the above embodiment, the service in the case of having one event condition has been described as an example, but there may be a plurality of event conditions. In this case, an order of conditions may be specified.

Hereinafter, as an embodiment of the present invention, an indoor environment management service considering the priority of a user registered as an object of 'Person' class will be described.

First, when T quantity enters the living room, T's preferred environment can be inferred through 'Task' referenced by 'preference' of 'Person' class for T quantity, and T's preferred indoor environment service can be provided. have. At this time, if the amount of T is converted to 'Cold Setting', 'UserCommand' object is created. In addition, 'hasTaskTpe', an object property of 'UserCommand', searches for an object matching 'taskName' among 'Task' classes by referring to 'taskName' of 'BatchTask' among subclasses of 'TaskType' class. The retrieved 'Task' uses the objects of the 'SubTask' referenced by the object property 'hasSubTask' to configure the service to be provided in the winding amount T environment.

On the other hand, when the Q group enters the living room in the situation where the service is provided, the T amount of cold setting environment service and the Q group preference environment service will cause a conflict. In this case, the conflict problem is solved by inferring the superiority relationship based on the priority of the two services using the reference object of the task property 'taskPriority'.

Also, when Q group passes through the living room and enters Q's room, the object property 'locationInfo' of 'Person' class and 'locationSensor' of object 'Space' class refer to the object of class 'LocationSensor'. Recognizing the movement of the military, the Q military's room will provide the Q military preference environment. In other words, the location sensor tracks which space the user is in by using the relation of which space it belongs to, and uses the device property 'device' of the 'Space' class of the space to find an object of the 'Device' class. By referring to it, it is inferred which device in the space should be operated among the devices in the home. Then, using the devices located in the Q group room, the service for providing the Q group's preferred environment is dynamically constructed using the object of 'SubTask'.

As described above, the method of the present invention may be implemented as a program and stored in a recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.) in a computer-readable form. Since this process can be easily implemented by those skilled in the art will not be described in more detail.

The present invention described above is capable of various substitutions, modifications, and changes without departing from the technical spirit of the present invention for those skilled in the art to which the present invention pertains. It is not limited by the drawings.

As described above, the present invention has the effect of clearly inferring information necessary for providing a service requested by a user in a ubiquitous home network by specifying a relationship between entities such as a user, a device, a service, and a space. . In addition, it is possible to provide an intelligent home network service without ambiguity by identifying relationships between various types of context information collected from a plurality of sensors. On the other hand, it is possible to dynamically configure and provide an intelligent service suitable for a user by analyzing the trend of context information that recognizes a user's behavior pattern.

In addition, the present invention provides a solution based on a priority policy when a conflict occurs between a plurality of users or a plurality of services provided. Another advantage of the present invention is that a privacy level policy prepares for the risk of leakage of personal information, and device access can also be used to prevent accidents that may occur in the use of dangerous devices.

The present invention based on the ontology as described above has the effect of providing scalability as an overall ubiquitous network service model including a home network.

Claims (17)

In the system for providing intelligent home network service based on ontology, A user ontology that stores a user ID and obtains location information of the user by referring to the position sensor ontology; A position sensor ontology storing an ID of a position sensor, position information on which the position sensor is installed, and position information of the object to be measured; A device ontology including an ID of a device and location information on which the device is installed; A space ontology that stores a name of a space constituting a home network and obtains information about the position sensor and the device installed in the space by referring to the position sensor ontology and the device ontology; And a service ontology for organizing and managing contents of a home network service. The service ontology, A task ontology including information about a service user, a name of a service task, a space on which the task is serviced, and information on a subtask referenced in providing a service; And a service ontology having, as a subclass, a subtask ontology including information on a device related to an operation to be performed for providing a service and information on an operation content of the device. Intelligent home network service system, characterized in that. The method of claim 1, The user ontology, Including information about the user's profile, contacts, groups to which they belong, preferences, and health status Intelligent home network service system. The method of claim 1, It further includes a sensor ontology for storing and managing matters related to the sensor, The sensor ontology, The position sensor ontology and A plurality of sensor ontology for storing the ID of the sensor, the location information on which the sensor is installed, and the sensor data about the object to be measured. Including as a subclass Intelligent home network service system. The method of claim 1, Further comprising an actuator ontology for classifying attributes of the device and storing and managing information on the classified operational attributes, The device ontology, Obtaining information on the operation attribute of the device by referring to the actuator ontology Intelligent home network service system. The method of claim 4, wherein The actuator ontology, A display ontology for storing and managing display information, a temperature ontology for storing and managing temperature information, an operating level ontology for managing operating level information, a brightness ontology for storing brightness information, and a broadcast for storing broadcast information Having a plurality of ontology subclasses classified according to the operational attributes containing the ontology Intelligent home network service system, characterized in that. The method of claim 1, The space ontology, Subclassing a plurality of spatial ontology for storing and managing information about a plurality of spaces for providing home network services Intelligent home network service system, characterized in that. The method of claim 1, The service ontology, It additionally includes an operation ontology that stores information on the operation attributes of the device required to provide a service as a subclass. The subtask ontology, Obtaining information about the operation contents of the device by referring to the operation ontology Intelligent home network service system, characterized in that. The method of claim 1, Further comprising a device access level ontology for storing and managing information about device access levels for device availability, The device ontology, Acquiring information on the availability of the device by referring to the device access level ontology Intelligent home network service system, characterized in that. The method of claim 1, It further includes a privacy ontology for storing and managing information on the degree of disclosure of personal information, The user ontology Obtaining information on whether or not to disclose personal information by referring to the privacy ontology Intelligent home network service system characterized by The method of claim 1, Further comprising a user priority ontology for storing and managing information about the priority between a plurality of users, The user ontology Acquiring user priority information for resolving a conflict problem between services provided to a plurality of users by referring to the user priority ontology; Intelligent home network service system, characterized in that. The method of claim 1, It further comprises a task priority ontology for storing and managing information about the priority between a plurality of tasks, The task ontology Acquiring task priority information for solving a conflict problem occurring between a plurality of tasks by referring to the task priority ontology Intelligent home network service system, characterized in that. The method of claim 1, It further includes a time ontology defining what is related to time occurring within the home network, The time ontology includes a time interval ontology as a subclass to support a service time that must be repeatedly provided. Intelligent home network service system. The method of claim 12, And a user behavior ontology for storing a user behavior including a user, an activity time, a device which has been operated, and operation information of the device as a history. Constructing contents of a service to be provided to the user by referring to a user ontology, a time ontology, a device ontology, an operation ontology associated with information constituting a pattern of behavior of the user patterned in the user behavior ontology Intelligent home network service system, characterized in that. The method according to claim 12 or 13, An event condition ontology that stores information about an event occurrence condition including an event condition time, a subject, and a location; And An event task ontology that stores information about a service task provided when a condition stored in the event condition ontology is satisfied Intelligent home network service system, characterized in that it further comprises. The method of claim 14, The event condition ontology, Intelligent home network service system, characterized in that for additionally storing information about the sequence of event occurrence conditions. The method of claim 1, User command ontology for storing information about a user's request service task, including user ID, request time, and request service task Intelligent home network service system, characterized in that it further comprises. The method of claim 16, Providing a service requested by a user by searching for a task ontology matching a name of a specific service task by the user request and referring to a task ontology whose name is matched Intelligent home network service system, characterized in that.

Images