KR20090053179A - Service controlling apparatus and method for context-aware knowledge service - Google Patents

Abstract

The present invention relates to a service control apparatus and method for context-aware knowledge service, and a computer-readable recording medium recording a program for realizing the method. The present invention relates to a home network service based on a ubiquitous environment. Service scheduling and service policy management for service execution, service control device for monitoring the service status of user's behavior, and a program for realizing the method to provide a context-adaptive customized service to the user. It is intended to provide a computer readable recording medium.

To this end, the present invention provides a service control method of a service control device, the method comprising: defining a priority between users or services, and setting a policy so that a service can be executed according to service priority when various services are executed simultaneously; When requesting a service, referring to the policy to determine whether the service is registered and whether the service can be provided to the user at the corresponding location; As a result of the determination, if the priority of the currently requested service is higher than a service already provided or an appropriate service registered to the user, registering the service with the service scheduler; Stopping a current service and storing a service state in a service data table when a service having a higher priority than a service currently being executed by the service scheduler is executed; Resuming the service by calling a service state stored in the service data table when the service is executed; And releasing a service registered in the service scheduler when the service ends.

Context Awareness, Knowledge Service, Service Controller, Scheduler, Policy, Ontology

Description

Service control apparatus and method for context-aware knowledge service

The present invention relates to a service control apparatus and method for context-aware knowledge service, and a computer-readable recording medium recording a program for realizing the method. More specifically, the present invention relates to a ubiquitous environment. Service scheduling and service policy management for service execution, service control device for monitoring the service status of user's behavior, and the method to provide a context-adaptive and customized service to a user in a home network service, and realizing the method The present invention relates to a computer-readable recording medium having recorded thereon a program.

In the future, applications and services in the ubiquitous era will have the characteristics that smart objects with computing and communication capabilities can recognize and adapt to dynamic environment changes, that is, context-aware characteristics. Context is almost all of the information available at the time the user interacts. In addition, the context information includes information that can be detected by the application as part of the application operating environment. This generally includes the location, identification, activity, status, etc. of people, groups, and objects. The context-aware service recognizes through the collection and exchange of such situation information, and provides the appropriate service to the situation through the process of interpretation and reasoning.

In a ubiquitous environment, context-aware services will be the largest and most important subset of the entire ubiquitous set of services. In addition, context-aware services can be applied to all areas of society such as home, medical care, education, disaster and relief, and shopping, and will have a great impact on society.

In particular, in order to provide advanced customized services in a ubiquitous environment, an intelligent and adaptive computing technology is needed. In addition, various devices should be able to exchange and share information with each other, and whether it is a situation to provide services by organically combining physical space, time, network environment, and various devices to provide an optimal service to a user. Aware) technology.

In the ubiquitous environment, the user's movement is considered in detail, and the service required by the user must be provided in an intelligently necessary situation. To do this, it is necessary to recognize the movement of users and to manage user, environment, and service information in a policy manner. As the service required by a user increases, problems such as service collision and security in a space among multiple users increase due to the expansion of the space. In order to solve this problem, it is necessary to define a policy for such a service and a user and a space to solve a conflict and provide security of a service.

Until now, the development of modules for simple service processing has been made on the results of inference, but only one user is managed without being considered for the increase of service requests. There is a limit to the application in an environment multihome network. Therefore, introduction of a service controller (service control device of the present invention) is required for service extension for multiple users.

In this case, the required service controller can efficiently provide a service by preventing service collision for multiple users in consideration of service scheduling, priority, intelligence level, and the like. In addition, for application in a multi-home network, a multi-threaded method is used to manage resources for all services, implement each service in a hierarchical structure, and efficiently handle multiple service requests of multiple users. Since it is required, it can be manufactured in a bundle form on the OSGi (Open Service Gateway Initiative) framework to enable efficient operation of the service.

It monitors the status of the service currently used by the user, and if the service is used in multiple ways, various execution policies of the service [policy set differently according to the user, Priority, Device Access Level, Security Level (Security Level, Intelligence Level, etc.) to temporarily set the service execution rank to enable distributed processing of services, and to provide service levels and various services when one user is provided with multiple services. An object of the present invention is to provide a service desired by a user without determining a policy and providing a duplicate.

Accordingly, the present invention provides a service scheduling apparatus for service execution and service policy management, a service control apparatus for monitoring a service state of a user's behavior in order to provide a context-adaptive customized service to a user in a home network service based on a ubiquitous environment; It is an object of the present invention and to provide a computer-readable recording medium having recorded thereon a program for realizing the method.

The objects of the present invention are not limited to the above-mentioned objects, and other objects and advantages of the present invention which are not mentioned above 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.

In order to achieve the above object, the present invention provides a service control apparatus of a context-aware knowledge service system, comprising: data filtering means for classifying and filtering input data, converting output data into a format suitable for a module to be transmitted; Service data management means for loading and managing information on a service provided to a user from an ontology; Policy means for defining priorities between users or services, and providing a policy for executing services according to service priorities when various services are executed simultaneously; And a service scheduling means for preventing a collision due to simultaneous execution between services in a service area through service scheduling with reference to the policy.

Meanwhile, the present invention provides a service control method of a service control apparatus, the method comprising: defining priorities between users or services, and setting a policy so that services can be executed according to service priorities when various services are executed at the same time; When requesting a service, referring to the policy to determine whether the service is registered and whether the service can be provided to the user at the corresponding location; As a result of the determination, if the priority of the currently requested service is higher than a service already provided or an appropriate service registered to the user, registering the service with the service scheduler; Stopping a current service and storing a service state in a service data table when a service having a higher priority than a service currently being executed by the service scheduler is executed; Resuming the service by calling a service state stored in the service data table when the service is executed; And releasing the service registered in the service scheduler when the service ends.

On the other hand, the present invention, for the context-aware knowledge service, to define a priority between users or services in the service control device having a processor, so that the service can be executed according to the service priority when the various services are executed at the same time Setting a policy; A function of determining whether to register a service and whether the service can be provided to a corresponding user at a corresponding location when referring to the policy; As a result of the determination, if a priority of a currently requested service is higher than a service already provided or a proper service registered to a corresponding user, registering a corresponding service in a service scheduler; A function of stopping a current service and storing a service state in a service data table when a service having a higher priority than a service currently being executed by the service scheduler is executed; When executing a service, calling a service state stored in the service data table to restart the corresponding service; And a computer readable recording medium having recorded thereon a program for realizing a function of releasing a service registered in the service scheduler when the service ends.

As described above, the present invention can increase efficiency by managing and processing multiple operations through multi-threading for input processing, and speeds up processing by scheduling and filtering services based on service policies, and services in a multi-home network situation. There is an effect that can provide the function efficiently. In this case, there is an advantage in that distributed processing of the service is possible through service scheduling.

The above objects, features, and advantages will become more apparent from the detailed description given hereinafter with reference to the accompanying drawings, and accordingly, those skilled in the art to which the present invention pertains may share the technical idea of the present invention. It will be easy to implement. 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.

In order to provide advanced customized services in the ubiquitous environment, intelligent and adaptive computing technology is needed. In addition, various devices should be able to exchange and share information with each other, and there should be situational technology to provide services by organically combining physical space, time, network environment, and various devices in order to provide an optimal service to users. do.

The context-aware knowledge service system is a middleware bundle based on the Open Service Gateway Initiative (OSGi) that provides the following functions (ie, Query Manager, Reasoning Engine). , An interface controller, a service controller, a session manager, a context manager, etc., to enable such knowledge services.

The context-aware knowledge service system may summarize, analyze, process, and process real-time information and context collected from various sensors in the house to provide information through various input / output methods and control devices. I / O control function].

In addition, the context-aware knowledge service system is a query for inferring an appropriate service according to context information (user's location information input from a sensor, environment information such as temperature and humidity of a home, illumination, and user profile information such as a user schedule). ) [Query Formatting Function].

In addition, the context-aware knowledge service system enables to provide a seamless service by storing a service state when a user moves and changes a service [service management function].

In addition, the context aware knowledge service system enables organic data construction and management through the relationship between user profile and context information (Ontology function, which is an object-oriented database).

The middleware configuration of the context aware knowledge service system is shown in FIG. 1.

As shown in FIG. 1, the knowledge service system in which the present invention is applied is configured in a bundle form based on a service platform conforming to the OSGi standard.

The OSGi framework runs on the Java Virtual Machine (JVM), making it portable and extensible, so it can be used on most systems with a JVM regardless of hardware (H / W) or operating system (OS). It provides a multi-threading technique and provides an interface to easily manage the installation and update of bundles. Middleware bundles (Reasoning Engine, Interface Controller, Session Manager, Query Manager, Context Manager, Context) that make up the context-aware knowledge service system on the OSGi framework Manager, Service Controller], and the bundle enables various knowledge services to be provided through a multi-modal interface (MMI).

Then, look at the characteristics of the knowledge service system whether the present invention is applied as follows.

Context-aware knowledge service system [OSGi-based system architecture] is a bundle-type middleware development using OSGi-based service platform, which can be easily linked with other services and middleware based on OSGi, and easy to distribute and manage services using middleware. Do. In addition, each bundle can be configured independently to provide excellent bundle recyclability. This feature can be used in various ubiquitous environment support knowledge information service technology, and in particular, it can be used for providing information through car navigation and vehicle condition checking service in conjunction with a telematics service bundle.

In addition, context-aware knowledge service system [meaning-based contextual information expression technology (Ontology)] uses ontology, which is a semantic / knowledge-based expression system, without context ambiguity (Physical, Environmental, Informational, Social, Application, System). ), Using the Web Ontology Language (OWL) and Resource Description Framework (RDF), the Semantic Web standard framework for context-awareness based on ontology. In addition, in order to effectively process a large amount of contexts in the middleware level, not only inferencing of context information based on ontology but also mining technology is applied to the user context through the user interface. Information can be effectively transmitted and operated. In addition, the size, shape, and configuration of the information content can be reconfigured according to the user device, the network, and the context to provide a new type of information.

In addition, the context-aware knowledge service system [knowledge information personalization technology] is equipped with a profiling technology through efficient context information (Context) management for the personalization of knowledge information services in the ubiquitous environment. That is, each situation information has access authority and priority such as security level, intelligence level, policy level, and device access level. It evaluates and provides the level of information that can be accessed by each, and it is configured to dynamically change by recognizing dynamic user behavior or information pattern.

The structure of the middleware bundles of the situation recognition knowledge service system having the above characteristics is shown in FIG. 2.

The roles of each middleware bundle constituting the context aware knowledge service system are as follows.

The inference engine 30 extracts and manages information from an ontology managing information of a complex concept of a user and an environment, a service, and a space-time, and transmits the information to a service bundle. In addition, when using services of multiple homes and multiple users, the situation is inferred based on the user's propensity, profile, and pattern, and the priority between users or services when a new service request or service command follows a user's movement. It checks whether the service is provided by the application of the policy, and transmits the device control signal and service information according to the provision level.

The interface / service controller 50 is provided with various types of context information (control signals (device control, service mode, system settings, etc.) input from the MMI and service request signals (information request) and sensors in the home. Transmits the input sensor signal into a common format and transmits it to another bundle. In addition, the sensor performs a classification and management with the basic data according to the classification and user input for each sensor input. In addition, it performs a function of encoding / decoding the data in the input / output situation into information in the form of RDF / XML. In addition, when the input / output information is in a form that is not suitable for processing by the middleware or is incorrectly transmitted, the corresponding information is filtered. In addition, when several signals are transmitted at the same time, it performs scheduling function for data flow and transmission to a service or another bundle according to basic context information about each input. In addition, it performs service management and scheduling function by configuring a service session for each location.

The service controller 50 performs a role as an interface and a service management function. Hereinafter, an interface function of a service controller will be described as being performed by an interface controller. However, it should be noted that the interface controller and the service controller can be configured as one module.

The session manager 40 performs a function of providing a seamless service by creating, deleting, and managing user-specific sessions (status information on a registration service and a service in use). In addition, it performs a log-on / off management function for each user and a service application status according to the user location. In addition, it performs a function of managing user session information based on the service status monitoring for each user and the policy defined in the inference engine 30. In addition, it performs a function of checking the service registration / cancellation and service provision for a specific user. In addition, to provide a seamless service, when the user terminates the service, the user stores state information and checks whether the service is restarted.

The query manager 20 stores and manages context information for multi-user processing. In addition, it saves and manages the inference result and retrieves metadata in the DBMS. Also, it manages various types of metadata information, manages intermediate data for operation, and manages various metadata of the knowledge repository 10. In addition, the inference engine 30 performs a function of generating and managing an appropriate type of query for information and services required by the inference engine 30. Also, it extracts semantic information based on rule and relationship and converts extracted semantic information into instance based on situation information ontology.

The Knowledge Repository 10 stores and manages user and various device related information, information for providing a knowledge-based service to a user, time information for providing a service, and the like, required for a home network environment, It manages ontology-based user context and service information describing the relationship required for each function.

When the user uses the service, the operation of the middleware bundle is shown in FIG. 3.

The input to the knowledge service system can be divided into the following two cases.

The first is a case where a user terminal such as a PDA or a mobile phone is directly input through a home pad, a wall pad, or the internet (direct input through a user terminal). In this case, the service that the user wants to receive through the service UI (User Interface) of the user terminal (service control such as device control, meal mode, sleep mode, system setting (priority, device access level, security level, Policy setting such as intelligent level), or the like, or to obtain certain information (information request for environment information, schedules of other users, etc.).

The second is when the context transmitted from the sensor constructed in the service environment is automatically transmitted to the knowledge service system (automatic input through sensor input). For example, in a case where a service environment is established, a sensor located for each spot senses a user's location or periodically transmits environmental information (temperature, humidity, and illuminance).

When there are two types of inputs (direct input through a user terminal, Homepad / Wallpad, Internet, and automatic input from a sensor), data processing of each middleware bundle for providing a knowledge base service is as follows. Hereinafter, the processing according to the command input, the information request, and the sensor input will be described separately.

First, the data processing process for command input is as follows.

First, when a command (device control, service mode (eg, meal mode, sleep mode, etc.), system setting, etc.) is input through a user terminal, a Homepad / Wallpad, or the Internet, the input data (Command) is converted into XML. The data is transmitted to a socket of an interface controller 50 and parsed into data available inside the system through an XML parser.

Thereafter, the interface controller 50 analyzes the data (command) parsed through the interfacing engine and classifies the data according to the type of service (device control, service mode, system setting, etc.). At this time, the classified data is transmitted to the corresponding bundle according to the service type (device control, service mode, system setting, etc.). That is, in case of device control, data [user ID and device name] is transmitted to the inference engine 30, and in case of system setting, user ID and policy set by the user [Priority, device Access level (Device Access Level), Security Level (Security Level), Intelligence Level (Intelligence Level) are transmitted to the inference engine 30, in the case of the service mode, data [User ID, Service Name (Service) Name) and Service Status] are transmitted to the service controller 50.

Therefore, in the classification result, in the case of device control, in order to consider the policy aspect (user priority and permission, etc.), the reasoning engine 30 transmits data (that is, user ID, device name ( Device Name)] is transmitted. In addition, in the case of system setting, the user ID and the policy set by the user (Priority, Device Access Level, Security Level, Intelligence Level) are the inference engine (30). Is sent).

As a result of the classification, in the service mode, data [User ID, Service Name, Service Status] is transmitted to the service controller 50, and the service controller 50 is transmitted. Analyzes information about services At this time, the service controller 50 checks whether service provision is appropriate for registration, configuration, and scheduling of the corresponding service. When it is determined whether the service is appropriate or not, the service controller 50 transmits a user ID (UserID) and service information (service name and service status) to the session manager 40, and the session manager 40. ) Creates a session for each user, determines the service state and whether to provide it, and transmits it to the inference engine 30.

Specifically, in the case of the service mode, the service controller 50 performs service analysis through a service management function. In this case, the service analysis means determining whether the service is registered and whether the service can be provided to the user at the corresponding location. If another service with a higher priority at the location is already running or the service is not authorized to the user, the service request is aborted at this stage and a message is not provided to the user. However, if the priority of the currently requested service is higher than the service already being provided or the appropriate service registered to the user, the service controller 50 registers the service in the scheduler. The service scheduler manages service information for each location and user to prevent service conflicts when multiple services are simultaneously executed at one location or services provided to a user are duplicated. Accordingly, the service controller 50 calls a policy (priority, device access level, security level, intelligent level) to prevent the occurrence of a collision in the service spot to the inference engine 30 to perform service scheduling. do.

Then, when the service is determined by the service scheduler, information for providing the service (user ID, service information (service name and status)) is transmitted to the session manager 40, and the session manager 40 is a user. Creates a separate session, determines the service state and whether to provide it to the inference engine 30. Here, the session manager 40 receives a user ID, a service name, and a service state from the service controller 50 as variable values in determining the service state and whether to provide the service, parses the input information, and then stores the user ID. It is used as a keyword to check the state of the session. That is, information about whether there is a service used by the corresponding user and what the final state of the service is is obtained from the session data table of the knowledge repository 10 through the query manager 20.

Meanwhile, the inference engine 30 transmits data to the query manager 20 to apply the corresponding policy after reviewing the input service and information. Then, the query manager 20 generates an appropriate query, transmits the generated query to the ontology of the knowledge repository 10 to obtain information [role of the situation information manager], and then the inference engine. Transfer to 30. After that, when the device to be serviced and controlled is determined, the inference engine 30 transmits the corresponding data (device control information) to the device controller and transmits the processing result to the interface controller 50 to provide a service to the user. Do it. At this time, if device control is necessary, the device is controlled by transmitting a device control list and a property for the corresponding service to the device controller.

That is, when the command is a service mode input, the inference engine 30 determines whether the input is appropriate and performs an operation for providing a corresponding service. That is, when a user ID, a service name, and a service state are input from the session manager 40 as variable values, the information is input through the query manager 20 in the rule engine. (Ontology), and transmits a query to the updated ontology to collect the device to be controlled and information to be displayed for the service (the inference engine 30 through the query manager 20) Update the ontology and collect information from the updated ontology]. At this time, the collected information is filtered using various policies (security level, device access level, priority, intelligent level), and based on such policy information (security level, device access level, priority, intelligent level). The service and information are determined and parsed and delivered to values available at the device controller and interface controller 50.

In addition, when the command is a device control input, the inference engine 30 determines whether the input is appropriate and performs an operation for providing a corresponding service. That is, the inference engine 30 receives a user ID and a device name from the interface controller 50, passes the input information (user ID, device name) to the query manager 20, and sends a query manager ( 20) generates a query based on this, requests the ontology the device access level (gets the user access level of the user based on the user ID), returns the result and passes it to the inference engine 30, the inference engine (30) ) Determines whether the device is controlled based on the collected information (user device access level in the policy), and if available, transmits a control command (on / off) to the device controller and sends the processing result to the interface controller 50. Inform the user. At this time, if device control is necessary, the device is controlled by transmitting a device control list and a property for the corresponding service to the device controller.

In addition, when the command is a system setting input, the inference engine 30 receives a user ID and a policy input by the user (priority, device access level, security level, intelligent level) from the interface controller 50, and executes a query manager ( 20), the query manager 20 receives the user ID and the policy set by the user (priority, device access level, security level, intelligent level) from the inference engine 30 based on the corresponding user (user ID) To the ontology. The inference engine 30 notifies the user of the processing result (ontology update result) through the interface controller 50.

Now, let's look at the data processing process for the information request.

When there is a request for information (eg, home environment information, schedule, profile, service level, security level, etc.) through a user terminal, a homepad / wallpad, or the Internet, an information request message converted into XML from the user terminal is similarly displayed. Is sent. Thereafter, the data converted into XML (information request message) is transmitted to the socket of the interface controller 50, and parsed into data that can be used in the system through the XML parser.

Subsequently, the interface controller 50 analyzes the parsed data [user ID, query name, information name] through the interfacing engine (recognizes that it is an information request in this case) and a reasoning engine. (30).

Thereafter, the inference engine 30 reviews the input information [user ID, query name, information name] [reviews whether the input is appropriate according to security level and device access level], and then queries to apply the corresponding policy. Data (information request message) is sent to the query manager 20, and the query manager 20 generates an appropriate query and transmits the generated query to the ontology of the knowledge repository 10. After obtaining the information, it is transmitted back to the inference engine (30). Thereafter, the information to be provided by the system is transmitted to the user through the interface controller 50. That is, in the case of an information request, the query manager 20 obtains the information requested by the user requesting from the inference engine 30 from the ontology and transmits the information to the inference engine 30. Then, the inference engine 30 collects the information requested by the user, determines the information according to the policy (security level, priority), and transmits the information to the user through the interface controller 50.

Finally, we will look at the data processing process for the sensor input.

When context information is input from the sensor, the context-aware knowledge service system transmits the user's location when the user's location is transmitted from the sensor to provide a service according to the user's location [in this case, when the sensor's location coordinates are input. Sensor location coordinates] According to the service area (Spot), the user's preferred environment (temperature, humidity, lighting, movies, music, etc. desired by the user) is provided.

Specifically, when a user is detected by a sensor located in each service area (for example, a living room, a room, a front door, etc.) (that is, when the user's location changes or the state of the service area changes), the corresponding sensor The sensor transmits sensor information (position coordinate information of the sensor) to a listener of the interface controller 50. Then, if the data transmitted from the sensor (sensor information) is duplicated or damaged, the interface controller 50 filters the filtered data, and then transmits the data [user ID, sensor data to the API of the inference engine 30]. , User location].

Thereafter, the inference engine 30 determines the service to be provided in the corresponding area (eg, living room, home room, entrance hall, etc.) with reference to the sensor information. At this time, the service is determined by referring to the ontology of the Knowledge Repository 10. That is, the inference engine 30 sends the data to the query manager 20 to review the input sensor information and apply the corresponding policy, and the query manager 20 generates an appropriate query. After that, the generated query is transmitted to the ontology of the knowledge repository 10 to obtain information, and then transmitted to the inference engine 30 again. Therefore, the inference engine 30 infers the location of the user based on the location of the sensor, and collects controller information on the service to be provided to the user. Subsequently, when the service is determined, the inference engine 30 transmits the corresponding service information [user ID, service name (preferred environment service), service status value (including user's location)] to the service controller 50. send.

In this case, the information input to the inference engine 30 is updated to the ontology through the query manager 20 in the rule engine, infers the user of the location by transmitting the query to the updated ontology, and again about the service to be provided to the user Collect control device information. The service is determined by applying a policy (security level, device access level, priority, intelligent level) to such device information. At this time, the query manager 20 obtains the position value of the user according to the position of the sensor from the ontology and transmits it to the inference engine 30 according to the request of the inference engine 30.

Thereafter, the service controller 50 checks whether service provision is appropriate for registration, configuration, and scheduling of the corresponding service, and then transmits data (user ID, service name, service status) to the session manager 40. By sending, the user and service status information are registered in the session.

Here, if it is determined whether the service is appropriate, the service controller 50 transmits a user ID (UserID) and service information (service name and status) to the session manager 40, and the session manager 40. Creates a session for each user, determines the service state and whether to provide it to the inference engine 30.

Specifically, the service controller 50 performs service analysis through a service management function. In this case, the service analysis means determining whether the service is registered and whether the service can be provided to the user at the corresponding location. If another service with a higher priority at the location is already running or the service is not authorized to the user, the service request is aborted at this stage and a message is not provided to the user. However, if the priority of the currently requested service is higher than the service already being provided or the appropriate service registered to the user, the service controller 50 registers the service in the scheduler. The service scheduler manages service information for each location and user to prevent service conflicts when multiple services are simultaneously executed at one location or services provided to a user are duplicated. Accordingly, the service controller 50 calls a policy (priority, device access level, security level, intelligent level) to prevent the occurrence of a collision in the service spot to the inference engine 30 to perform service scheduling. do.

Then, when the service is determined by the service scheduler, information for providing the service (user ID, service information (service name and status)) is transmitted to the session manager 40, and the session manager 40 is a user. Creates a separate session, determines the service state and whether to provide it to the inference engine 30. Here, the session manager 40 receives a user ID, a service name (preferred environment service), and a service state (including the user's location) from the service controller 50 in determining the service state and whether to provide the service as a variable value. After parsing the entered information, the state of the session is checked using the user ID as a keyword. That is, information about whether there is a service used by the corresponding user and what the final state of the service is is obtained from the session data table of the knowledge repository 10 through the query manager 20.

Next, the inference engine 30 sends the data to the query manager 20 to apply the corresponding policy after reviewing the input service and information. Then, the query manager 20 generates an appropriate query, transmits the generated query to the ontology of the knowledge repository 10 to obtain information [role of the situation information manager], and then the inference engine. Transfer to 30. After that, when the device to be serviced and controlled is determined, the inference engine 30 transmits corresponding data (device control information) to the device controller to control the device, and the user can recognize the sensor through the interface controller 50. Inform the service processing result. That is, the inference engine 30 collects the user's policy (security level, device access level, priority, intelligent level) from the ontology through the query manager 20, and based on the device, the device is controlled through the device controller. And informs the service processing result due to sensor recognition through the interface controller 50. At this time, if device control is necessary, the device is controlled by transmitting a device control list and a property for the corresponding service to the device controller.

In summary, the context-aware knowledge service system is a knowledge repository that stores and manages information of users and environments, complex concepts of services and time and space, and user-specific policies (security level, device access level, priority, and intelligent level). Ontology) 10 and input data (any one of device control, service mode, user command including system setting, information request message, and sensor input information) are parsed for use in the system, and classified according to service type. Service controller for performing service scheduling to prevent a collision between users or services in a service area by referring to an interface controller 50 for performing the operation and a policy (security level, device access level, priority, and intelligent level). 50 and, when providing a service according to service scheduling, seamlessly tracks the service state for each user (S Infer the service to be provided based on the information collected from the session manager 40 and the knowledge repository (ontology) 10 for providing the eamless service, and the policy (security level, device access level, priority, intelligent level). Inquiry to the knowledge repository (ontology) 10 by generating a query according to the request of the inference engine 30 and the inference engine 30 to dynamically control whether or not the service provided by the user according to the It includes a query manager 20 for receiving the response.

Here, the session manager 40 registers a session when the service is started by storing the state of the user and the service, and stores the final state when the service is terminated, and informs the final state when the service is next requested. It provides a seamless service from the state.

In particular, when the input data are service mode commands and sensor input information, the service controller 50 calls a policy (security level, device access level, priority, intelligent level) to the inference engine 30 to refer to the policy. Perform service scheduling.

When the input data is a device control command, the inference engine 30 receives a user ID and a device name from the interface controller 50, and displays the device and the device to be controlled for the corresponding service through a query generated based on the user ID. Collects information to be collected (collected through the query manager 20), determines whether the device is controlled based on the device access level among the policies, and transmits a device control command to the device controller if available. The control result is transmitted to the user through the interface controller 50.

In addition, when the input data is a system setting command, the inference engine 30 receives a user ID and a policy set by the user (security level, device access level, priority, intelligent level) from the interface controller 50, The policy set by the user is updated in the knowledge repository (ontology) 10 through the query manager 20. In this case, the ontology update result may be notified to the user through the interface controller 50.

In addition, when the input data is an information request message, the inference engine 30 receives a user ID, a query name, and an information name from the interface controller 50, and uses a knowledge repository (ontology) through a query generated based on this. Collect the information requested by the user from the 10 (collected through the query manager 20) and deliver it to the user through the interface controller 50 based on the policy (security level, device access level, priority, intelligent level). do.

In addition, when the input data is a service mode command, the inference engine 30 receives a user ID, a service name, and a service state from the session manager 40, and the device to be controlled for the corresponding service through the query manager 20. And collect information to be displayed, and transmit a device control command to the device controller based on the policy (security level, device access level, priority, intelligent level) and transmit the control result to the user through the interface controller 50.

In addition, when the input data is sensor input information, the inference engine 30 infers the location of the user based on the location of the sensor and collects controller information on the service to be provided to the user, and then the service controller 50. If the service controller 50 determines that there is no service conflict, the device controller is controlled by the device controller based on the policy (security level, device access level, priority, intelligent level). The command is transmitted and the control result is informed to the user through the interface controller 50.

Hereinafter, the configuration and operation of the service control device (Service Controller 50) will be described in more detail with reference to FIGS. 4 and 5.

The service controller 50 is installed and executed on the OSGi framework in the form of an OSGi bundle as shown in FIG. 1.

The service controller 50 may request information about the current user's location or service providing status from another service bundle, and also call various service bundles or provide queries to the inference engine 30 based on information input from the outside. do.

In particular, when a user uses several services at the same time, the service controller 50 performs service scheduling to provide a service by determining an execution order of the service according to a policy at the time of service execution. At this time, scheduling is performed by referring to a policy engine that manages policies when scheduling services. The Policy Engine implements service priority, security level, intelligence level, etc. to resolve service conflicts and provides selective or partial provision of services according to these policies. To develop. In addition, since each service requires detailed data about the service and the user in order to implement a customized service for the user, for this purpose, the inference engine is requested for various information, and the service operation can be performed using the obtained information. Has the function to In addition, each service implements service information tailored to the user based on the transmitted information, and formats the information in a manner that the upper service calls and uses lower unit services to transmit the result to the outside. In this process, each service uses a multi-threading technique to enable efficient processing of multiple service requests of multiple users.

The service controller 50 enables efficient implementation and management of services by providing the following functions, and provides scalability of services. In addition, it provides efficiency by enabling dynamic and rapid processing of various services in a multi-home network.

-If one user is provided with multiple services, the service level and various service policies are determined according to the type of service so that the user can provide the desired service without being duplicated. Schedule.

-Service progress monitoring function that continuously manages the service progress when the service is being provided

-Policy Management function to manage various policies (Intelligence Level, Priority, Security Level) set differently according to users

-Data transmission and data parsing & transformation for data use with Multi-modal Interaction (MMI) for transmission to user-based interface

-Security function that restricts access to user's various information used for customized service according to security level when using service

The service controller 50 having the above function provides a service for a sensor input according to a user's command or a user's movement and environment information. At this time, the service controller 50 analyzes the input information and moves the information to the service bundle as needed. Then, the service controller 50 monitors the state of the service currently used by the user, and if the service is used in multiple times, the service controller 50 temporarily determines the service execution order by referring to various execution policies of the service. At this time, the service is provided to the user according to a predetermined execution order. In addition, the service controller 50 examines whether the service is valid by examining the service for collisions or security problems.

That is, the service controller 50 performs service scheduling to prevent a collision between services in a service area, thereby preventing several services from running simultaneously and colliding, and the service priority and user priority at the corresponding place. It performs service scheduling according to the system and translates various types of context information (control signal and service request signal input from MMI and sensor signal input from sensor in home) into a common format and transmits them to another bundle. do. In addition, the sensor performs classification and management with the basic data according to the classification and user input for each sensor input. In addition, when the input / output information is in a form that is not suitable for processing by the middleware or is incorrectly transmitted, the corresponding information is filtered. In addition, when several signals are transmitted at the same time, it performs scheduling function for data flow and service or transmission to other bundles according to basic context information about each input, and service management and scheduling function by configuring service session for each location. Do this.

Then, referring to FIG. 4, the configuration of the service control device (service controller 50) according to the present invention is characterized by parsing and filtering input data, and transmitting and formatting output data. Data Filter 52, Service Data Manager 53 for loading and managing information about services provided to users from Ontology, and priority between users or services. Policy Engine 54, which provides a policy that allows a service to be executed according to priorities when various services are executed at the same time, and refers to the policy, and simultaneously runs between services in a service area through service scheduling. It includes a service scheduler (55) for preventing a collision according to.

Looking at the function of each component of the service controller 50 according to the present invention having the above configuration in more detail as follows.

The data filter 52 classifies and filters various data transmitted through the TCP socket from the outside to the present system, and serves to format data transmitted from the inside to the external interface. In addition, it is connected to the device controller (Device Controller) that is a module for controlling an external device can transmit the device control signal.

The service data manager 53 performs a function of storing, deleting, and updating a data about a service provided to a user from an ontology.

The service scheduler 55 performs a service scheduling to prevent a collision between services in a service area to prevent several services from being executed at the same time. In this case, the policy for service scheduling is Obtained through policy engine 54.

The policy engine 54 defines a priority between services. Accordingly, when various services are executed at the same time, the policy engine 54 can execute the services according to the priorities.

The data filter 52 is a data interpreter that performs external classification and performs filtering and filtering, and a data formatter that converts internal data when the external data is transmitted to the outside. It is composed.

In addition, the service scheduler 55 may include a service selector for selecting a service to be provided to a user in a service area, and a service checker for checking a service conflict situation in a service area before providing a service. (Service Checker), which classifies services into one-time services and schedule services, and performs a service management engine (Service Managing Engine) for processing the service registration, execution, stop, stop command.

In addition, the policy engine 54 includes a service priority & policy manager for managing priorities and policies between services for resolving service conflicts. In this case, the policies applied include Security Level, Intelligence Level (see Table 4 below), User Priority (see Table 1 and Table 2 below), Device Access Levels (see Table 3 below).

In addition, the service data manager 54 may include a service data table storing service information such as a service name and a service state, and a service query manager which collects / updates query information by accessing the service data table. Service Query Manager).

When the user uses the service, the operation of the service controller 50 is shown in FIG. 5.

In the case of accessing the service controller 50 from an external bundle, the service controller 50 transmits a service name, a service state, and a user ID to the service controller 50 to execute a specific service. In this case, the service controller 50 performs an interface function. In this case, the user may directly access the server socket 51 from the MMI 60 and the UI or enter a sensor value. Service controller 50 performs a service management function.

That is, when data is transmitted to the context-aware server socket 51, data transmitted from the outside of the system (MMI, UI, Sensor, etc.) is transmitted through the socket communication with the service controller 50. In this case, the service controller 50 sorts the data transmitted from the outside and transmits the data to the appropriate service bundle. If the data transmitted from the outside is wrong data or data that is not useful for providing the service, the service controller 50 filters the data. do. That is, a user requests a service (a request for information on the environment, a schedule of another user's environment, etc.) or a command (device control, system setting) through a UI of a terminal (PDA, mobile phone, etc.) that the user has. Etc.), and also when sensor information according to a user's movement is transmitted to the system, data is transmitted to the server socket 51 of the service controller 50. In this case, since the transmitted information does not use the service management function of the service controller 50, the service controller 50 only serves as an interface for receiving information from the outside (interface controller 50 role). . Looking at this in detail.

First, the interface function of the service controller 50 will be described.

When a command (device control, system setting, etc.) is input through a user terminal, Homepad / Wallpad, or the Internet, input data (Command) is converted into XML and transmitted to the server socket 51 of the service controller 50, XML Parsers are parsed into data that can be used inside the system. In this case, the classified data is transmitted to the corresponding bundle according to the service type. In case of device control, data [user ID and device name] are transmitted to the inference engine 30, and in case of system setting, user ID. And the policy set by the user (Priority, Device Access Level, Security Level, Intelligence Level) is transmitted to the inference engine (30).

In addition, when there is a request for information (eg, home environment information, schedule, profile, service level, security level, etc.) through a user terminal, a homepad / wallpad, the Internet, or the like, an information request converted into XML from the user terminal or the like is also requested. The message is sent. Thereafter, the data converted into XML (information request message) is transmitted to the server socket 51 of the service controller 50 and parsed into data that can be used in the system through an XML parser. Subsequently, the interface controller 50 analyzes the parsed data [user ID, query name, information name] through the interfacing engine (recognizes that it is an information request in this case) and a reasoning engine. (30).

In addition, when sensors located in each service area (eg, living room, room, entrance, etc.) detect the user (ie, when the user's location changes or the state of the service area changes, etc.), the sensor is connected to the interface controller ( The sensor information (position coordinate information of the sensor) is transmitted to a listener of the interface controller 50. Then, if the data transmitted from the sensor (sensor information) is duplicated or damaged, the interface controller 50 filters the filtered data, and then transmits the data [user ID, sensor data to the API of the inference engine 30]. , User location].

In the above, the input interface function of the service controller 50 has been described. Looking at the output interface function of the service controller 50 corresponding to this, when the command is a service mode input, the inference engine 30 determines the device to be serviced and controlled, the corresponding data (device control information) device controller (Device Controller) ) And the processing result to the interface controller 50 to provide a service to the user. At this time, if device control is necessary, the device is controlled by transmitting a device control list and a property for the corresponding service to the device controller.

In addition, if the command is a device control input, the inference engine 30 determines whether the device is controlled based on the collected information (user device access level in the policy), and if available, a control command (on / off) to the device controller. ) And notify the user via the interface controller 50 of the processing result. At this time, if device control is necessary, the device is controlled by transmitting a device control list and a property for the corresponding service to the device controller.

In addition, when the command is a system setting input, the inference engine 30 notifies the user of the processing result (ontology update result) through the interface controller 50.

In addition, in the case of a user's information request input, the inference engine 30 collects the information requested by the user, determines the information according to a policy (security level, priority), and transmits the information to the user through the interface controller 50.

In addition, in the case of sensor input information, the inference engine 30 transmits a device control command to the device controller based on a policy (security level, device access level, priority, intelligent level) and outputs the control result to the interface controller 50. Inform the user via At this time, if device control is necessary, the device is controlled by transmitting a device control list and a property for the corresponding service to the device controller.

Meanwhile, a service management function of the service controller 50 will be described.

When data about a service transmitted from a bundle inside the system is transmitted to the API 51 of the service controller 50, the service controller 50 performs a service management function which is its own function. That is, service analysis is first performed using the inputted information. In this case, the service analysis means determining whether the service is registered and whether the service can be provided to the user at the corresponding location. If another service with a higher priority at the location is already running or the service is not authorized to the user, the service request is aborted at this stage and a message is not provided to the user. However, if the priority of the currently requested service is higher than the service already being provided or the appropriate service registered to the user, the service controller 50 registers the service with the service scheduler 55. In this case, the service scheduler 55 manages location and user-specific service information to prevent service conflicts when multiple services are simultaneously performed at one location or services provided to one user are duplicated. Accordingly, the service controller 50 calls the inference engine 30 with a policy (priority, device access level, security level, intelligent level) for preventing a collision in a service area, and performs a service schedule. do. Thereafter, when a service is determined by the service scheduler 55, information (user ID, service name, service status) for providing a service is returned to the session manager 40.

That is, when a command (service mode, etc.) is input through a user terminal, Homepad / Wallpad, or the Internet, the input data (Command) is converted into XML and transmitted to the server socket 51 of the service controller 50, and the XML parser Parsing is made into data available inside the system. In this case, the classified data is transmitted to the corresponding bundle according to the service type. In the case of the service mode, the data [User ID, Service Name, Service Status] is the service controller 50. Is sent to. As a result of the classification, in the service mode, data [User ID, Service Name, Service Status] is transmitted to the service controller 50, and the service controller 50 is transmitted. Analyzes information about services At this time, the service controller 50 checks whether service provision is appropriate for registration, configuration, and scheduling of the corresponding service. When it is determined whether the service is appropriate, the service controller 50 transmits a user ID (UserID) and service information (service name and service status) to the session manager 40.

In addition, as described above, when a user is detected by a sensor located in each service area (eg, a living room, a room, a front door, etc.) (that is, when the user's location changes or the state of the service area changes), The sensor transmits sensor information (position coordinate information of the sensor) to the interface controller 50, and the interface controller 50 filters the data (sensor information) transmitted from the sensor if it is duplicated or damaged. , The data (ie, user ID, sensor data, user location) is transmitted to the API 31 of the inference engine 30. Thereafter, the inference engine 30 determines the service to be provided in the corresponding area (eg, living room, home room, entrance hall, etc.) with reference to the sensor information. At this time, the service is determined by referring to the ontology of the knowledge repository 10. The inference engine 30 reviews the input sensor information and then applies the query to the query manager 20 to apply the corresponding policy. After transmitting the data, the query manager 20 generates an appropriate query and transmits the generated query to the ontology of the knowledge repository 10 to obtain information, and then returns to the inference engine 30. send. In this case, the inference engine 30 infers the location of the user based on the location of the sensor, and collects controller information on the service to be provided to the user. Subsequently, when the service is determined, the inference engine 30 transmits corresponding service information (user ID, service name (preferred environment service), service status value (including user's location)) to the service controller 50.

Thereafter, the service controller 50 checks whether service provision is appropriate for registration, configuration, and scheduling of a corresponding service [service management function], and then transmits data (user ID, service name, service status) to the session manager 40. ) To register the user and service status information in the session.

In the above, the policy (security level, device access level, priority, intelligent level) referenced by the service controller 50 will be described in more detail as follows.

Priority is divided into User Priority (see Table 1 below) and Task Priority (see Table 2 below).

As shown in [Table 1], User Priority sets the priority of service users, and when two or more users request the same service in the same space, the priority of the user is confirmed by checking the priority of the user. Provide the requested service to the user.

In addition, task priority is a priority of services, as shown in Table 2 below. When a user requests several services, the task priority is provided according to the priority of the corresponding service.

On the other hand, the security level (Security Level) is to apply a differential security level for the context (Context) in order to enhance user privacy and security. Depending on this security level, the degree of disclosure of user information (basic information and schedules) will vary.

On the other hand, the Device Access Level is applied to different situations and environments by applying a level to use, control and manage the device in conjunction with the user's level as shown in [Table 3] below. The level varies.

On the other hand, the intelligence level (Intelligence Level) is used to provide a preferred environment service, as shown in Table 4 below. Therefore, by checking the intelligence level (Intelligence Level) of each user to provide a preferred environment service according to the level.

The service scheduler 55 of the service controller 50 is responsible for service management for each user and for each location. The life cycle of the services managed by the service scheduler 55 is shown in FIG. 6.

As shown in FIG. 6, the status of each service is divided into four states: Register, Start, Pause, and Stop.

When a user inputs through a UI or the like to use a service or a command of executing a specific service comes from the inference engine 30 through sensor value input, the service is registered in the user / service DB, and from this time, the service scheduler ( 55, it is possible to manage the status of the service.

After that, when the service is started and enters the Start state, and the service having a higher priority than the service currently being executed by the service scheduler 55 is executed, the current service is paused by the pauseService command. Will enter. At this time, the paused service stores the service state in the session manager 40 and the service data table, and when executed again, provides a seamless service by reloading the service state. Makes it possible. In addition, when the service is completely terminated, the service is stopped and the registration is released from the service scheduler 55.

As described above, a service is required for a sensor input according to a command or movement of the user and a sensor input according to environmental information. At this time, the service controller 50 according to the present invention analyzes the input information and moves the information to the service bundle as needed, monitors the status of the service currently used by the user, and if the service is used in multiple times, The service execution rank will be temporarily determined by referring to various execution policies of. At this time, the service is provided to the user according to a predetermined execution order. In addition, the service controller 50 examines whether the service is valid by examining the service for collisions or security problems.

On the other hand, the method of the present invention as described above can be written in a computer program. And the code and code segments constituting the program can be easily inferred by a computer programmer in the art. In addition, the written program is stored in a computer-readable recording medium (information storage medium), and read and executed by a computer to implement the method of the present invention. The recording medium may include any type of computer readable recording medium.

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.

The present invention can be used for context awareness knowledge service.

1 is a diagram illustrating an example of a middleware configuration of a cognitive knowledge service system to which the present invention is applied;

2 is a configuration diagram of an embodiment of a knowledge service system in which the present invention is applied;

3 is a diagram illustrating an operation of a knowledge cognitive service system to which the present invention is applied;

4 is a detailed configuration diagram of an embodiment of the service controller of FIG. 2 according to the present invention;

5 is a diagram for explaining an operation of a service control device according to an embodiment of the present invention;

6 is an exemplary diagram illustrating a service life cycle in the service scheduler of the service control device according to the present invention.

* Explanation of symbols for the main parts of the drawings

10: Knowledge Repository 20: Query Manager

30: Reasoning Engine 40: Session Manager

50: interface / service controller 60: multi-modal interface (MMI)

Claims (13)

In the service control device of the context aware knowledge service system, Data filtering means for classifying and filtering the input data, and converting the output data into a format suitable for a module to be transmitted; Service data management means for loading and managing information on a service provided to a user from an ontology; Policy means for defining priorities between users or services, and providing a policy for executing services according to service priorities when various services are executed simultaneously; And Service scheduling means for preventing conflicts due to simultaneous execution of services in a service area through service scheduling with reference to the above policy Service control device for a context-aware knowledge service comprising a. The method of claim 1, The service scheduling means, Service information for each location and user is managed to simultaneously perform multiple services in one location or duplicate services provided to one user. Service control device for a context-aware knowledge service, characterized in that to perform service scheduling. The method of claim 2, The service scheduling means, After selecting a service to be provided to the user in the service area, checking the service conflict situation in the service area before providing the service, classifying the service into a one-time service and a schedule service and registering the service with a command for registering, executing, stopping, and stopping the service. And a service control device for a context-aware knowledge service, characterized in that the processing for the situation is performed. The method of claim 3, The service scheduling means, Determine whether the service is registered and whether the service can be provided to the user at the location, manage the status of the service when the service is determined, if the service with higher priority than the currently running service is running, Service control for cognitive knowledge services, characterized by providing a seamless service by stopping the service of the service, storing the service state in the session manager and the service data table, and recalling the service state when it is executed again. Device. The method of claim 1, The data filtering means, Parsing the input data and filtering the data if the data is not suitable for processing by middleware or incorrectly transmitting the data, and formatting the output data and transmitting the data to the service bundle. Service control device for contextual knowledge services characterized in that. The method of claim 1, The input data is, Device control, service mode, a user command including a system setting, a service request device for a knowledge service whether the situation, characterized in that any one of the information request message, the sensor input information. The method of claim 6, The service control device, And when the input data is a service mode command and sensor input information, calling the policy to an inference engine to perform the service scheduling with reference to the policy. The method according to any one of claims 1 to 7, The above policy, If multiple users request the same service in the same space by setting the priority of service users, check the user's priority to provide the requested service to users with higher priority, or set the priority between services so that one user requests multiple services. The priority of providing the service according to the priority of the service, Security level that varies the degree of disclosure of user information through the differential security level of situation information for user privacy and security enhancement, Appropriate level to use, control, and manage the device in conjunction with the user's level, and the level of device access according to different situations and environments, Service control apparatus for the context-aware knowledge service, characterized in that it comprises an intelligent level for providing a preference environment service according to the level. In the service control method of the service control device, Defining priorities between users or services, and setting a policy so that services can be executed according to service priorities when various services are executed simultaneously; When requesting a service, referring to the policy to determine whether the service is registered and whether the service can be provided to the user at the corresponding location; As a result of the determination, if the priority of the currently requested service is higher than a service already provided or an appropriate service registered to the user, registering the service with the service scheduler; Stopping a current service and storing a service state in a service data table when a service having a higher priority than a service currently being executed by the service scheduler is executed; Resuming the service by calling a service state stored in the service data table when the service is executed; And Releasing a service registered in the service scheduler when the service ends; Service control method for a context-aware service comprising a. The method of claim 9, The service scheduler, Service information for each location and user is managed to simultaneously perform multiple services in one location or duplicate services provided to one user. Service scheduling method for a context-aware knowledge service, characterized in that to perform service scheduling. The method of claim 10, The service scheduler, After selecting a service to be provided to the user in the service area, checking the service conflict situation in the service area before providing the service, classifying the service into a one-time service and a schedule service and registering the service with a command for registering, executing, stopping, and stopping the service. A service control method for a context-aware knowledge service, characterized in that for executing a process for. The method according to any one of claims 9 to 11, The above policy, If multiple users request the same service in the same space by setting the priority of service users, check the user's priority to provide the requested service to users with higher priority, or set the priority between services so that one user requests multiple services. The priority of providing the service according to the priority of the service, Security level that varies the degree of disclosure of user information through the differential security level of situation information for user privacy and security enhancement, Appropriate level to use, control, and manage the device in conjunction with the user's level, and the level of device access according to different situations and environments, Service control method for the context-aware knowledge service, characterized in that it comprises an intelligent level for providing a preference environment service according to the level. In the service control device having a processor for context awareness knowledge service, Defining priorities between users or services, and setting a policy to execute services according to service priorities when various services are executed simultaneously; A function of determining whether to register a service and whether the service can be provided to a corresponding user at a corresponding location when referring to the policy; As a result of the determination, if a priority of a currently requested service is higher than a service already provided or a proper service registered to a corresponding user, registering a corresponding service in a service scheduler; A function of stopping a current service and storing a service state in a service data table when a service having a higher priority than a service currently being executed by the service scheduler is executed; When executing a service, calling a service state stored in the service data table to restart the corresponding service; And A function of releasing a service registered in the service scheduler when the service ends A computer-readable recording medium having recorded thereon a program for realizing this.

Images