JP5571484B2 - Real space application service control system and control method - Google Patents

Description

  The present invention relates to a control system and control method for a real space application service realized by using various devices such as home appliances, sensors, actuators and the like connected to each other by a network such as the Internet.

  Home network services using information appliances are gradually becoming more widely recognized as a technology that is already approaching the practical use phase and the diffusion phase. Various services have been proposed in the fields of home security, home control, entertainment, life support, etc., and many have been put to practical use, such as machine security (home security), monitoring systems for the elderly, home automation, and remote meter reading. . In the ubiquitous network society where all things are expected to be connected to the network in the future, not only the information home appliances mentioned above, but also various other devices, sensors, actuators, etc. are connected to the network, home network services It is expected that the diversity and added value of home network service will be further improved (to distinguish it from the present, the evolution of home network service is called “real space application”).

  In the control of real space applications, great scalability is required because the types and number of things connected to the network increase dramatically. Conventionally, the software meets the requirements of scalability by generating small software called agents for each person, device, and place, and executing the state management and communication control of people, devices, and places. Techniques aimed at making them have been proposed (Non-Patent Documents 1 to 3).

  FIG. 14 is a diagram showing a service providing mechanism in the prior art. Here, it is assumed that when a person P enters a room Q, a service is provided that has a scenario in which the TV R is automatically turned on if no one is present. Hereinafter, the operation of the conventional system will be described in order. When the person P enters the room Q, the sensor S detects it. The sensor S notifies the device agent DA (S) corresponding to itself that the person P has entered the room (step S101). Subsequently, DA (S) notifies FA (Q), which is an agent in room Q, that person P has entered the room (step S102).

  Furthermore, FA (Q) notifies HA (P), who is the agent of person P, that person P has entered the room (step S103). HA (P) holds the service activation condition T, and when HA (P) receives the person P's entry notification, the profile information of the person P including the service activation condition T is returned to FA (Q) (step). S104). FA (Q) inspects the service activation condition T, and instructs the device agent DA (R) of the television R to turn on the television R when only the person P exists in the room Q. Is transmitted (step S105). The DA (R) that received it translates the power-on command into a command for operating the actual device, and transmits it to the television R (step S106). As a result, the TV R is turned on.

  Steps S101, S102, S103, S104, and S106 are predetermined steps. When a certain event (E) occurs, a specified action (A) is executed if a specific condition (C) occurs. Is realized by an ECA rule. The same operation is always performed regardless of conditions. Step S105 varies depending on the result of the condition determination performed according to the service activation condition T, but is also realized using the ECA rule. In addition, the device to be used holds the identifier of the person P who is using the device as profile information. When another person tries to use the device, the profile information is referred to, and the use is permitted only when there is no real space application that is already using the device. It is a mechanism that prevents the occurrence of device competition where spatial applications try to use the same device. Since such an agent is small software as described above, the above scenario can be executed by executing the agent on a server in which a communication line is connected to these sensors and actuators (for example, the television R). .

Kamibayashi, Takemoto, Tsuji, Uchiyama, Teramoto, “A Study on Realization of Service Provision by Real Space Agents,” IEICE General Conference, B-20-13, Mar. 2009. Kaoru, Shinrin, Uchiyama, Takemoto, Teramoto, “Device Control Overlay Network for Real Space Services,” The Shin-Seikai General Conference, B-20-14, Mar. 2009. Takemoto Shinrin, Tsuji, Uchiyama, Teramoto, “Agent model for real space service realization,” Shinsei Gakkai General Conference, B-20-15, Mar. 2009.

  According to the prior art described above, the scenario to be realized needs to be decomposed into a set of ECA rules and embedded in the agent corresponding to the event in advance. The task of disassembling a scenario intended by a real-space application service developer into a plurality of ECA rules in consideration of the operation target device, the operation content for each step, or the execution order is technical as the scenario becomes more complicated. It is not a problem that can be easily solved by increasing the difficulty. Also, when deploying and deleting scenarios, distributing ECA rules and profile information across multiple devices, venues, and human agents places a great burden on the service developer or user. . Furthermore, in such a technique for embedding multiple ECA rules by embedding an agent, when there are multiple scenarios, multiple rules are set for the same agent, making it difficult to manage the correspondence between the rules and the scenarios. Become. For this reason, there is a problem that there is a high possibility that an inconvenience such as a mixture of a plurality of scenarios will occur.

  This scenario is realized by a plurality of ECA rules, but there is no mechanism for managing a single scenario as a batch. Therefore, there is no mechanism for managing and holding information related to the scenario, such as basic information such as the scenario name and ID, and information such as what is the list of all devices used by the scenario. This means that various processes that should be performed by recognizing the scenario unit cannot be performed. Since device conflict detection is performed independently by each device agent, when a real-space application uses multiple devices, the scenario may be partially possible or impossible. There is a problem that it may occur and is inappropriate as an execution form of the application. In addition, each scenario is attributed to a person, and the person who occupies and uses the equipment is a person. For example, it can handle cases where multiple people experience the same scenario together, such as watching TV. There is a problem that you can not.

  The present invention has been made in view of such circumstances, and a real space using an agent that realizes scalability for handling a huge number of items such as various devices, sensors, actuators as well as information appliances. In the application control method, the cost reduction associated with the introduction and release of scenarios, the appropriate method for detecting and resolving device conflicts, and the real-space application service that can realize the diversity of usage modes that allow scenarios to be used by multiple users. It is an object to provide a control system and a control method.

  The present invention is a system for controlling a real space application service provided by controlling a device connected to a network via a software agent, and the real space application service is executed by the corresponding application software. The contents of the application software can be freely changed in a range that can be described by the application software, and a plurality of the application software can exist and operate simultaneously, and the real space application service, Software corresponding to each of the user of the system that controls the real space application service, the device, the real space application service, and the place where the real space application service is provided. Characterized in that it comprises a wear agent.

  According to the present invention, the software agent includes a communication unit that performs information communication with each other, a storage unit that stores information, and a control unit that controls operation, and the software agent corresponding to a place where the real space application service is provided The storage means included in the information includes the status of the place where the real space application service is provided, information on attributes, a list of devices installed in the place, and the real space application service that uses the device for each of the devices. Identification information, information related to the type of exclusive operation executed prior to device operation is held, and storage means provided in the software agent corresponding to the device includes information regarding the state and attributes of the device, and a protocol for communicating with the device. Etc., commands for operating the device Information about the real space application service that uses the device, information about the exclusive operation type to be executed prior to device operation, and the storage means included in the software agent corresponding to the user stores the status of the user , Information related to attributes, identification information of real space application services enjoyed by the user, and storage means included in the software agent corresponding to the real space application services include the status and attributes of the devices used by the application services. And information for communicating with the software agent corresponding to the device and identification information of the user of the application service.

  According to the present invention, the software agent corresponding to the real space application service has a tree structure in which a child software agent is connected under one parent software agent, and for each combination of devices used by the real space application service. One child software agent is generated.

  According to the present invention, a software agent corresponding to a place where the real space application service is provided holds information on a real space application service that uses the device for each device installed in the place, and the real space application The service obtains the usage status of the device to be used by inquiring of the software agent corresponding to the location where the real space application service is provided through the software agent corresponding to itself, and other real space application services. If not used, the device usage information held by the software agent corresponding to the location where the real space application service is provided is updated to obtain the right to use.

  According to the present invention, the real space application service acquires the use status of the device to be used by inquiring the software agent corresponding to the device via the software agent corresponding to the real space application service. If not used, the real space application service information using the device held by the device is updated to obtain the right to use.

  According to the present invention, when the software agent corresponding to the real space application service occupies each device to be used, the software agent continues to occupy the device until the application service is started or ended, or an operation is performed. It is characterized in that it is stored as profile information of the device, which is used every time it is used, and when the operation is completed, the occupation is released.

  According to the present invention, after the real space application service obtains a right to use a device required by itself, a device operation command and input information from the device are transmitted to the software agent corresponding to the device and the software agent corresponding to the device. It transmits or receives via communication between.

  The present invention relates to a control method in a system for controlling a real space application service provided by controlling a device connected to a network via a software agent, and the real space application service is a corresponding application. It is realized by executing software, and the contents can be freely changed within a range that can be described by the application software, and a plurality of the application software can exist and operate simultaneously, and the real space application A service, a user of a system controlling the real space application service, the device, the real space application service, and a place where the real space application service is provided. Characterized in that it comprises a software agent corresponding to.

  According to the present invention, the software agent includes a communication unit that performs information communication with each other, a storage unit that stores information, and a control unit that controls operation, and the software agent corresponding to a place where the real space application service is provided The storage means included in the information includes the status of the place where the real space application service is provided, information on attributes, a list of devices installed in the place, and the real space application service that uses the device for each of the devices. Identification information, information related to the type of exclusive operation executed prior to device operation is held, and storage means provided in the software agent corresponding to the device includes information regarding the state and attributes of the device, and a protocol for communicating with the device. Etc., commands for operating the device Information about the real space application service that uses the device, information about the exclusive operation type to be executed prior to device operation, and the storage means included in the software agent corresponding to the user stores the status of the user , Information related to attributes, identification information of real space application services enjoyed by the user, and storage means included in the software agent corresponding to the real space application services include the status and attributes of the devices used by the application services. And information for communicating with the software agent corresponding to the device and identification information of the user of the application service.

  According to the present invention, the software agent corresponding to the real space application service has a tree structure in which a child software agent is connected under one parent software agent, and for each combination of devices used by the real space application service. One child software agent is generated.

  According to the present invention, a software agent corresponding to a place where the real space application service is provided holds information on a real space application service that uses the device for each device installed in the place, and the real space application The service obtains the usage status of the device to be used by inquiring of the software agent corresponding to the location where the real space application service is provided through the software agent corresponding to itself, and other real space application services. If not used, the device usage information held by the software agent corresponding to the location where the real space application service is provided is updated to obtain the right to use.

  According to the present invention, the real space application service acquires the use status of the device to be used by inquiring the software agent corresponding to the device via the software agent corresponding to the real space application service. If not used, the real space application service information using the device held by the device is updated to obtain the right to use.

  According to the present invention, when the software agent corresponding to the real space application service occupies each device to be used, the software agent continues to occupy the device until the application service is started or ended, or an operation is performed. It is characterized in that it is stored as profile information of the device, which is used every time it is used, and when the operation is completed, the occupation is released.

  According to the present invention, after the real space application service obtains a right to use a device required by itself, a device operation command and input information from the device are transmitted to the software agent corresponding to the device and the software agent corresponding to the device. It transmits or receives via communication between.

  According to the present invention, in a real space application service control system using an agent model, introduction of a scenario is compared with a conventional method in which a plurality of ECA rules are held in an agent and a scenario is realized by linking them. Deletion and management are greatly facilitated. In addition, by securing the right to use the device and operating the device through the agent corresponding to the real space application service, one real space application service occupies and operates a plurality of devices at the same time; and In addition, it is possible to realize the cooperative use in which a plurality of users use the same real space application service.

It is a figure which shows the structure of the software and hardware in 1st Embodiment of this invention. It is a flowchart which shows operation | movement of the system shown in FIG. It is a sequence diagram which shows the detailed processing operation of the system shown in FIG. It is a sequence diagram which shows the detailed processing operation of the system shown in FIG. It is a figure which shows the structure of the software and hardware in 2nd Embodiment of this invention. It is a flowchart which shows operation | movement of the system shown in FIG. In the system shown in FIG. 5, it is a sequence diagram which shows the detailed processing operation | movement which updates the profile information of the real space application 1 after a subsequent user makes a use application. It is a figure which shows the structure which allocates an agent for every apparatus set. It is. It is a figure which shows the structure of the software and hardware in 3rd Embodiment of this invention. It is a sequence diagram which shows the processing operation which secures the apparatus which the real space application 12 uses. It is a sequence diagram which shows the processing operation which secures the apparatus which the real space application 12 uses. It is a sequence diagram which shows the execution processing operation | movement of the real space application in 4th Embodiment of this invention. It is a figure which shows the mechanism of the service provision in a prior art.

<First Embodiment>
Hereinafter, a control system for a real space application service according to a first embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing a software and hardware configuration in the first embodiment. Here, it is assumed that one person exists in a room as an entity, and a real space application for using two devices operates. Each entity has a corresponding software agent. The room includes a room agent (hereinafter referred to as FA) 2, the real space application 1 includes a real space application agent (hereinafter referred to as SA) 3, and the person includes a human agent (hereinafter referred to as HA) 4. Exists. The actual device 7 includes a device agent (hereinafter referred to as DA) 5, and the device 8 includes a device agent (hereinafter referred to as DA) 6. The system shown in FIG. 1 includes an application layer in which the real space application 1 exists, a platform layer in which each agent exists, and a physical layer in which devices exist. The real space application 1 is provided from an application provider.

  Each software agent includes a communication unit that performs information communication with each other, a storage unit that stores information, and a control unit that controls operations. The storage means included in the FA 2 includes the status of the place where the real space application service is provided, information on attributes, a list of devices installed at the location, and identification of the real space application service that uses the device for each of the devices. Information and information related to the exclusive operation type executed prior to device operation are held. The storage means provided in the DAs 5 and 6 includes device status and attribute information, information such as a protocol for communicating with the device, information about commands for operating the device, and identification information of the real space application service that uses the device. In addition, information regarding the exclusive operation type to be executed prior to the device operation is held. In addition, the storage means included in the HA 4 holds information regarding the state of the user (person) and attributes, and identification information of the real space application service enjoyed by the user. Further, the storage means included in SA3 holds the status and attributes of the device used by the application service, information for communicating with each software agent corresponding to the device, and identification information of the user of the application service. .

  Next, a processing operation for starting and executing the real space application 1 will be described with reference to FIG. FIG. 2 is a flowchart showing the operation of the system shown in FIG. First, when SA3 receives an activation request (step S1), SA3 activates a real space application (the application is shown as AP in the drawing) 1 (step S2). The activation request is made, for example, by setting in advance to automatically activate when a person enters the room, or by selecting from a list an available service displayed on the portable terminal held by the person. An activation request is issued.

  After the real space application 1 is activated, it enters a standby state, and checks whether the target device is already used by another real space application by determining whether a device used by the real space application 1 can be secured. (Step S3). If the target device is not used (if the target device is usable), information indicating that the real space application 1 is used is added to the profile of the person managed by the HA 4 to update the profile ( Step S4). After the above processing is completed, the real space application 1 is executed and the actual device operation is performed (step S5). On the other hand, when the target device to be used is already used for another real space application, the real space application 1 is not executed, and the execution of the real space application 1 fails (step S6).

  Next, the detailed processing operation of the system shown in FIG. 1 will be described with reference to FIG. FIG. 3 is a sequence diagram showing detailed processing operations of the system shown in FIG. First, HA4 transmits a trigger to activate real space application 1 to SA3 (step S11). In response, when SA3 transmits a start command to the real space application 1 (step S12), the real space application 1 is started and a response is returned to SA3 (step S13).

  Next, SA3 transmits a device occupation request to FA2 (step S14). In response to this, the FA 2 transmits a device occupation request to the DA 5 (step S15). The DA 5 updates the profile if the device 7 can be occupied (step S16), and returns a response to the FA 2 ( Step S17). When FA2 transmits a device occupation request to DA6 (step S18), DA6 updates the profile if device 8 can be occupied (step S19), and returns a response to FA2 (step S20). . Then, the FA 2 returns a response (OK) to the device occupation request to the SA 3 (Step S21).

  Next, SA3 transmits execution permission to the real space application 1 (step S22). In response to this, the real space application 1 enters an executable state and returns a response to SA3 (step S23). When the response is returned, SA3 returns a response of activation OK to the activation trigger to HA4 (step S24). In response to this, the HA 4 updates the profile (step S25). Thereafter, when the real space application 1 transmits a device operation command to operate the device 7 and the device 8 to the SA3 as necessary (steps S26 and S28), the SA3 transmits to the DA5 and DA6. Then, a device operation command is transmitted (steps S27 and S29).

  As described above, since the FA 2 grasps the occupation status of the devices 7 and 8, the device occupation request is transmitted to the FA 2, and the device profile information is updated when the target device is not used in another real space application. Thus, the real space application 1 can use the device.

  Next, another detailed processing operation in the system shown in FIG. 1 will be described with reference to FIG. The processing operation shown in FIG. 4 is different from the processing operation shown in FIG. 3 in that negotiation for device occupancy is performed individually with each device agent (DA5, DA6). First, HA4 transmits a trigger to activate real space application 1 to SA3 (step S31). In response to this, when SA3 transmits an activation command to real space application 1 (step S32), real space application 1 is activated and a response is returned to SA3 (step S33).

  Next, when SA3 transmits a device occupation request to DA5 (step S34), DA5 updates the profile if device 7 can be occupied (step S35), and returns a response to SA3 (step S36). ). When SA3 transmits a device occupation request to DA6 (step S37), DA6 updates the profile if device 8 can be occupied (step S38), and returns a response to SA3 (step S39). .

  Next, SA3 transmits execution permission to the real space application 1 (step S40). In response to this, the real space application 1 enters an executable state and returns a response to SA3 (step S41). When the response is returned, SA3 returns a response of activation OK to the activation trigger to HA4 (step S42). In response to this, the HA 4 updates the profile (step S43). Thereafter, when the real space application 1 transmits a device operation command to operate the device 7 and the device 8 to the SA3 as necessary (steps S44 and S46), the SA3 transmits to the DA5 and DA6. Then, a device operation command is transmitted (steps S45 and S47).

  The advantage of the processing operation shown in FIG. 4 is that the load of the device occupation processing can be distributed and concentrated on the FA 2 can be avoided. However, since the amount of the entire sequence increases, it is desirable to determine in consideration of the introduction form of each agent, for example, whether or not the room agent and the device agent are installed on the same server.

  In this way, device operation commands from the real space application 1 are performed via the corresponding agent (SA3), so that it is possible to prevent individual devices from being directly operated from the application layer, thereby improving security. Can be made. In the prior art, a plurality of rules embedded in the agent in advance is activated by an event that occurs in the real space and is linked to each other, and there is no function for managing a single scenario as a whole. Therefore, there is no mechanism for managing and holding information related to the scenario, such as basic information such as the scenario name and ID, and information such as what is the list of all devices used by the scenario.

  In the first embodiment, a scenario is provided as a single real space application service, and information related to the real space application service is managed and maintained by the corresponding agent. Therefore, management including introduction and deletion of scenarios is performed. Becomes easy. In addition, since the real space application service and the agent corresponding to the real space application service can share and handle various processes, load distribution can be achieved. For example, authentication processing related to the use of the real space application service can be partly performed by an agent.

  The software implementation of the system shown in FIG. 1 can be performed using an existing agent platform. For example, PIAX (http://www.piax.org/) which is open source software can be used. It is.

Second Embodiment
Next, a control system for a real space application service according to a second embodiment of the present invention will be described. FIG. 5 is a diagram showing a software and hardware configuration in the second embodiment. In this figure, the same parts as those in the system shown in FIG. The system shown in FIG. 5 is different from the system shown in FIG. 1 in that there are two people (users) using the real space application 1 and there are corresponding human agents HA41 and HA42.

  Next, referring to FIG. 6, when the user 1 (HA 41) is already using the real space application 1 and another user 2 (HA 42) expresses the intention to use the real space application 1. A series of processing operations will be described. FIG. 6 is a flowchart showing the operation of the system shown in FIG. The state in which there is already a user in use When a request for use is issued from another user, there are two steps. The first stage is confirmation of the user's usage qualification. For example, in the case where the place is a private home, the resident permits, but the other guests do not permit the authentication process. After passing through this first stage, the next second stage is to use the real space application 1 together with the previous user who has already used it (referred to as cooperative use), or use the same real space application 1 It is a process control process that starts another one and uses the preceding user and the succeeding user separately.

  The processing operation shown in FIG. 6 is a processing operation when the user 1 and the user 2 use the system cooperatively. It is reasonable for the authentication process and the process control process to be basically determined by the real space application 1 that is the service provider. The authentication process is performed based on the profile information of the user 2 held by the agent HA2. Further, the process control processing makes an inquiry to the user 2 as necessary, and confirms the intention. However, in general, in the real space application 1, since services are provided by actual device operations, there are rare cases where there are a plurality of devices of the same type, especially when assuming home appliances in general homes. It is considered that cooperative use is often selected. Multiple process activation is selected when there are many devices in a public space or the like.

  First, when a request for use of the real section application 1 is issued from the HA 42 (step S51), the real space application 1 determines whether or not to permit the use (step S52). If the real space application 1 permits the use of the user 2 as a result of this determination, the SA 3 and the HA 42 update the profile information (step S53). As a scenario of the real space application 1, in the case where an intention display or operation from the user is necessary, the real space application 1 sends the request to the user held as the corresponding SA3 profile information.

  When the service providing method varies depending on individual users, for example, in the case of display on an electronic terminal carried by the user, the information is displayed on the portable terminal of each user held as profile information of SA3. Will be. That is, the action of “using a real space application” including cooperative use is equivalent to being described in the profile information (use user) of the corresponding agent (SA3) of the real space application 1. Then, the HA 41 (user 1) and the HA 42 (user 2) use the real space application 1 together (step S54). On the other hand, if the use of the real space application 1 is not permitted, the HA 42 (user 2) cannot use the real space application 1 (step S55).

  Next, the detailed processing operation of the system shown in FIG. 5 will be described with reference to FIG. FIG. 7 is a sequence diagram showing a detailed processing operation for updating the profile information of the real space application 1 after a subsequent user makes a use application in the system shown in FIG. First, the HA 42 transmits a use request for the real space application 1 to SA3 (step S61). In response to this, SA3 transmits information for requesting use permission judgment to real space application 1 (step S62). When the real space application 1 that has received this request returns a response of “OK” to SA3 (step S63), SA3 updates the profile (step S64). Subsequently, the SA 3 permits the HA 42 to use the real space application 1 and transmits information for instructing profile update (step S65). In response to this, the HA 42 updates the profile (step S66).

  If the scenario belongs to a person (user) and the person who occupies and uses the device is a person as in the prior art, each scenario belonging to multiple people is recognized as a different scenario, so it is not a collaboration. There was a problem of being detected as a conflict. In the second embodiment, the entity that occupies and uses the device is a real space application (effectively an agent corresponding to the real space application), and a person has a relationship of using the real space application. Even if they try to use the same scenario (real space application) at the same time, there is no effect on the relationship between the device and the real space application that occupies and uses the device, so that cooperative use is possible.

  The correspondence between the real space application and its agent may be, for example, what kind of equipment exists in the real space, or when the real space application is operating in parallel with multiple processes. The corresponding agent cannot be determined as one. If one agent is associated with one real-space application, when there are two device sets and they are operating in different processes, the operations of both processes are confused and cannot be distinguished. Get up. On the other hand, if an agent is assigned in units of processes, there is a possibility that the operation as intended by the real space application cannot be realized. This restricts the operation mode (process configuration) of the real space application, which also causes a problem. These problems can be avoided by assigning an agent to each actual device combination (device set).

  Next, a modified example of the system shown in FIG. 5 will be described with reference to FIG. FIG. 8 is a diagram illustrating a configuration in which an agent is assigned to each device set. Here, only one set of devices 7 and 8 used by the real space application 1 exists in the room (FA2). For example, there are already other device sets formed of the devices 9 and 10. When there is one set, the agent corresponding to the real space application 1 assigns the agents SA31 and SA32 of the real space application 1 corresponding to each device set under the agent SA3 corresponding to the real space application 1, and under each of them. The agent agents DA51, DA52, DA53, DA54 corresponding to the device set are connected. Allocating an agent corresponding to the real space application 1 for each device set means taking such a configuration.

<Third Embodiment>
Next, a control system for a real space application service according to a third embodiment of the present invention will be described. FIG. 9 is a diagram illustrating the configuration of software and hardware in the third embodiment. In this figure, the same parts as those in the system shown in FIGS. 1 and 5 are denoted by the same reference numerals, and description thereof is omitted. The system shown in FIG. 9 is different from the systems shown in FIGS. 1 and 5 in that the two real space applications 11 and 12 are in a device competition state in which the same device 8 (DA 52) is to be used.

  Next, referring to FIG. 10, the real space application 11 uses the device 8 (DA52) and the device 9 (DA53) where the real space application 11 uses the device 7 (DA51) and the device 8 (DA52). A processing operation when the subsequent real space application 12 is started will be described. FIG. 10 is a flowchart showing the operation of the system shown in FIG. First, when the real space application 12 issues a request to use the devices 8 and 9 (step S71), it is determined whether the devices 8 and 9 are used by another real space application (step S72). If the device 8 or the device 9 is used as a result of this determination, the real space application 12 cannot be activated (step S76). On the other hand, when the device 8 or the device 9 is not used, the SA 32 secures a device to be used (step S73). Then, the profile of the HA 43 is updated (step S74), and the real space application is executed (step S75).

  Next, the details of the processing operations in steps S72 and S73 shown in FIG. 10 will be described with reference to FIG. FIG. 11 is a sequence diagram showing a processing operation for securing a device used by the real space application 12. First, the HA 43 transmits a trigger for starting a real space application to the SA 32 (step S81). In response to this, the SA 32 transmits an activation command to the real space application 12 (step S82). The real space application 12 returns an OK response after being activated (step S83). SA32 transmits a device occupation request to FA2 (step S84). The FA 2 corresponding to the room in which the device is installed holds information regarding whether or not the device is being used, and returns the occupation status of the device.

  Since the device 8 has already been used by the real space application 11, the FA 2 returns a response to the device occupation request such as “device 8 is NG and device 9 is OK” (step S85). In response to this, the SA 32 cannot occupy the device required by the real space application 12, and transmits an activation NG indicating that activation cannot be performed to the HA 43 (step S86). If both the device 8 and the device 9 are usable, the profile update of the device 8 and the device 9 is executed from the FA 2, and the real space application 12 becomes usable.

  Next, with reference to FIG. 12, the detail of the modification of the processing operation of step S72, S73 shown in FIG. 10 is demonstrated. First, the HA 43 transmits a trigger for starting a real space application to the SA 32 (step S91). In response to this, the SA 32 transmits an activation command to the real space application 12 (step S92). The real space application 12 returns an OK response after being activated (step S93). The SA 32 transmits a device occupation request to the DA 52 (step S94). Here, since the DA 52 is already occupied, the DA 52 returns NG indicating that it cannot be occupied (step S95). Subsequently, the SA 32 transmits a device occupation request to the DA 53 (step S96). Here, the DA 53 updates the profile (step S97), and returns OK indicating that it can be occupied as a response (step S98).

  Next, the SA 32 determines whether all the devices to be occupied can be occupied, and if not, sends a release request to the occupied device (DA 53 in this case) (step S99). The DA 53 updates the profile (step S100), and returns OK indicating that it has been released (step S101). In response to this, the SA 32 cannot occupy the device required by the real space application 12, and transmits an activation NG indicating that activation cannot be performed to the HA 43 (step S102). If both the device 8 and the device 9 are usable, the profile update of the device 8 and the device 9 is executed from the FA 2, and the real space application 12 becomes usable.

  As described above, the software agent (DA51, DA52, DA53) corresponding to the device has a function of holding the usage status of the responsible device, that is, which real space application is used as one item of the profile. Therefore, the real space application can know whether or not the device used by itself can be secured by inquiring the agent of the device. As a result, if it can be used, the device agent is informed that it wants to use it, and if the device agent permits, the profile is updated and the real space application can secure the device. Will be able to use.

  11 and 12, the real space application agent confirms the usage status of all the devices used by the agent of the real space application, and the real space is used when all of them are usable. In order to execute the application, it is possible to avoid improper application execution due to partial use of necessary equipment pointed out as a problem of the prior art. In addition, in this way, being occupied by the agent of the real space application that is a part of the system that controls the real space application means that the right to use the device from the real space application service temporarily after the system intervenes. It means that it is possible to take over. This enables an arbitration operation such as temporarily restricting execution of the real space application service when a conflict is detected. What has been described above is an execution example of “various processing that should be performed by recognizing a scenario unit” that cannot be realized by the conventional technology.

  The process for securing used devices shown in FIG. 11 can be executed when the agent in the location (room) manages the usage status of all the devices in the location, and the load is concentrated on the agent in the location. The used device reservation processing operation shown in FIG. 12 is a form in which this work is shared by the agent of the device. There is no functional difference between them, and the processing efficiency is affected by the number of devices placed in the place, the frequency of device competition, and the like. Therefore, the optimum one may be selected according to the assumed system configuration and performance requirements.

<Fourth embodiment>
Next, a control system for a real space application service according to a fourth embodiment of the present invention will be described. In the first to third embodiments described above, when the real space application is activated, the occupying process of the device to be used is executed, and continues to be occupied until the real space application is terminated. In the present embodiment, the occupancy process is not executed when the real space application is activated, the occupancy process is executed for the first time when the device operation occurs, and the occupancy is released when the device operation ends. As an example of such a real space application, it is conceivable to automatically turn on the lighting and the air conditioner when a room resident comes home. In other words, the device is operated in response to some event having a low occurrence frequency. In such a real space application, if activation and occupancy are executed at the same time, almost no device operation is performed, but the device is occupied and cannot be used by other real space applications. Invite a strange state. This embodiment is for avoiding such inefficient device use.

  Next, the execution processing operation of the real space application in the present embodiment will be described with reference to FIG. The configuration of software and hardware is the same as that shown in FIG. FIG. 13 is a sequence diagram showing the execution processing operation of the real space application in the present embodiment. First, HA4 transmits a trigger for starting real space application 1 to SA3 (step S111). In response to this, when SA3 transmits an activation command to real space application 1 (step S112), real space application 1 is activated and a response is returned to SA3 (step S113). When the response is returned, SA3 returns a response of activation OK to the activation trigger to HA4 (step S114). In response to this, the HA 4 updates the profile (step S115). By this processing operation, a standby state is entered (step S116).

  Next, when the real space application 1 transmits a device operation command to SA3 as necessary (step S117), SA3 transmits a device occupation request to FA2 (step S118), and FA2 When the device occupancy OK response is received (step S119), a device operation command is transmitted to DA5 (step S120). When the device operation is finished, SA3 transmits a device occupation release request to FA2 (step S121), and upon receiving a device occupation release OK response from FA2, SA3 makes a device occupation request to real space application 1. An OK response indicating that the release has been completed is returned (step S123).

  Next, HA4 transmits a trigger to end real space application 1 to SA3 (step S124). In response, when SA3 transmits a termination command to the real space application 1 (step S125), the real space application 1 is terminated and a response is returned to SA3 (step S126). When the response is returned, SA3 returns an end OK response to the end trigger to HA4 (step S127). In response to this, the HA 4 updates the profile (step S128).

  As described above, in the present embodiment, the device to be used is not occupied when the real space application 1 is activated, and is temporarily put on standby. In this state, when a device operation command is issued from the real space application 1, a device occupancy request is transmitted from the agent (SA3) of the real space application 1 to the agent (FA2) of the place, and if successful, device operation (DA5, DA6) ) Is executed, and when the operation is completed, the exclusive release is executed. Thereafter, this is repeated until an end request for the real space application 1 is received. In the present embodiment, the processing operation for occupying and releasing the device every time the device is operated has been described. However, as shown in the first to third embodiments, the real space application is activated. It may be mixed with devices that continue to occupy. Which method is adopted is defined for each device as profile information held by the agent (SA3) of the real space application 1.

  1, 5, 8, and 9 are recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into a computer system and executed. Thus, the real space application service control process may be performed. Here, the “computer system” includes an OS and hardware such as peripheral devices. The “computer system” includes a WWW system having a homepage providing environment (or display environment). The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Further, the “computer-readable recording medium” refers to a volatile memory (RAM) in a computer system that becomes a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. In addition, those holding programs for a certain period of time are also included.

  The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, what is called a difference file (difference program) may be sufficient.

  It can be applied to applications where it is indispensable to control real space application services realized by using various devices such as home appliances, sensors, actuators and the like connected to each other by a network such as the Internet.

  1 ... real space application, 2 ... FA (room agent), 3, 31, 32 ... SA (real space application agent), 4, 41, 42, 43 ... HA (human agent), 5, 6, 51, 52, 53, 54 ... DA (device agent), 7, 8, 9 ... device

Claims (12)

A system for controlling a real space application service provided by controlling a device connected to a network via a software agent,
The real space application service is implemented by the application software corresponding thereto is executed, the contents of the real space application services and to be able to freely alter the extent that can be written of the application software monitor, the Multiple application software can exist and operate simultaneously,
A software agent corresponding to each of the real space application service, a user of the system that controls the real space application service, the device, the real space application service, and a place where the real space application service is provided;
The software agent includes communication means for performing information communication with each other, storage means for storing information, and control means for controlling operation,
The storage means provided in the software agent corresponding to the place where the real space application service is provided includes the state of the place where the real space application service is provided, information on attributes, a list of devices installed in the place, For each of the devices, identification information of the real space application service that uses the device, information about the exclusive operation type that is executed prior to device operation,
The storage means comprises software agent corresponding to the device, wherein the device state information about the attributes, protocol information for communicating with the device, information about the command for operating the apparatus, the apparatus Identification information of the real space application service to be used and information on the exclusive operation type executed prior to device operation are retained,
The storage means provided in the software agent corresponding to the user holds information about the user's status and attributes, identification information of the real space application service enjoyed by the user,
The storage means included in the software agent corresponding to the real space application service includes information about the state and attributes of the device used by the real space application service, information for communicating with the software agent corresponding to the device, and the real space application. Service user identification information is retained,
The software agent corresponding to the location, the software agent corresponding to the device, the software agent corresponding to the user, and the software agent corresponding to the real space application service operate in cooperation, thereby avoiding device contention and the device. A system for controlling real-space application services, characterized by   The software agent corresponding to the real space application service has a tree structure in which a child software agent is connected under one parent software agent, and there is a child software agent for each combination of devices used by the real space application service. The system for controlling the real space application service according to claim 1, wherein one system is generated. The software agent corresponding to the location where the real space application service is provided holds information on the real space application service that uses the device for each device installed at the location,
The real space application service acquires the usage status of the device to be used by inquiring the software agent corresponding to the location where the real space application service is provided, via the software agent corresponding to the real space application service,
When not used for another real space application service, the device usage information held by the software agent corresponding to the place where the real space application service is provided is updated to obtain a right to use. A system for controlling a real space application service according to claim 1. The real space application service acquires the usage status of the device to be used by inquiring the software agent corresponding to the device via the software agent corresponding to the real space application service,
4. The right to use by updating the real space application service information that uses the device held by the device when the device is not used for another real space application service. A system for controlling a real space application service according to any one of the preceding claims. When the software agent corresponding to the real space application service occupies each device to be used, the software agent continues to occupy the device from the start of the real space application service until it ends or whenever the device is operated. The real space according to any one of claims 1 to 4, wherein information indicating whether to occupy and release the occupancy when the operation ends is stored as profile information of the device. A system that controls application services.   After the real space application service obtains the right to use the device required by itself, the device operation command and the input information from the device are communicated between the software agent corresponding to the device and the software agent corresponding to the device. The system for controlling a real space application service according to any one of claims 1 to 5, wherein the system transmits or receives via the system. A control method in a system for controlling a real space application service provided by controlling a device connected to a network via a software agent,
The real space application service is implemented by the application software corresponding thereto is executed, the contents of the real space application services and to be able to freely alter the extent that can be written of the application software monitor, the Multiple application software can exist and operate simultaneously,
A software agent corresponding to each of the real space application service, a user of the system that controls the real space application service, the device, the real space application service, and a place where the real space application service is provided;
The software agent includes communication means for performing information communication with each other, storage means for storing information, and control means for controlling operation,
The storage means provided in the software agent corresponding to the place where the real space application service is provided includes the state of the place where the real space application service is provided, information on attributes, a list of devices installed in the place, For each of the devices, identification information of the real space application service that uses the device, information about the exclusive operation type that is executed prior to device operation,
The storage means comprises software agent corresponding to the device, wherein the device state information about the attributes, protocol information for communicating with the device, information about the command for operating the apparatus, the apparatus Identification information of the real space application service to be used and information on the exclusive operation type executed prior to device operation are retained,
The storage means provided in the software agent corresponding to the user holds information about the user's status and attributes, identification information of the real space application service enjoyed by the user,
The storage means included in the software agent corresponding to the real space application service includes information about the state and attributes of the device used by the real space application service, information for communicating with the software agent corresponding to the device, and the real space application. Service user identification information is retained,
The software agent corresponding to the location, the software agent corresponding to the device, the software agent corresponding to the user, and the software agent corresponding to the real space application service operate in cooperation, thereby avoiding device contention and the device. A real space application service control method characterized by controlling   The software agent corresponding to the real space application service has a tree structure in which a child software agent is connected under one parent software agent, and there is a child software agent for each combination of devices used by the real space application service. 8. The real space application service control method according to claim 7, wherein one is generated. The software agent corresponding to the location where the real space application service is provided holds information on the real space application service that uses the device for each device installed at the location,
The real space application service acquires the usage status of the device to be used by inquiring the software agent corresponding to the location where the real space application service is provided, via the software agent corresponding to the real space application service,
When not used for another real space application service, the device usage information held by the software agent corresponding to the place where the real space application service is provided is updated to obtain a right to use. The real space application service control method according to claim 7 or claim 8. The real space application service acquires the usage status of the device to be used by inquiring the software agent corresponding to the device via the software agent corresponding to the real space application service,
10. The right to use by updating the real space application service information using the device held by the device when the device is not used for another real space application service. The real space application service control method according to any one of the preceding claims. When the software agent corresponding to the real space application service occupies each device to be used, the software agent continues to occupy the device from the start of the real space application service until it ends or whenever the device is operated. The real space according to any one of claims 7 to 10, wherein information indicating whether to use the occupancy and releasing the occupancy upon completion of the operation is stored as profile information of the device. Application service control method.   After the real space application service obtains the right to use the device required by itself, the device operation command and the input information from the device are communicated between the software agent corresponding to the device and the software agent corresponding to the device. The real space application service control method according to any one of claims 7 to 11, wherein the real space application service is transmitted or received.

Images