Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/02—Standardisation; Integration
  • H04L41/022—Multivendor or multi-standard integration
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L12/2803—Home automation networks
  • H04L12/2807—Exchanging configuration information on appliance services in a home automation network
  • H04L12/2809—Exchanging configuration information on appliance services in a home automation network indicating that an appliance service is present in a home automation network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L12/2803—Home automation networks
  • H04L12/2807—Exchanging configuration information on appliance services in a home automation network
  • H04L12/281—Exchanging configuration information on appliance services in a home automation network indicating a format for calling an appliance service function in a home automation network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/08—Configuration management of networks or network elements
  • H04L41/0803—Configuration setting
  • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
  • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/08—Configuration management of networks or network elements
  • H04L41/0893—Assignment of logical groups to network elements

Definitions

• the present invention relates to the configuration for the management, that is to say the monitoring and control, of devices of a system on the basis of management rules defining at least one action to be performed by said system when unless a condition is met.
• Consumer electronics devices with a network interface and remote-controllable home automation devices are proliferating. This makes it possible to offer new services to users, especially in a home or business premises.
• a management system that is to say, monitoring and control, can then be set up to manage its new services.
• Such a management system is able to detect devices in its environment and retrieve a description.
• UPnP Universal Plug and Play
• SSDP Simple Service Discovery Protocol
• a device indicates its presence by means of a message of the type SDDP NOTIFY.
• the control point of the system then transmits a request of the HTTP GET type and obtains in response, in XML format ⁇ eXtended Markup Language in English), a description of the states in which the device can be located and the functions that he has the opportunity to execute.
• the management system can be configured using ⁇ business rules ⁇ , also known as business rules. These management rules are defined by at least one condition and at least one action. Thus, when the condition of the management rule is fulfilled, the system implements the associated action, through a rules engine ⁇ business rules engine in English).
• the purpose of such a rule engine is to separate the business logic, that is to say the scenarios to be implemented, from the system logic. Thus, the business logic can evolve and be maintained separately from the application programming itself.
• a user can customize the behavior of his device management system, for example with regard to home automation or multimedia services.
• management rules requires technical skills to interpret events and messages generated within the management system and program the rules engine appropriately. It is then difficult, if not impossible without assistance to a user without these technical skills, to define new management rules and thus customize his environment as he pleases.
• the management systems of the state of the art thus lack flexibility, because of this limitation related to the technical skills required for programming rule engines and the interpretation of events and messages generated.
• the method is such that a configuration device obtains a description of states in which each apparatus of the system is able to find itself, and obtains a description of functions that each apparatus of the system is able to perform.
• the method is further such that the configuration device: transcribes said descriptions of states and functions into respective semantic expressions; provides said semantic expressions of states and functions to a user interface; allows a user, via the user interface, to define at least one management rule from at least one condition, based on the semantic state expressions, and at least one action, based on the semantic expressions of functions; and, transcribes each management rule, defined semantically via the user interface, into interpretable instructions by the rules engine.
• the user can define management rules, in a simple way that does not require skills related to the programming of rule engines, or the interpretation of events or messages. generated in the system.
• this semantic approach via the user interface allows the user to use a natural language to understand the possible states and functions in the system and allows him to define just as naturally the management rules to be applied by the system.
• the configuration device transcribes the description of the state or function into semantic expressions according to said different values.
• the configuration device transcribes said descriptions of states and functions into semantic expressions in a predetermined language from a choice of several languages available via the user interface.
• management rules is all the more natural for the user.
• the configuration device transcribes said descriptions of the states and functions into semantic expressions by using at least one correspondence dictionary between, for each apparatus according to its type, each state or function and a semantic expression corresponding.
• the configuration device allows the user, via the user interface, to define at least one management rule condition on the basis of a timestamp event or an activation event. user profile with said system.
• the configuration device allows the dissemination via the user interface of a management rule being defined, and the configuration device allows the broadcast via the user interface, for each device concerned by a defined condition or action, of a semantic expression corresponding to a name of said apparatus associated with a semantic expression corresponding to a verb representative of the state or of the function concerned by respectively said defined condition or action.
• the definition of the management rules is all the more natural for the user.
• the configuration device enables the automatic insertion, for the display of the management rule being defined, of semantic link expressions based on each defined condition or action.
• the configuration device allows, via the user interface, a selection of several devices, and allows to associate a condition or action to this selection of devices.
• the configuration device allows, via the graphical interface, the display of representations of said devices in groups established according to a geographical distribution of said devices and / or according to services provided by said apparatus.
• the configuration device receives descriptions of states and functions of the devices according to different protocols using different formats, and transcribes in a same format the received descriptions to obtain said descriptions of the states and functions.
• the invention also relates to a configuration device for managing devices of a system on the basis of management rules defining at least one action to be performed by said system when at least one condition is fulfilled, said system comprising an engine rules for implementing each of said management rules.
• the configuration device is such that it comprises: means for obtaining a description of states in which each device of the system has the possibility of being, and means for obtaining a description of functions that each device of the system has the possibility run.
• the configuration device is further such as to include: means for transcribing said descriptions of the states and functions into respective semantic expressions; means for providing said semantic statements of states and actions to a user interface; means for enabling a user, via the user interface, to define at least one management rule from at least one condition, based on the semantic state expressions, and at least one action, on the basis of semantic expressions of functions; and, means for transcribing each management rule, defined semantically via the user interface, into interpretable instructions by the rule engine.
• the invention also relates to a graphical interface for defining management rules for the management of devices of a system, each management rule defining at least one action to be performed by said system when at least one condition is fulfilled.
• the graphic interface is such that it comprises: a first display area intended to display representations of said apparatuses and to allow a user to select at least one of said apparatuses; a second display area for displaying semantic expressions representative of respective states in which at least one selected apparatus is able to be located and to allow a user to select; a third display area for displaying semantic expressions representative of functions that at least one selected apparatus has the ability to execute; and a fourth display area for displaying a management rule being defined.
• the GUI is further such that said second and third display areas are adapted to allow a user to define at least one management rule from at least one condition, based on semantic state expressions. displayed in the first display area, and at least one action, based on the semantic function expressions displayed in the second display area.
• the invention also relates to a computer program intended to be read by a computer system or a processor.
• This computer program includes instructions for implementing the method mentioned above in any of these implementation variants, when said program is executed by a computer system or a processor.
• the invention also relates to storage means comprising such a computer program.
• FIG. 1 schematically illustrates a device management system in which the invention can be implemented
• FIG. 2 schematically illustrates an architecture for a management system configuration device
• FIG. 3 schematically illustrates an architecture for a control unit of the management system comprising the configuration device
• FIG. 4 schematically illustrates an algorithm implemented by the configuration device, when detecting a topology change of the management system
• FIG. 5 schematically illustrates an algorithm implemented by the configuration device, when defining a management rule to be applied by the management system
• FIG. 6 schematically illustrates an algorithm implemented by the management system of FIG. 1 to apply a management rule
• FIG. 7 schematically illustrates a graphical interface allowing a user to define a management rule to be applied by the management system.
• Fig. 1 schematically illustrates a device management system 100 in which the invention can be implemented.
• the system 100 allows device management in a given environment.
• this example is the home environment of individuals, but can also be any other type of environment, such as a professional environment.
• the system 100 manages devices adapted for home automation, such as lamps, shutters or heaters, etc. a control unit 110 of the system 100 can remotely control and monitor.
• the system 100 manages devices providing multimedia services, such as a digital recorder, a set-top box, video cameras, etc. which can themselves also be controlled and monitored remotely by the control unit 110.
• the system 100 allows the management of devices that can be in different states, and next if the functions they offer are actually activated or not.
• a lamp-type device can be in a state "lit” (on English) or "off" ⁇ off in English) and provides the functions of activation and deactivation of lighting.
• the control unit 110 comprises a plurality of interfaces 111, 112, 113, based on communication technologies, whether wireless or wired.
• the interfaces 111, 112, 113 allow the control unit 110 to communicate with devices according to different protocols and / or via different communication media.
• the control unit 110 is thus connected to a device 121 via the interface 111, to the devices 131, 132, 133 via the interface 112 and to a device 122 via the interface 113.
• control unit 110 makes it possible to apply in the system 100 user-defined management rules.
• Fig. 2 schematically illustrates an architecture for a configuration device 200 of the management system 100.
• the configuration device 200 allows a user to define management rules to be enforced by the control unit 110.
• the configuration device 200 may be included in or separate from the control unit 110.
• the first case is that presented in FIG. 2.
• the control unit 1 10 includes a memory for storing the rules provided by the configuration device 200 and a rule engine for enforcement. Note that in this second case, it is not necessary for the configuration device 200 to include a rules engine, since the configuration device 200 is only used for the purpose of defining management rules and not for the purpose of enforcing them.
• the configuration device 200 includes a formatting module 210 for formatting received data as messages according to different protocols via a group of interfaces 305.
• the interface group 305 is shown in FIG. 3 and corresponds to all the interfaces 111, 112, 113 of the control unit 110.
• the configuration device 200 receives, from the devices of the system 100, state descriptions in which these devices have the opportunity to be, and descriptions of functions that these devices have the ability to perform. Since the configuration device 200 can receive these descriptions according to different protocols using different formats, the formatting module 210 transcribes in the same format the received descriptions. This allows the configuration device 200 to obtain state and function descriptions in a single format, independent of the communication technologies and protocols implemented.
• the formatting module 210 then makes it possible to simplify the subsequent transcription of these descriptions of states and functions into semantic expressions. It should be noted that the configuration device 200 may not include the formatting module 210 when the devices use the same communication protocol. The formatting module 210 further receives notifications or events from the system 100 devices, highlighting changes in state of these devices.
• the configuration device 200 includes a management module 208 of a list of all the devices of the system 100 and the services they offer.
• the configuration device 200 furthermore comprises a list 209 of the apparatuses of the system 100, the states in which they have the possibility of being and the functions they propose.
• the management module 208 is in charge of the management of the list 209, according to information received from the formatting module 210.
• the management module 208 also makes it possible to invoke functions with the apparatuses of the system 100.
• the configuration device 200 further comprises a manager module 207 of the actual states of the devices of the system 100 and monitoring these states.
• the manager module 207 thus obtains a representation of the effective context of the system 100. This context representation is maintained by the management module 207 as a function of the information provided by the management module 208, and possibly by a rules engine 202 of the configuration device 200.
• the rules engine 202 is in charge of applying the management rules, as they can be obtained by executing the algorithm described below in relation with FIG. 5.
• the rule engine 202 receives from the manager module 207 information about the occurrence of events that cause changes in the state of the devices of the system 100. When a management rule condition is fulfilled as a result of such a change of state. state, the rule engine 202 then requires the management module 208 to apply each action defined by this management rule, invoking the appropriate functions of the devices concerned.
• the rule engine 202 is for example JRuleEngine type, according to the document "JSR-94: Java Specification Request 94, version 1.1".
• the configuration device 200 further comprises a rule base 203. Once a management rule is defined, it is stored in semantic form for later display. This storage can be done in a dedicated storage unit (not shown in Fig. 2), or in the list 209 then extended to allow to store management rules in semantic form.
• the configuration device 200 further stores the management rule in the rule base 203, after transcription. This rule base 203 is then used by the rule engine 202 to determine, when a state change occurs in the system 100, if a management rule condition is fulfilled.
• the configuration device 200 further comprises a rule transcriber 204.
• the rule transcriber 204 transcribes the management rule, which is expressed in semantic form, into interpretable instructions by the rule engine 202. This transcription can be done using a Look-Up Table (LUT) .
• the rule translator 204 then stores the management rule transcribed in the rule base 203.
• the configuration device 200 may further comprise a semantic database 206, which serves as a correspondence dictionary between, for each device according to its type, each state or function and a corresponding semantic expression.
• the configuration device 200 may alternatively, or in addition to the semantic database 206, use a remote database (not shown) via a communication network. This makes it easier to update the dictionary following the appearance of new devices on the market.
• the semantic database 206 preferably comprises equivalent semantic expressions in several languages.
• the configuration device 200 furthermore comprises a rule editor 205.
• the rule editor obtains, for example via the manager module 207, a list of the devices of the system 100. It also obtains, for example via the manager module 207, a description of the states in which each device of the system 100 has the possibility to be, and a description of each function that each device of the system 100 is able to perform.
• the rule editor 205 then transcribes these descriptions into semantic expressions, using the semantic database 206. This makes it possible to obtain a description of the states and functions in natural language for the user.
• the semantic database 206 includes equivalent semantic expressions in several languages, the rule editor 205 makes it possible to perform the transcription according to a language chosen by the user.
• the configuration device 200 transcribes the description of the state or function into semantic expressions according to these different values.
• a lamp-type device can be turned on in several configurations: low intensity, intensity medium or high intensity.
• Two states can then be defined: “on” or “off”, with for the "on” state an attribute representative of the intensity.
• this apparatus can propose two functions "to increase the intensity” and “to decrease the intensity”, with each one an attribute representative of the intensity to be reached by application of the function.
• the configuration device 200 furthermore comprises a user interface management module 201.
• the management module 201 is in charge of interfacing the rule editor 205 with a graphic interface module 304.
• the management module 201 enables thus, the rule editor 205 provides the semantic expressions of the states and functions to the GUI module 304.
• the management module 201 further allows the rule editor 205 to provide the GUI module 304 the list of devices of the system 100.
• the management module 201 further allows the user, via the GUI module 304, to define at least one management rule from at least one condition, based on of these semantic state expressions, and at least one action, based on these semantic expressions of functions.
• the management module 201 then provides each condition and action defined to the rule editor 205.
• the configuration device 200 or the control unit 110 may make it possible to implement the configuration device 200 or the control unit 110.
• Each of these platforms then comprises an interface module with the other platform for exchanging the data necessary for managing the devices of the system 100.
• the interface between the two platforms can then be implemented by the use of Web protocols, for example HTTP (HyperText Transfer Protocol in English) or SOAP (Simple Object Access Protocol in English).
• All or part of the architecture shown in FIG. 2 and algorithms described below in relation to FIGS. 4 to 6 can be implemented in software form by executing a set of instructions by a programmable machine, such as a DSP (Digital Signal Processor in English), a microcontroller or a processor of type CPU (Central Processing Unit in English or Central Processing Unit in French).
• a programmable machine such as a DSP (Digital Signal Processor in English), a microcontroller or a processor of type CPU (Central Processing Unit in English or Central Processing Unit in French).
• all or part of the architecture shown in FIG. 2 and algorithms described below in relation to FIGS. 4 to 6 can be implemented under hardware form by a machine or a dedicated component, such as an FPGA (Field Programmable Gate Array) or an Application-Specific Integrated Circuit (ASIC). Application in French).
• FPGA Field Programmable Gate Array
• ASIC Application-Specific Integrated Circuit
• Fig. 3 schematically illustrates an architecture for the control unit 110 comprising the configuration device 200.
• the control unit 110 comprises, connected by a communication bus 310:
• processor 300 a processor, microprocessor, microcontroller or CPU 300;
• RAM Random Access Memory in English or Random Access Memory in French
• ROM Read Only Memory in English or Mémoire à Lire Seul in French
• a storage medium reader 303 such as a SD (Secure Digital Card) card reader;
• human-machine interface means and more particularly a graphical interface module 304 for managing the display of a graphical interface 700, an example of which is illustrated below in relation with FIG. 7;
• interface means 305 for communication with the apparatuses of the system 100, comprising in particular the interfaces 111, 112, 113.
• the CPU 300 is capable of executing instructions loaded into the RAM 301 from the ROM 302, an external memory (not shown), a storage medium, such as an SD card or the like, or a communication network.
• the control unit 110 When the control unit 110 is turned on, the CPU 300 is able to read instructions from RAM 301 and execute them.
• These instructions form a computer program which causes the CPU 300 to implement all or some of the algorithms described below in relation to FIGS. 4-6.
• Fig. 4 schematically illustrates an algorithm implemented by the configuration device 200, during the detection of a system topology change 100.
• a change of topology occurs when a device is disconnected from the system 100, when a device is connected for the first time to the system 100 or when a device is reconnected to the system 100.
• the algorithm starts in a step S401.
• the configuration device 200 detects a change of topology of the system 100.
• the configuration device 200 checks whether a device has been added to the system 100 relative to the context preceding the change of topology. If this is the case, a step S405 is performed; otherwise, a step S404 is performed.
• step S404 the configuration device 200 determines which device has been disconnected from the system 100 and removes it from the list of devices 209.
• the manager module 207 then updates the context information of the system 100. This information can be be propagated to the rule editor 205 so that it updates the user interface accordingly.
• the algorithm is then terminated in a step S409.
• step S405 the configuration device 200 obtains the name of the newly connected device or reconnected to the system 100. It also obtains a description of the states in which this device has the possibility to be and the functions it has the ability to run. For example, as already mentioned, a protocol based on the UPnP standard can be used for this purpose.
• the configuration device 200 performs a formatting of the descriptions obtained.
• the configuration device 200 when the configuration device 200 is adapted to receive descriptions of states and functions of the devices according to different protocols using different formats, the configuration device 200 transcribes in a same format the received descriptions. He thus obtains homogeneous descriptions of states and functions.
• the configuration device 200 transcribes the descriptions of the states and functions into respective semantic expressions, through the rule editor 205.
• the rule editor 205 thus allows the updating of the rules. user interface accordingly.
• step S408 the configuration device 200 updates the list of devices 209. Then, in step S409, the algorithm is terminated.
• Fig. 5 schematically illustrates an algorithm implemented by the configuration device 200, when defining a management rule.
• the algorithm starts in a step S501, during which the display of the graphical interface 700 is initialized.
• a step S501 the display of the graphical interface 700 is initialized.
• An example of such a graphical interface is described below with reference to FIG. 7.
• the configuration device 200 detects a selection, by the user via the graphic interface 700, of a device of the system 100. This selection can be made using a pointer or a pointer. 'a touch screen.
• the configuration device 200 makes it possible, via the graphic interface 700, to display representations of the devices in groups established according to their geographical distribution and / or according to the services they provide.
• the graphic interface 700 allows, from a list of devices, to indicate in which room of a dwelling each device is located and / or which service, eg multimedia or home automation, each device is relative.
• the configuration device 200 then retains this indication in the list of devices 209.
• the configuration device 200 detects that a management rule element type, i.e. condition or action, is selected for the device selected in step S502.
• This selection can be performed by drag and drop (drag-and-drop in English) an icon representative of the selected device in a first zone 710 of the graphic interface 700, intended for the definition of the conditions of the rule. management, or in a second area 720 of the graphic interface 700, for defining the actions of the management rule.
• the configuration device 200 obtains a semantic description of the states in which the selected apparatus is able to find itself or a description of the functions that it can execute.
• the description obtained depends on the type of management rule element, i.e. condition or action, selected in step S503.
• the configuration device 200 then makes it possible, in a next step S505, to update the display accordingly.
• the user obtains a visualization in the form of semantic expressions of the conditions or actions that he can use to define the management rule on the basis of the selected apparatus.
• the configuration device 200 detects a selection of a state or function from those displayed in step S505. A condition or action is thus defined. This means that the user has respectively selected a condition or an action to define the management rule.
• the configuration device 200 allows the display to be updated accordingly. An area 730 of the graphical interface 700, intended to display the management rule being defined, then makes the condition or the action appear in semantic form.
• the configuration device 200 allows the display of a semantic expression corresponding to a name of the selected apparatus associated with a semantic expression corresponding to a verb. representative of the state or action concerned. Referring to the example of the lamp already mentioned, the display may result in "the lamp is on” for a condition or "turn on the lamp” for an action.
• the configuration device 200 enables the automatic insertion, for the display of the management rule being defined, of semantic link expressions based on the condition or action.
• the display may result in "if the lamp is on” for a condition or "then turn on the lamp” for an action.
• Other semantic link expressions can be inserted.
• the configuration device 200 may make it possible to define several conditions for the same management rule. These conditions can be alternatives to trigger the action and in this case they are separated by the semantic expression "or”; on the contrary, they can be cumulative and in this case they are separated by the semantic expression "and”.
• the configuration device 200 can make it possible to define several actions for the same management rule. In this case, the different actions are separated by the semantic expression "and”.
• step S508 the configuration device 200 checks whether the definition of the rule is complete. If this is the case, a step S509 is performed; otherwise, step S502 is repeated.
• step S509 the configuration device 200 stores the rule in its semantic form, for example in the list 209, and transcribes the management rule into interpretable instructions by the rule engine 202.
• step S510 the device The configuration manager 200 stores the management rule transcribed in the rule base 203.
• a new management rule may be defined by repeating the algorithm from step S501.
• the configuration device 200 allows, via the graphic interface 700, a selection of several devices during the step S502. It then allows to associate a condition or action to all the devices of this selection. Then, in step 505, only the states or functions common to all the devices in the selection are displayed. Preferably, in step S507, when updating the display of the management rule being defined, a condition, or an action as the case may be, is displayed for each apparatus of the selection. This facilitates the subsequent transcription of the management rule into interpretable instructions by the rule engine 202.
• the configuration device 200 allows the user, via the graphical interface, to define at least one management rule condition based on a timestamp event. The system 100 then has a clock allowing the configuration device 200 to check if the condition based on the time stamp event is fulfilled.
• the user can set a condition with respect to a date, a given schedule on that date, a given schedule regardless of the date, a day of the week, and so on.
• the configuration device 200 allows the user, via the graphical interface, to define at least one management rule condition on the basis of an activation event of a user profile with the user.
• System 100 Radio Frequency Identification (RFID) technology (for Radio Frequency Identification in English or Radio Frequency Identification in French) can be used for this purpose. It makes it possible to store data on RFID tags or RFID tags. For example, the ISO 14443 A & B standards can be implemented. Thus, a user can activate his profile by placing the RFID tag that identifies him near a corresponding reader. In the same way, a user having a terminal equipped with NFC (Near Field Communication) technology, such as a mobile phone, can exchange information identifying him with respect to the system 200 equipped.
• NFC Near Field Communication
• the user can then define a condition relating to its presence or absence in the premises in which the system 100 is installed.
• Conditions defined on the basis of timestamp events or activation of a user profile can be combined with each other and / or combined with minus a state condition of a system apparatus 100 to define the management rule.
• Fig. 6 schematically illustrates an algorithm implemented by the control unit 110 to apply a management rule as defined by execution of the algorithm of FIG. 5.
• the algorithm starts in a step S601.
• the control unit 110 detects an event.
• This event may be related to a change of state of a device of the system 100, be a timestamp event or user profile activation as mentioned above.
• control unit 110 performs a step of checking the management rules that have been previously defined. More particularly, the rule engine 202 traverses the rule base 203. In a next step S604, the control unit 110 checks whether the detected event corresponds to a condition of a previously defined management rule. If this is the case, a step S605 is performed; otherwise, the algorithm is terminated in a step S606.
• This system operation with a forward chaining rules engine can be applied with a backward chained rules engine, that is, a motor that verifies that, for a given purpose, conditions are established.
• step S605 the control unit 110 performs the action defined in the management rule for which the condition, or all the conditions, are met. More particularly, the rule engine 202 instructs the management module 208 to invoke each function corresponding to the action, or actions, defined in the management rule. The algorithm is then terminated in step S606.
• Fig. 7 schematically illustrates an example of a graphical user interface 700 that allows the user to define a management rule.
• the graphic interface 700 comprises zones already mentioned: the zone 710 which is intended to define the conditions of the management rule; the area 720 which is intended for the definition of the actions of the management rule; and the area 730 which is intended for displaying the management rule being defined.
• the graphical interface 700 further comprises a zone 740 which is intended for the display of icons 742, 746, 747, 748 representative of the apparatuses of the system 100 which may be the subject of a condition or an action.
• the zone 740 may comprise several sub-areas 741, 745 in order to display the icons 742, 746, 747, 748 according to a geographical distribution of the devices in the system 100 and / or according to services provided by these devices.
• the zone 710 includes a sub-area 714 to deposit an icon 742, 746, 747, 748 representative of a device of the system 100.
• an icon 742, 746, 747, 748 representative of a device of the system 100.
• another sub-area 715 of area 710 is updated with a semantic description of each state in which the apparatus concerned may be located.
• This subfield 715 allows the user to choose from among these states to add one or more conditions to the management rule being defined.
• the zone 710 furthermore comprises at least one condition validation button
• the zone 710 includes two validation buttons: a first button to add an alternative condition to another condition of the management rule being defined, and a second button to add a cumulative condition to another condition of the management rule being defined.
• the area 720 includes a sub-area 724 to deposit an icon 742, 746, 747, 748 representative of a device of the system 100.
• a sub-area 724 to deposit an icon 742, 746, 747, 748 representative of a device of the system 100.
• another sub-area 725 of area 720 is updated with a semantic description of the functions offered by the apparatus concerned.
• This sub-area 725 allows the user to choose from these functions to add one or more actions to the management rule being defined.
• the area 720 further includes an action enable button (not shown) for selecting an action to define the management rule. If an action is already present in the management rule being defined, the validated action is added cumulatively to that already present.
• the graphic interface 700 may further comprise tabs 711, 712, 713 which are exclusively activated.
• the tab 711 is intended to activate the zone 710 to define a condition relating to a state of a device, or a selection of several devices, of the system 100.
• the tab 712 is intended to activate the zone 710 to define a condition for a timestamp event.
• Tab 713 is for enabling zone 710 to define a condition for user profile activation.
• the graphic interface 700 can furthermore make it possible to select several devices in the zone 740, and to simultaneously drag and drop the icons representing these devices into one of the sub-zones 714 and 724. In this case, the sub-zones 714 and 724 Zones 715 and 725 are respectively updated by the configuration device 200 with the semantic expressions of the states and functions that are common to the selected devices.
• the graphical interface 700 may further include a language selection menu.
• the user can choose a language from a set proposed by the configuration device 200 via the graphic interface 700.
• the configuration device 200 then transcribes the descriptions of the states and functions into semantic expressions in the selected language.
• the configuration device 200 does so in the selected language.
• the graphic interface 700 furthermore comprises a management rule validation button (not shown), which makes it possible to validate the management rule displayed in zone 730.
• the management rule is then stored in its semantic form, for example in the list 209, and transcribed into interpretable instructions by the rule engine 202, as previously described in relation to FIG. 5.
• the user interface can also be multimodal, and use a combination of graphic and voice inputs and outputs.
• the system can rely on the semantic terms covering the equipment, their functions and states, to define a dictionary of words that are preferentially recognized by a speech recognition engine.
• a user can speak to dictate a rule to the system, which then relies on the semantic dictionary to establish a multi-user voice recognition.
• the system can display via the GUI element 730 the semantic rule recognized by the system.
• the user interface can also be voice only.
• the management rule is then defined by voice recognition and the dissemination of the information relating to the devices of the system 100, the semantic expressions corresponding to the states and functions and the management rule being defined is done by voice synthesis rather than by by display.

Landscapes

• Engineering & Computer Science (AREA)
• Automation & Control Theory (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Human Computer Interaction (AREA)
• User Interface Of Digital Computer (AREA)
• Selective Calling Equipment (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Priority Applications (4)

Applications Claiming Priority (2)

Publications (1)

Family

ID=45757399

Family Applications (1)

Country Status (6)

Families Citing this family (9)

Citations (3)

Family Cites Families (3)

• 2011
  • 2011-03-22 FR FR1152337A patent/FR2973186A1/fr active Pending
• 2012
  • 2012-02-15 WO PCT/EP2012/052600 patent/WO2012126679A1/fr active Application Filing
  • 2012-02-15 EP EP12705827.9A patent/EP2689559B1/fr active Active
  • 2012-02-15 BR BR112013023788-0A patent/BR112013023788B1/pt active IP Right Grant
  • 2012-02-15 US US14/006,141 patent/US9654347B2/en active Active
  • 2012-02-15 CN CN201280014213.9A patent/CN103477590B/zh active Active

Patent Citations (3)

Also Published As

Similar Documents

Legal Events