Abstract:
The present invention relates to a system ( 100 ) for broadcasting targeted information for a home network (RD) to which at least one electronic device ( 4 ) including a processing means is connected, said broadcasting system including: at least one detector agent ( 1 ) for detecting a predefined event (E id ), said at least one detector agent ( 1 ) being arranged on the at least one electronic device ( 4 ); at least one selector agent ( 2 ) for selecting an action (A id ) to be performed, the at least one selector agent ( 2 ) being arranged on the at least one electronic device ( 4 ); and at least one broadcasting agent ( 3 ) for broadcasting targeted information content (Cid) for an end user ( 5 ), the at least one broadcasting agent ( 3 ) being arranged on the at least one electronic device ( 4 ). The detector ( 1 ), selector ( 2 ) and broadcasting ( 3 ) agents perform tasks in separate execution contexts on a processing means of the at least one electronic device ( 4 ) connected to the home network (RD).

Description:
TECHNICAL FIELD 
       [0001]    The present invention relates to a system for broadcasting targeted information for a home network connected to a remote network, such as the Internet, at least one electronic device being able to be connected to said home network, as well as a method for implementing such a system. 
       BRIEF DISCUSSION OF RELATED ART 
       [0002]    With the generalization of home networks of the Wi-Fi, Bluetooth, Zigbee, Ethernet or PLC (PowerLine Communication) type and compatible electronic devices used by the general public, a new generation of Internet services is developing that can be used without necessarily using a computer or smartphone. 
         [0003]    The list of devices connected in this way includes radios and television sets, recording and audiovisual broadcasting equipment such as video recorders, DVD/Blu-ray players or hi-fi components, tablets and digital photo frames, as well as electric household equipment, smart electric meters, and remote monitoring devices. 
         [0004]    The Internet connection allows these devices to access new services and content, benefit from remote updates, and provide information on their use. 
         [0005]    In particular, it becomes possible to use the connected devices to broadcast targeted content as a supplement to the usual broadcast channels comprising personal computers or smartphones. Furthermore, these devices may be provided with “sensors” that can be used to select the content based on events detected during their operation. 
         [0006]    For example, a television can record information on the type of content (channel, program, film) viewed by the user, a hi-fi component may know the user&#39;s musical taste, a smart electric meter can record the consumption history of electric devices, a refrigerator can prepare an inventory of stored products, a coffeemaker can indicate when the reserve is empty. This information can be used to perform actions making it possible to provide targeted contextual information to the user, for example targeted information for additional video content, a music album, an electricity offer adapted to the household&#39;s consumption, a promotional offer for a food product, or a coffee refill. 
         [0007]    The primary application of the broadcast of targeted content is the possibility of transmitting information according to the user&#39;s context, at the very moment when an event is detected in the environment. This type of contextual information is already widely used on computers, with the broadcast of information according to searches done by the user on his search engine or the history of sites visited, and on mobile telephones, with the broadcast of mobile information according to the user&#39;s location. 
         [0008]    However, several problems arise in implementing this “home contextual information.” 
         [0009]    First of all, the connected devices do not all have functions making it possible to sense usage information and carry out corresponding actions, such as displaying information. 
         [0010]    Some devices have advanced detection capacities (for example, an electric meter can provide information on the user&#39;s consumption habits, the type of devices connected to the electrical grid, or the need for maintenance), but most often have limited broadcast capacities; others, on the contrary, have expansive broadcast capacities, such as televisions or photo frames, but limited detection capacities. 
         [0011]    Additionally, targeting may require the use of information from several devices that must be analyzed before being used. 
         [0012]    Then, selecting the actions to be performed requires complex processing operations that may exceed the capacities of the connected objects. 
         [0013]    The performance of the selected actions may also require capacities using more than one device. 
         [0014]    Furthermore, selecting information based on events detected by home objects poses problems in terms of protecting user&#39;s privacy. 
         [0015]    In fact, the direct transmission of the data supplied by the objects connected to a remote server responsible for analyzing them, without the user having means of monitoring the transmitted information, runs the risk of that data being used inappropriately, while its storage outside the user&#39;s control contravenes the principles of protection of and access to private data. 
         [0016]    Lastly, when a piece of information triggers a transaction for a service, it must be possible to determine all of the events that led to that transaction so as to remunerate the various operators and improve the targeting process. 
         [0017]    The current solutions to this problem fall into several categories. Each device having connected functions is most often connected to a dedicated service platform operated by the manufacturer, which will be responsible for receiving information from the device. This platform may also be used to broadcast information related to the received information, either via the device itself, or using a device of the computer, tablet, or smartphone type. 
         [0018]    Another solution is the use of a controlled relay device by a third party operator, such as a box ADSL or a smart electric meter, to monitor the devices within the home network (electric grid or local network), detect events, and escalate them to a central server. That server will be responsible for analyzing them and initiating a broadcast of information by means of a device of the computer, tablet, or smartphone type. 
         [0019]    Lastly, a final solution comprises incorporating, on a smart terminal of the computer, tablet, or smartphone type, sensors or relays making it possible to communicate directly with each connected device. Upon request by the user, the smart terminal can read information on each home network device, notify a server that returns corresponding information to it, and display that information instantaneously on the screen of the terminal. 
         [0020]    Each solution currently proposed has its own limitations. Using a separate platform for each connected device makes it impossible to combine information coming from several devices to make the information more targeted. Furthermore, in the case where the device does not have broadcast functions, the broadcast of the information must be done using another channel, and requires that the user be connected on the platform or have previously entered his contact information thereon to be able to receive the supplied information. 
         [0021]    The use of a relay device controlled by a third party, such as an ADSL box or a smart electric meter, requires that all of the connected devices, irrespective of their manufacturer, be capable of communicating with the relay device, using the same communication network and the same protocols. Then, the broadcasting requires a central server capable of recovering the information from each relay device, selecting the existing information to be broadcast, and broadcasting it, which may be very greedy in terms of performance-related consumption in the event a large number of users and devices is being managed. Lastly, broadcasting of the information requires that the user have a specific device or have previously entered his contact information to be able to receive the information provided. 
         [0022]    In the various solutions currently proposed, the system is centralized and requires the use of a central server, generally connected to a single broadcast device, to which each device of the network must be connected and configured. 
         [0023]    The proper operation of the system with its connected home network is therefore dependent on the proper configuration and proper operation of the central server and the connection of each device of the home network thereto. 
         [0024]    The use of a terminal of the computer, tablet, or smartphone type to detect and select the information poses other problems. The device must have sensors or relays compatible with each connected device. The system only operates when the device is present and connected to the home network, which poses a problem in the case of a smartphone, which, by definition, is mobile, or a computer, which is not always turned on. 
         [0025]    The user must first initialize the device before it detects an event and broadcasts associated content. The device also does not have access to events that may have been detected before it was initialized. 
         [0026]    Lastly, irrespective of the selected solution, using a single centralized server outside the user&#39;s network to detect information in the area around the user and broadcast other information related thereto poses significant problems in terms of privacy protection. In fact, these methods lead to remote monitoring of the user, as well as storage on a remote server of the information continuously recovered from the user&#39;s network, then associating that information with the identity of the users so as to be able to target them. This means that these methods can easily be used inappropriately for harmful purposes, and contribute to hindering the adoption of these technologies by users concerned about protecting their privacy and security. 
       BRIEF SUMMARY 
       [0027]    The present invention aims to resolve all or some of the aforementioned drawbacks. 
         [0028]    To that end, the present invention relates to a system for broadcasting targeted information for a home network to which at least one electronic device including a processing means is connected, said broadcasting system including at least one detector agent for detecting a predefined event, said at least one detector agent being arranged on the at least one electronic device and being arranged to collect information generated by at least one physical sensor equipping the electronic device(s) following the detection of an event by the at least one physical sensor, to interpret that information using a local event database comprising a set of event definitions, to associate the event with an event data structure identified from among the set of event definitions, each being associated with a unique electronic event identifier, and to publish the electronic event identifier associated with the identified event in an event feed passing through the home network; at least one selector agent for selecting an action to be performed, the at least one selector agent being arranged on at least one electronic device and being arranged to collect the event feed passing through the home network, to interpret the electronic identifier associated with the identified event assimilated to the event feed using a local action database comprising a set of action definitions, to deduce therefrom the selection of an action from the set of action definitions as a function of the electronic identifier of the identified event, each being associated with a unique electronic action identifier, and to publish the electronic identifier associated with the selected action in an action feed passing through the home network; and at least one broadcasting agent for broadcasting targeted information content for an end user, the at least one broadcasting agent being arranged on at least one electronic device and being arranged to collect the action feed passing through the home network, to interpret the electronic action identifier associated with the selected action assimilated to the action feed, optionally using a local content database comprising a set of content definitions, to perform the action at a predetermined moment by broadcasting targeted information content according to the electronic identifier of the selected action to transmit the encrypted event, action, and content identifiers in the case of a transaction following the performance of the action, the detector, selector, and broadcasting agents performing tasks in separate execution contexts on processing means of the at least one electronic device connected to the home network. 
         [0029]    This arrangement makes it possible to combine information coming from several devices to perform customized actions. The selector agents may use events coming from several event feeds produced by different detector agents asynchronously to select the actions to be performed, and the broadcasting agents may also combine actions coming from several action feeds to broadcast content by combining it with local content. 
         [0030]    This arrangement also allows all of the “detector” devices, even those without broadcasting capacities, to be used to select content. The detector agents use the broadcasting agents to broadcast content, without requiring the presence of a central server responsible for recovering all of the events and initiating all of the actions, which is less costly in terms of server resources. This reduces prerequisites in terms of processing capacity for the detector agents, and therefore their cost, and eliminates the need for a central system for selecting and broadcasting content outside the user&#39;s network. 
         [0031]    Furthermore, this arrangement eliminates the need to have a central device in the home network such as a computer, tablet, or smartphone, that must remain continuously connected to the home network. Several multifunctional devices may be used as the “selector agent,” without requiring a broadcast capacity. This applies to “screenless” devices that are always active, such as Internet gateways (ADSL, optical fiber, cable) or smart electric meters. 
         [0032]    According to one embodiment, the home network may be connected to at least one remote server by means of an outside network, such as the Internet, and the data related to the identified events, selected actions, and broadcast content is stored locally and communicated outside the home network, anonymously and encrypted upon action by the home network user, to at least one remote server. 
         [0033]    According to one embodiment, the information contained in the local databases used by a first detector or selector agent is encrypted so as to prevent access to that information by a second selector or broadcasting agent arranged downstream of the first agent in a direction of communication of the data by the event feed and/or the action feed. 
         [0034]    According to one embodiment, the local event and/or action and/or content database receive(s) regular updates from one or more remote event and/or action and/or content databases, respectively. 
         [0035]    According to one embodiment, the local database(s) is (are) always connected to the remote database(s). 
         [0036]    According to one embodiment, the remote databases are centralized in a single remote database. 
         [0037]    According to one embodiment, the local databases are centralized in a single database. 
         [0038]    According to one embodiment, one or all of the local databases are outside the home network. 
         [0039]    According to one embodiment, the at least one detector, selector and broadcasting agents automatically connect to the external databases upon receipt of an event. 
         [0040]    According to one embodiment, the events not identified by the at least one detector agent are published in a specific feed, indicating all of the information collected by the at least one detector agent for each unidentified event. 
         [0041]    According to one embodiment, the specific feed is anonymously published upon authorization by the user at regular intervals to a remote database either by the detector agent, or by the selector agent. 
         [0042]    According to one embodiment, the broadcasting agent, such as a mobile telephone, is located outside the home network, but is accessible through a public and shared network, such as a GSM network. 
         [0043]    According to one embodiment, the at least one electronic device comprises compatible onboard software making it possible to exchange with at least one second electronic device. 
         [0044]    According to one embodiment, the onboard software uses protocols of the XML/IP type based on the UPnP, XMPP, and Atom/RSS standards. 
         [0045]    This arrangement allows the at least one electronic device to identify itself once it connects to the home network, and to thereby have an open system that easily makes it possible to add or remove agents of each type in a same network automatically using the “Plug &amp; Play” procedure. 
         [0046]    According to one embodiment, the at least one detector agent and the at least one selector agent each comprise a cache memory for the detected events and the actions to be performed, respectively. 
         [0047]    This arrangement makes it possible to combine both the real-time and asynchronous execution. The agents that are not accessible when the notification is issued may thus find the last events and actions on their own initiative, for example when they are reconnected to the network. 
         [0048]    This arrangement also allows the system to operate even when no Internet connection is available and to improve the reactivity of the system. In particular, this cache memory may be updated using technologies of the “broadcast” type (TV, radio, satellite, cable) without an Internet connection. 
         [0049]    The present invention also relates to a method for broadcasting targeted information for a home network to which at least one electronic device is connected comprising processing means, said method including, in this order, the steps of inventorying the at least one electronic device the first time the at least one electronic device is activated and each time the electronic device is connected to/disconnected from the home network, identifying the at least one electronic device connected to the home network, detecting an event and identifying an event using at least one detector agent comprising collecting information generated by at least one physical sensor equipping the electronic device(s) following the detection of an event by the at least one physical sensor, interpreting that information using a local event database comprising a set of event definitions, associating the event with an event data structure identified from among the set of event definitions, each being associated with a unique electronic event identifier, and publishing the electronic event identifier associated with the identified event in an event feed passing through the home network; selecting an action using a selector agent comprising collecting the event feed passing through the home network, interpreting the electronic identifier associated with the identified event assimilated into the event feed using a local action database comprising a set of action definitions, deducing the selection of an action from the set of action definitions according to the electronic identifier of the identified event, each being associated with a unique electronic action identifier, and publishing the electronic identifier associated with the selected action in an action feed passing through the home network; broadcasting targeted information content to an end user using at least one broadcasting agent comprising collecting the action feed passing through the home network, interpreting the electronic action identifier associated with the selected action assimilated to the action feed, optionally using a local content database comprising a set of content definitions, and performing the action at a predetermined moment by broadcasting the targeted information content as a function of the electronic identifier of the selected action. 
         [0050]    According to one alternative embodiment of the method, the step for broadcasting content to an end user using at least one broadcasting agent initiates a request to the at least one selector agent so that it updates its set of action definitions from one or more remote databases, then the at least one selector agent in turn initiates a request to the at least one detector so that it updates its set of event definitions from one or more remote databases. 
         [0051]    According to one alternative embodiment of the method, the step for selecting an action using a selector agent initiates a request to the at least one detector for it to update its set of event definitions from one or more remote databases. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0052]    In any case, the invention will be well understood using the following description in reference to the appended diagrammatic drawing, showing, as a non-limiting example, a broadcasting system according to the invention. 
           [0053]      FIG. 1  is a block diagram of the broadcasting system according to one embodiment of the invention. 
           [0054]      FIG. 2  is a block diagram illustrating the implementation of the so-called inventory step of the broadcasting method according to the invention. 
           [0055]      FIG. 3  is a block diagram illustrating the implementation of a so-called event detection and identification step of the broadcasting method according to the invention. 
           [0056]      FIG. 4  is a block diagram illustrating the implementation of a so-called action selection step of the broadcasting method according to the invention. 
           [0057]      FIG. 5  is a block diagram illustrating the implementation of a so-called broadcasting step for broadcasting content to an end user of the broadcasting method according to the invention. 
           [0058]      FIG. 6  is a block diagram illustrating a so-called transaction step that may be implemented following the implementation of the broadcasting method according to the invention. 
           [0059]      FIG. 7  is a block diagram of a so-called reconciliation step that may be implemented in parallel with the broadcasting method according to the invention. 
       
    
    
     DETAILED DESCRIPTION 
       [0060]    Tables providing examples of information exchanged between the various elements of the broadcasting system according to the invention are provided at the end of the description. 
         [0061]    As illustrated in  FIG. 1 , the system  100  is based on the use of three types of agents located within a same home network RD. 
         [0062]    A detector agent  1  recovers information  6  detected by physical sensors (operating message; electric, radio, light, sound signal) following an event E and interprets it using a local event database BE. 
         [0063]    The local database BE identifies an identified event data structure E id  from among the set EE of event definitions. 
         [0064]    In the rest of the description, the identified event data structure E id  will be designated as identified event E id . 
         [0065]    The detector agent  1  generates electronic identifiers id E  of the identified events E id  and publishes them in an event feed FE. 
         [0066]    That agent  1  also stores the notification addresses for the selector agent  2 . 
         [0067]    The detector agent  1  can receive regular updates from the event database BE from one or more remote databases BE′ through an update feed FE′. 
         [0068]    There may be one or more detector agents within a same home network RD. 
         [0069]    The event feed FE is received and analyzed by a selector agent  2 , which deduces the actions to be performed A id  therefrom using a local action database BA containing targeting rules, and broadcasts them in an action feed FA. 
         [0070]    The local action database BA is regularly updated from one or more remote databases BA′ through an update feed FA′. 
         [0071]    The selector agents  2  keep the list of addresses of the event feeds FE to which they subscribe. 
         [0072]    These agents  2  also store the notification addresses for the broadcasting agents  3 . 
         [0073]    There may be one or more selector agents  2  in a same home network RD. 
         [0074]    The action feed FA is received and analyzed by a broadcasting agent  3 , which performs the actions A id  at the desired moment to broadcast the content  8 , optionally using a local content database BC. 
         [0075]    In this case, the local content database BC is updated regularly from one or more remote databases BC′ through an update feed FC′. 
         [0076]    The broadcasting agents  3  keep the list of addresses of the action feeds FA to which they subscribe. 
         [0077]    There may be one or more broadcasting agents  3  in a same home network RD. 
         [0078]    The broadcast content  8  may optionally trigger one or more transactions T by the user  5  from a simple information request to a purchase, which makes it possible to generate revenue. 
         [0079]    Each initiated transaction T is associated with an identifier id T  formed from event id E , action id A , and content id O  identifiers having contributed to the initiation of the transaction T. 
         [0080]    This identifier id T  is stored by a remote transaction database BT′ and is associated with the revenue resulting from the initiated transaction. A reconciliation agent is used a posteriori, making it possible to remunerate the various parties. 
         [0081]    The three agents (detector  1 , selector  2 , broadcasting  3 ) are installed and operate within a home network RD of the user  5 , locally store the generated information, perform the analyses using local databases BE, BA, BC, which update themselves regularly from remote databases BE′, BA′, BC′. 
         [0082]    The updates are done anonymously; the information recovered during a transaction T is also anonymous and encrypted independently by each detector  1 , selector  2 , or broadcasting  3  agent. 
         [0083]    The method according to the invention is based on the use of these detector  1 , selector  2 , or broadcasting  3  agents embodied by compatible electronic devices  4  that communicate using predefined protocols, based on standard Internet protocols typically used for communication between computers. 
         [0084]    Several classes of agents are managed, an agent being able to be a dedicated physical piece of equipment or software installed on a multifunctional piece of equipment both comprising data processing means. 
         [0085]    In one embodiment, each electronic device  4  is equipped with compatible onboard software making it possible to exchange with the other electronic devices  4  using protocols of the XML/IP type based on the UPnP and Atom/RSS standards. 
         [0086]    One embodiment of a first step of the method according to the invention illustrated in  FIG. 2 , comprising taking an inventory of all of the electronic devices  4  connected to the home network RD, is carried out the first time the devices  4  are activated and upon each connection to or disconnection from the home network RD. 
         [0087]    This step comprises several execution tasks listed below and referenced in  FIG. 2 . 
         [0088]    (i): Upon each activation, the detector agent  1  inventories the available physical interfaces and the associated networks. 
         [0089]    Then, for each network, the detector agent  1  defines whether it is a private network (which can be used to broadcast an event feed FE, update notifications with connection to the remote event database BE′) or a public network (which may only be used to connect to the remote event database BE′). 
         [0090]    This choice is made automatically based on rules and may be modified manually. 
         [0091]    The aforementioned rules may relate to the type of physical interface used, the presence of security measures such as encryption, or the use of a particular addressing scheme. 
         [0092]    (ii): On each inventoried private network, the detector agent  1  broadcasts a notification using a specific protocol based on the uPnP protocol in order to signal itself to the other agents, by indicating its unique identifier, its class, its type, the supported protocols, the types of detectable events, the publication address where its event feed FE is published, and other optional parameters. 
         [0093]    The selector agents  2  present on the same private network determine, according to the supplied information, whether they wish to subscribe to the event feed FE that the detector agent  1  is producing, according to their processing capacities and other parameters. The process is initiated each time agents are reconnected to the home network RD. 
         [0094]    (iii): Optionally, on each inventoried private and public network, the detector agent  1  tries to connect to a remote event database BE′ using an update feed FE′ assuming the form of a connection of the http/IP type so as to update its local event database BE regularly. 
         [0095]    The address of the remote event database BE′ is pre-stored in the parameters of the device  4 , and several addresses may be predefined. Upon response from the remote event database BE′, the detector agent  1  provides its class, its type, and supported protocols. 
         [0096]    If the remote event database BE′ cannot respond to the request from the detector agent  1  due to incompatibility, it provides the detector agent  1  with another address to be used. 
         [0097]    If, on the contrary, the remote event database BE′ responds to the detector agent  1 , it indicates the protocol versions to be used, the update address(es), the update frequency, and other optional parameters. 
         [0098]    This information is stored by the detector agent  1 , and no information on the detector agent  1  is stored by the remote event database BE′. 
         [0099]    All exchanges between the detector agent  1  and the event database BE′ are also encrypted so as to prevent the interception of the information and use a data exchange protocol of the XML/Atom type. 
         [0100]    (iv): Optionally, if the detector agent  1  has functions making it possible to receive multicast content (TV, radio, satellite, cable), it connects on one or more predefined channels so as to receive updates regularly from the local event database BE from the remote database BE′. 
         [0101]    (v): Likewise, upon each activation, the selector agent  2  inventories the available physical interfaces in the associated networks. 
         [0102]    Then, for each network, the selector agent  2  defines whether it is a private network (which can be used to receive event notifications, broadcast action feeds, and connect to the remote action database BA′) or a public network (which may only be used to connect to the remote action database BA′). 
         [0103]    This choice is made automatically based on rules, and may be modified manually. 
         [0104]    The aforementioned rules may relate to the type of physical interface used, the presence of security measures such as encryption, or the use of a particular addressing scheme. 
         [0105]    (vi): On each inventoried private network, the selector agent  2  broadcasts a notification using a specific protocol based on the uPnP protocol so as to signal itself to the other agents, by indicating a unique identifier, the class and the type of agent, the address of the action feed FA and the notification address where the new events can be indicated, the supported protocol versions, and other optional parameters. 
         [0106]    Each detector agent  1  present stores the notification address of the selector agent  2  in a local database (not shown) so as to be able to notify it when the event feed FE is updated. 
         [0107]    The broadcasting agents  3  present on the same private network determine, according to information provided, whether they wish to subscribe to the action feed FA of the selector agent  2 , according to their processing capacities and other parameters. 
         [0108]    The process is initiated each time selector agents  2  are reconnected to the home network RD. 
         [0109]    (vii): On each inventoried private and public network, the selector agent  2  tries to connect to a remote action database BA′ using an update feed FA′ assuming the form of a connection of the http/IP type so as to update its local action database BA regularly. 
         [0110]    The address of the remote action database BA′ is pre-stored in the parameters of the device  4 , and several addresses may be predefined. 
         [0111]    Upon response from the remote action database BA′, the selector agent  2  provides its class, its type, the types of events and actions supported (according to information recovered from the detector  1  and broadcasting  3  agents), as well as the supported protocol versions. 
         [0112]    If the remote action database BA′ cannot respond to the request from the selector agent  2  due to incompatibility, it provides the selector agent  2  with another address to be used. 
         [0113]    If, on the contrary, the remote action database BA′ responds to the selector agent  2 , it indicates the versions of protocols to be used, the update address(es), the update frequency, and other optional parameters. 
         [0114]    This information is stored by the selector agent  2 ; no information on the selector agent  2  is stored by the remote action database BA′. 
         [0115]    Furthermore, all of the exchanges between the selector agent  2  and the action database BA′ are encrypted so as to prevent interception of the information and use a data exchange protocol of the XML/Atom type. 
         [0116]    (viii): Alternatively, if the selector agent  2  has functions making it possible to receive multicast content (TV, radio, satellite, cable), it connects on one or more predefined channels so as to receive updates regularly for the local action database BA from the remote database BA′. 
         [0117]    (ix): Likewise, upon each activation, the broadcasting agent  3  inventories the available physical interfaces and the associated networks. Then, for each network, the agent defines whether it is a private network (which can be used to receive updates from the action feed FA and connect to the remote content database BC′) or a public network (which can only be used to connect to the remote content database BC′). This choice is made automatically based on rules, and can be modified by manually. 
         [0118]    The aforementioned rules may pertain to the type of physical interface used, the presence of security measures such as encryption, or the use of a particular addressing scheme. 
         [0119]    (x): On each inventoried private network, the broadcasting agent  3  broadcasts a notification using a specific protocol based on the uPnP protocol in order to signal itself to the other agents, by indicating a unique identifier, the class and type of agent, the notification address of the actions, the supported protocol versions, the types of actions that can be executed, and other optional parameters. 
         [0120]    Each selector agent  2  present stores the notification address of the broadcasting agent  3  in a local database (not shown) so as to be able to notify it when the action feed FA is updated. 
         [0121]    (xi): Optionally, in the case where the broadcasting agent  3  is able to broadcast content  8  upon request, it is associated with a content database BC used to save content regularly found from one or more remote content databases BC′ using a content feed FC′ assuming the form of a connection of the http/IP type so as to update its local content database BC regularly. 
         [0122]    The address of the remote content database BC′ is pre-stored in the parameters of the device  4 , and several addresses may be predefined. Upon response from the remote content database BC′, the broadcasting agent  3  provides its class, its type, and the supported protocols. 
         [0123]    If the database cannot respond to the request from the broadcasting agent  3  due to incompatibility, it provides the broadcasting agent  3  with another address to be used. 
         [0124]    If, on the contrary, the remote content database BC′ responds to the broadcasting agent  3 , it indicates the protocol versions to be used, the update address(es), the update frequency, and other optional parameters. 
         [0125]    This information is stored by the broadcasting agent  3 , and no information on the broadcasting agent  3  is stored by the remote content database BC′. 
         [0126]    All of the exchanges between the broadcasting agent  3  and the remote content database BC′ are also encrypted so as to prevent the interception of information and use a data exchange protocol of the XML/Atom type. 
         [0127]      FIG. 3  illustrates a second so-called detection and interpretation step of the method according to the invention. 
         [0128]    This detection and interpretation step is carried out upon the detection of an event E by a detector agent  1 . 
         [0129]    This step comprises several execution tasks listed below and referenced in  FIG. 3 . 
         [0130]    (i): This step is initiated upon receipt of information  6  from sensors connected to the detector agent  1 . This receipt may be initiated by an initiating event E or at the initiative of the detector agent  1  itself. 
         [0131]    (ii): The detector agent  1  can optionally connect to the remote event database BE′, using the protocol of the Atom/RSS type, so as to update its local event database BE proactively. No information on the detector agent  1  is kept by the remote database BE′. 
         [0132]    (iii): The information recovered, stored in the form of manipulable files, is analyzed by the detector agent  1  using the local event database BE so as to translate it into an identified event E id  comprised in a set EE of event definitions according to a predefined nomenclature. 
         [0133]    (iv): Once the event E id  is identified, the detector agent  1  updates the event feeds FE by indicating the identifier id E  and the type of event, plus additional variables. 
         [0134]    The detector agent  1  integrates certain data from sensors used to identify the event E as well as its model identifier id E  (generic); this information is encrypted using a key provided by the remote event database BE′ and incorporated into the event feed FE. 
         [0135]    The event feed FE is stored in the form of a file of the RSS/XML type. The detector agent  1  then notifies all of the pre-recorded selector agent(s)  2  of the update to the event feed FE through a request of the HTTP/XML type at their notification address. 
         [0136]    (v): Following receipt of the update notification, or at its own initiative, each subscribed selector agent  2  connects to the event feed FE by means of an HTTP-type request so as to recover the information on the last detected event(s) E id . 
         [0137]      FIG. 4  illustrates a third so-called broadcasting step of the method according to the invention. 
         [0138]    This step is carried out following the receipt of an update notification of an event feed FE by a selector agent  2 . 
         [0139]    This step comprises several execution tasks listed below and referenced in  FIG. 4 , some being shared with the execution tasks of the previous step. 
         [0140]    (v): The selector agent  2  connects to the event feed(s) to which it is subscribed so as to recover the information on the last detected event(s) using a request of the HTTP type. The data is returned to it in the form of an RSS/XML type file. 
         [0141]    (vi): Optionally, following the reading of a new event E id  in any event feed FE, the selector agent  2  connects to the remote action database BA′ so as to update the local database BA containing the sets of rules using a request of the HTTP(s) type. 
         [0142]    (vii): The sets of rules are then evaluated by the selector agent  2  using the variables provided by the detector agent  1  in the event feed FE, the information stored by the selector agent  2 , and optionally user preferences. 
         [0143]    Each rule contains a list of conditions that the event E id  must satisfy and in light of a set EA of action definitions to be executed. The rule may apply to one or more events E id  coming from one or more detector agents  1 . 
         [0144]    For each action to be executed, a type is also provided as well as variables that will be determined by the selector agent  2  based on information stored in the event feed FE or information stored locally (such as the content or the user&#39;s personal data). 
         [0145]    (viii): Once the list of actions to be executed is determined, the selector agent  2  marks the event(s) E id  as “processed” and updates the action feed FA. 
         [0146]    For each action, it incorporates the identifiers id E  of the events used to select the action A id  as well as its model identifier id A  (generic). 
         [0147]    This information is encrypted using a key provided by the remote action database BA′ used. The action feed FA is stored in the form of a file of the RSS/XML type. 
         [0148]    The selector agent  2  then notifies all of the prerecorded broadcasting agents  3  of the update through a request of the http/XML type at their notification address. 
         [0149]    (ix): Following receipt of the update notification, or at its own initiative, each broadcasting agent  3  connects to the action feed FA by an http request so as to recover the information on the last action(s) A id  to be executed. 
         [0150]      FIG. 5  illustrates a fourth so-called broadcasting step of the method according to the invention. 
         [0151]    This step is carried out following receipt of an update notification of an action feed FA by a broadcasting agent  3 . 
         [0152]    This step comprises several execution tasks listed below and referenced in  FIG. 5 , some being shared with the execution tasks of the previous step. 
         [0153]    (ix): The broadcasting agent  3  connects to the action feed(s) FA to which it subscribes so as to recover the information on the last action(s) to be executed using a request of the http type. The data is returned to it in the form of a file of the RSS/XML type. 
         [0154]    (x): Optionally, the broadcasting agent  3  can connect to a remote content database BC′ so as to update the local database BC using a request of the http(s) type. 
         [0155]    (xi): Following the detection of one or more new actions A id  to be executed, the broadcasting agent  3  plans its execution. 
         [0156]    It verifies that another identical or contradictory action A id  is not planned at the same moment. Depending on the capacities of the broadcasting agent  3 , these tasks are performed upon receipt of the actions A id  or when they are executed. 
         [0157]    (xii): Optionally, the broadcasting agent  3  can connect to a local content database BC so as to find content therein to be used to execute the actions A id . 
         [0158]    The identifier id C  of the content or the feed to be used is found in the variables associated with the action A id  to be executed transmitted in the action feed FA. 
         [0159]    (xiii): At the planned moment, the broadcasting agent  3  performs the program action A id  with its parameters. 
         [0160]    The action A id  may be of multiple types depending on the capacities of the broadcasting agent  3 : selection of a particular channel in the case of a device  4  having functions making it possible to receive multicast content  8  (TV, radio, satellite, cable), broadcasting of content  8 , display of a dialogue with the user  5 , execution of an application, etc. 
         [0161]    Once the action A id  is performed, the broadcasting agent  3  marks it as processed. 
         [0162]    The targeted information broadcasting method according to the invention may lead to additional transactions T for a service illustrated in  FIG. 6 . 
         [0163]    This step is carried out after the execution of an action A id  by a broadcasting agent  3 . 
         [0164]    This step comprises several execution tasks listed below and referenced in  FIG. 6 . 
         [0165]    (xiv): During the execution of the action A id  by the broadcasting agent  3 , the user  5  can choose to initiate a transaction T on an external transaction system  7  (operated by a third party) and referenced in the parameters of the action, for example a website. 
         [0166]    The address of this transaction system  7  is associated with the broadcast content  8 , in the form of a URL hypertext link, for example. 
         [0167]    Upon connection, the information on the executed action A id  is also sent to the transaction system  7 . 
         [0168]    This includes the identifiers of the content id C  and actions id A  that were used as well as the model identifier id E  (generic). This information is encrypted using a key provided by the content database BC′ used. 
         [0169]    The initiation of the transaction T may also be recorded as an event E so as to be reused by the system  100  to select other actions A id . 
         [0170]    (xv): The transaction system  7  sends the remote transaction database BT′ the details of the transaction T as well as the data for the executed action A id . 
         [0171]    (xvi): The remote transaction database BT′ calculates, from the supplied elements, the amount due by the third party operating the transaction system  7  for that transaction T. 
         [0172]    This amount may be a fixed fee per transaction T, a percentage of the amount generated by the transaction T, etc. 
         [0173]    (xvii): The remote transaction database BT′ uses the identifiers of the agents associated with the transaction T to calculate the portion of the revenue from the transaction T due to each protagonist according to predefined rules. 
         [0174]    Lastly, the targeted information broadcasting method according to the invention can lead to a final additional step, called a reconciliation step, illustrated in  FIG. 7 . 
         [0175]    This step is executed at regular intervals at the initiative of the remote transaction database BT′. 
         [0176]    This step comprises several execution tasks listed below and referenced in  FIG. 7 . 
         [0177]    (xviii): The remote transaction database BT′ sends each identified remote content database BC′ (using database identifiers provided in each transaction T) a statement summarizing the revenues generated over the elapsed period for each type of broadcasting agent  3  and each content identifier id C . 
         [0178]    After decrypting the information using a unique key, each remote transaction database BT′ uses that information to remunerate the intermediaries (e.g., content suppliers, manufacturers or operators of broadcasting devices). 
         [0179]    (xix): The remote transaction database BT′ sends each identified remote action database BA′ (using database identifiers provided in each transaction T) a statement summarizing the revenue generated over the elapsed period for each type of selector agent  2  and each action identifier id A . 
         [0180]    After decrypting the information using a unique key, each remote transaction database BT′ uses this information to remunerate the intermediaries (e.g., manufacturers or operators of selector devices). 
         [0181]    (xx): The remote transaction database BT′ sends each remote event database BE′ (using database identifiers provided in each transaction T) a statement summarizing the revenue generated over the elapsed period for each type of detector agent  1  and each event identifier id E . 
         [0182]    After decrypting the information using a unique key, each remote transaction database BT′ uses this information to remunerate the intermediaries (e.g., manufacturers or operators of detector devices). 
         [0183]    Thus, the primary interest of the method related to the usage is the protection of privacy, which is ensured on several levels. 
         [0184]    The remote databases do not store any information on the user  5  for the devices  4  used; they operate in a “passive” mode and are queried by the home agents at regular intervals, based on the update model for Internet-based update feeds. 
         [0185]    The databases outside the home network RD do not know the identity of the agents of the home network RD, and cannot determine which event E id , action A id  or content C id  was actually processed during a broadcast for a particular user  5 . 
         [0186]    In the case of devices  4  having multicast functions, the updates are downloaded without any connection of the local agents to the remote database. 
         [0187]    All of the data related to the identified events E id  and the executed actions A id  is stored locally and is only communicated outside the home network RD in case of a transaction T, upon action by the user  5 . 
         [0188]    Furthermore, each downstream agent cannot access the information used by an upstream agent, the information being encrypted. 
         [0189]    The detector agent  1  does not have access to the stored data of the user  5  and can only use the data from received events E to identify it, using a local database BE. 
         [0190]    The transmitted information from the sensors is encrypted and can only be interpreted by the corresponding event database BE′. 
         [0191]    The information outlined on the detected events E id  as well as the history are not transmitted by the selector agent  2 . 
         [0192]    All of the selection rules for the actions A id  are executed locally. The information transmitted on the actions is encrypted and can only be interpreted by the corresponding action database BA′. 
         [0193]    The broadcasting agent  3  cannot access the initial event data E that led to the choice to broadcast the targeted information  8  or the rules that were used to select the broadcast of the targeted information  8 , which is encrypted. 
         [0194]    The information transmitted outside the home network RD is not personal and does not make it possible to determine which specific agent or user  5  generated it. 
         [0195]    It is aggregated by the remote transaction database BT′ and encrypted so as only to be able to be interpreted by the corresponding databases. 
         [0196]    Although the invention has been described relative to specific examples and embodiments, it is of course in no way limited thereto, and on the contrary encompasses all technical equivalents of the described steps and means. 
         [0197]    The following information is provided by the agent  1  to the selector agent(s)  2  using a file of the XML type: 
         [0000]    
       
         
               
               
               
             
           
               
                   
               
               
                 Information 
                 Description 
                 Example 
               
               
                   
               
             
             
               
                 Class 
                 Detector agent 
                 “detector” 
               
               
                 Protocol 
                 Version of the protocol, including 
                 “version 1.0” 
               
               
                   
                 the nomenclature of types, 
                   
               
               
                   
                 events, and actions 
                   
               
               
                 Type 
                 Type of agent, defining the 
                 “audio” 
               
               
                   
                 capacities of the agent broadly 
                   
               
               
                   
                 speaking 
                   
               
               
                 Events 
                 Types of events that can be 
                 “sound,” “music,” 
               
               
                   
                 detected. 
                 “radio” 
               
               
                 Address of 
                 Address where the event feed is 
                 “http://192.168.1.22/ 
               
               
                 the feed 
                 published by the detector agent 
                 eventFeed” 
               
               
                   
               
             
          
         
       
     
         [0198]    The following information may optionally be provided by the detector agent  1  to the remote event database BE′ so as to receive the updates for the local event database BE using a file of the XML type: 
         [0000]    
       
         
               
               
               
             
           
               
                   
               
               
                 Information 
                 Description 
                 Example 
               
               
                   
               
             
             
               
                 Class 
                 Detector agent 
                 “detector” 
               
               
                 Protocol 
                 Version of the protocol, including the 
                 “version 1.0” 
               
               
                   
                 nomenclature of types, events, and 
                   
               
               
                   
                 actions and the exchange protocols 
                   
               
               
                   
                 between agents 
                   
               
               
                 Type 
                 Type of agent, defining the 
                 “audio” 
               
               
                   
                 capacities of the agent broadly 
                   
               
               
                   
                 speaking 
                   
               
               
                 Events 
                 Types of events that can be 
                 “sound,” “music,” 
               
               
                   
                 detected. 
                 “radio” 
               
               
                   
               
             
          
         
       
     
         [0199]    The following information is returned by the remote event database BE′ depending on the types of events that may be detected using a file of the XML type: 
         [0000]    
       
         
               
               
               
             
           
               
                   
               
               
                 Information 
                 Description 
                 Example 
               
               
                   
               
             
             
               
                 Address 1 
                 Address where the updates of 
                 “https://update1.serveur.net/ 
               
               
                   
                 the local event database are 
                 var1” 
               
               
                   
                 published 
                   
               
               
                 Frequency 
                 Update frequency 
                 1 hour 
               
               
                 Encryption 
                 Encryption keys to be used 
                 {key} 
               
               
                 keys 
                 with the information provided 
                   
               
               
                   
                 by the remote event database 
                   
               
               
                 Database ID 
                 Unique identifier of the local 
                 event1 
               
               
                   
                 event database 
                   
               
               
                 Address n 
                 Address where the updates for 
                 “https://updaten.serveur.net/ 
               
               
                   
                 the local event database are 
                 var2” 
               
               
                   
                 published 
                   
               
               
                 Frequency 
                 Update frequency 
                 1 hour 
               
               
                 Encryption 
                 Encryption keys to be used 
                 {key} 
               
               
                 keys 
                 with the information provided 
                   
               
               
                   
                 by the remote event database 
                   
               
               
                 Database ID 
                 Unique identifier of the local 
                 eventn 
               
               
                   
                 event database 
               
               
                   
               
             
          
         
       
     
         [0200]    Subsequently, the detector agent  1  regularly updates the local event database BE by connecting to the addresses provided by the remote database BE′ at the indicated frequencies, using a protocol of the Atom/RSS type. The local event database BE can also be updated during the operation of the detector agent  1 . 
         [0201]    The following information is provided by the selector agent  2  to the broadcasting agents  3  using a file of the XML type: 
         [0000]    
       
         
               
               
               
             
           
               
                   
               
               
                 Information 
                 Description 
                 Example 
               
               
                   
               
             
             
               
                 Class 
                 Selector agent 
                 “selector” 
               
               
                 Protocol 
                 Version of the protocol, including 
                 “version 1.0” 
               
               
                   
                 the nomenclature of types, 
                   
               
               
                   
                 events, and actions and the 
                   
               
               
                   
                 exchange protocols between 
                   
               
               
                   
                 agents 
                   
               
               
                 Type 
                 Type of agent, defining the 
                 “multifunctional” 
               
               
                   
                 capacities of the agent broadly 
                   
               
               
                   
                 speaking 
                   
               
               
                 Address of 
                 Address where the event feed is 
                 “http://192.168.1.23/ 
               
               
                 the feed 
                 published by the selector agent 
                 actionFeed” 
               
               
                   
               
             
          
         
       
     
         [0202]    The following information is provided by the selector agent  2  to the detector agents  1  in order to receive the update notifications for the event feeds FE using a file of the XML type: 
         [0000]    
       
         
               
               
               
             
           
               
                   
               
               
                 Information 
                 Description 
                 Example 
               
               
                   
               
             
             
               
                 Class 
                 Selector agent 
                 “selector” 
               
               
                 Protocol 
                 Version of the protocol, including 
                 “version 1.0” 
               
               
                   
                 the nomenclature of types, 
                   
               
               
                   
                 events, and actions and the 
                   
               
               
                   
                 exchange protocols between 
                   
               
               
                   
                 agents 
                   
               
               
                 Type 
                 Type of agent, defining the 
                 “multifunctional” 
               
               
                   
                 capacities of the agent broadly 
                   
               
               
                   
                 speaking 
                   
               
               
                 Notification 
                 Address where the detector agent 
                 “http://192.168.1.23/ 
               
               
                 address 
                 can notify the selector agent of a 
                 eventNotif” 
               
               
                   
                 new event 
               
               
                   
               
             
          
         
       
     
         [0203]    The following information is provided by the selector agent  2  to the remote action database BA′ so as to receive the updates for the local action database BA using a file of the XML type: 
         [0000]    
       
         
               
               
               
             
           
               
                   
               
               
                 Information 
                 Description 
                 Example 
               
               
                   
               
             
             
               
                 Class 
                 Selector agent 
                 “selector” 
               
               
                 Protocol 
                 Version of the protocol, including the 
                 “version 1.0” 
               
               
                   
                 nomenclature of types, events, and 
                   
               
               
                   
                 actions and the exchange protocols 
                   
               
               
                   
                 between agents 
                   
               
               
                 Type 
                 Type of agent, defining the 
                 “multifunctional” 
               
               
                   
                 capacities of the agent broadly 
                   
               
               
                   
                 speaking 
                   
               
               
                 Events 
                 Types of events that can be 
                 “sound,” “music,” 
               
               
                   
                 detected, based on the types 
                 “radio” 
               
               
                   
                 supported by the event feeds to 
                   
               
               
                   
                 which the selector agent subscribes. 
                   
               
               
                 Actions 
                 Types of actions that can be 
                 “sound” “video” 
               
               
                   
                 executed, based on the types 
                 “TV” 
               
               
                   
                 supported by the broadcasting 
                   
               
               
                   
                 agents that subscribe to the action 
                   
               
               
                   
                 feed 
               
               
                   
               
             
          
         
       
     
         [0204]    The following information is returned by the remote action database BA′ according to the types of events and actions supported using a file of the XML type: 
         [0000]    
       
         
               
               
               
             
           
               
                   
               
               
                 Information 
                 Description 
                 Example 
               
               
                   
               
             
             
               
                 Address 1 
                 Address where the updates of 
                 “https://update1.serveur.net/ 
               
               
                   
                 the database are published 
                 var1” 
               
               
                 Frequency 
                 Update frequency 
                 1 hour 
               
               
                 Encryption 
                 Encryption keys to be used 
                 {key} 
               
               
                 keys 
                 with the information provided 
                   
               
               
                   
                 by the database 
                   
               
               
                 Database ID 
                 Unique identifier of the action 
                 action1 
               
               
                   
                 database 
                   
               
               
                 Address n 
                 Address where the updates for 
                 “https://updaten.serveur.net/ 
               
               
                   
                 the database are published 
                 var2” 
               
               
                 Frequency 
                 Update frequency 
                 1 hour 
               
               
                 Encryption 
                 Encryption keys to be used 
                 {key} 
               
               
                 keys 
                 with the information provided 
                   
               
               
                   
                 by the database 
                   
               
               
                 Database ID 
                 Unique identifier of the action 
                 actionn 
               
               
                   
                 database 
               
               
                   
               
             
          
         
       
     
         [0205]    Subsequently, the selector agent  2  regularly updates the local action database BA by connecting to the addresses provided by the remote database BA′ at the indicated frequencies, using a protocol of the Atom/RSS type. 
         [0206]    The following information is provided by the broadcasting agent  3  to the selector regions  2  in order to receive the update notifications for the action scenes FA using a file of the XML type: 
         [0000]    
       
         
               
               
               
             
           
               
                   
               
               
                 Information 
                 Description 
                 Example 
               
               
                   
               
             
             
               
                 Class 
                 Broadcasting agent 
                 “broadcasting” 
               
               
                 Protocol 
                 Version of the protocol, including 
                 “version 1.0” 
               
               
                   
                 the nomenclature of types, 
                   
               
               
                   
                 events, and actions and the 
                   
               
               
                   
                 exchange protocols between 
                   
               
               
                   
                 agents 
                   
               
               
                 Type 
                 Type of agent, defining the 
                 “video” 
               
               
                   
                 capacities of the agent broadly 
                   
               
               
                   
                 speaking 
                   
               
               
                 Actions 
                 Types of actions that can be 
                 “sound” “video” 
               
               
                   
                 executed 
                 “TV” 
               
               
                 Notification 
                 Address where the detector 
                 “http://192.168.1.23/ 
               
               
                 address 
                 agent can notify the selector 
                 actionNotif” 
               
               
                   
                 agent of a new action 
               
               
                   
               
             
          
         
       
     
         [0207]    The following information may optionally be provided by the broadcasting agent  3  to the remote content database BC′ so as to receive the updates for the local content database BC using a file of the XML type: 
         [0000]    
       
         
               
               
               
             
           
               
                   
               
               
                 Information 
                 Description 
                 Example 
               
               
                   
               
             
             
               
                 Class 
                 Broadcasting agent 
                 “broadcasting” 
               
               
                 Protocol 
                 Version of the protocol, including 
                 “version 1.0” 
               
               
                   
                 the nomenclature of types, events, 
                   
               
               
                   
                 and actions and the exchange 
                   
               
               
                   
                 protocols between agents 
                   
               
               
                 Type 
                 Type of agent, defining the 
                 “video” 
               
               
                   
                 capacities of the agent broadly 
                   
               
               
                   
                 speaking 
                   
               
               
                 Actions 
                 Types of actions that can be 
                 “sound” “video” “TV” 
               
               
                   
                 executed 
               
               
                   
               
             
          
         
       
     
         [0208]    The following information is returned by the remote content database BC′ based on the information provided using a file of the XML type: 
         [0000]    
       
         
               
               
               
             
           
               
                   
               
               
                 Information 
                 Description 
                 Example 
               
               
                   
               
             
             
               
                 Address 1 
                 Address where the updates of 
                 “https://update1.serveur.net/ 
               
               
                   
                 the database are published 
                 var1” 
               
               
                 Frequency 
                 Update frequency 
                 1 hour 
               
               
                 Encryption 
                 Encryption keys to be used 
                 {key} 
               
               
                 keys 
                 with the information provided 
                   
               
               
                   
                 by the database 
                   
               
               
                 Database ID 
                 Unique identifier of the action 
                 content1 
               
               
                   
                 database 
                   
               
               
                 Address n 
                 Address where the updates for 
                 “https://updaten.serveur.net/ 
               
               
                   
                 the database are published 
                 var2” 
               
               
                 Frequency 
                 Update frequency 
                 1 hour 
               
               
                 Encryption 
                 Encryption keys to be used 
                 {key} 
               
               
                 keys 
                 with the information provided 
                   
               
               
                   
                 by the database 
                   
               
               
                 Database ID 
                 Unique identifier of the action 
                 contentn 
               
               
                   
                 database 
               
               
                   
               
             
          
         
       
     
         [0209]    The following information may be provided by the detector agent  1  for each event recorded in the event feed FE; the format of the feed is of the XML/RSS type. 
         [0000]    
       
         
               
               
               
             
           
               
                   
               
               
                 Information 
                 Description 
                 Example 
               
               
                   
               
             
             
               
                 Protocol 
                 Version of the protocol, including 
                 “version 1.0” 
               
               
                   
                 the nomenclature of types, events, 
                   
               
               
                   
                 and actions and the exchange 
                   
               
               
                   
                 protocols between agents 
                   
               
               
                 Timestamp 
                 Date and time of the event 
                 “2010-03-15 20:05:15 GMT” 
               
               
                 Event 
                 Type of event detected 
                 “device_on” 
               
               
                 Event identifier 
                 Identifier of the detected event, 
                 “XX-121-3338” 
               
               
                   
                 generated by the event database, 
                   
               
               
                   
                 which can be interpreted by the 
                   
               
               
                   
                 selector agent 
                   
               
               
                 Event variables 
                 Variables associated with the 
                 “heater,” “30 min,” “priority 1” 
               
               
                   
                 event 
                   
               
               
                 Detector agent ID 
                 Model of the detector agent, used 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 during the reconciliation phase 
                   
               
               
                 Sensor identifiers 
                 Information used to detect the 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 event, encrypted by the detector 
                   
               
               
                   
                 agent using the key of the event 
                   
               
               
                   
                 database having provided the 
                   
               
               
                   
                 identification rules used. 
                   
               
               
                 Database ID 
                 Identifier of the event database 
                 event1 
               
               
                   
                 used 
               
               
                   
               
             
          
         
       
     
         [0210]    The following information may be provided by the selector agent  2  to the broadcasting agents  3  for each action indicated in the action feed FA; the format of the feed is of the XML/RSS type. 
         [0000]    
       
         
               
               
               
             
           
               
                   
               
               
                 Information 
                 Description 
                 Example 
               
               
                   
               
             
             
               
                 Protocol 
                 Version of the protocol, including 
                 “version 1.0” 
               
               
                   
                 the nomenclature of types, events, 
                   
               
               
                   
                 and actions and the exchange 
                   
               
               
                   
                 protocols between agents 
                   
               
               
                 Timestamp 
                 Date and time of the event 
                 “2010-03-15 20:05:15 GMT” 
               
               
                 Action 
                 Type of action to be executed 
                 “playvideo” 
               
               
                 Action identifier 
                 Identifier of the action to be 
                 “REET-TTR21” 
               
               
                   
                 executed generated by the action 
                   
               
               
                   
                 database, which may be 
                   
               
               
                   
                 interpreted by the broadcasting 
                   
               
               
                   
                 agent 
                   
               
               
                 Action variables 
                 Variables associated with the 
                 “12,” “20:35,” “Priority 1” 
               
               
                   
                 action, including the execution 
                   
               
               
                   
                 date, priority, scenario in case of 
                   
               
               
                   
                 error, address of the associated 
                   
               
               
                   
                 transaction agent. 
                   
               
               
                 Selector agent ID 
                 Model of the selector agent, used 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 during the reconciliation phase 
                   
               
               
                 Events 
                 Type of the detected event(s) 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 having made it possible to initiate 
                   
               
               
                   
                 the action 
                   
               
               
                 Event identifier 
                 Identifier of the detected event(s) 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 having made it possible to initiate 
                   
               
               
                   
                 the action 
                   
               
               
                 Database ID 
                 Identifier of the action database 
                 action1 
               
               
                   
                 used 
                   
               
               
                 Detector agent 
                 Model of the detector agent(s) 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 ID(s) (encrypted) 
                 having made it possible to initiate 
                   
               
               
                   
                 the action, used during the 
                   
               
               
                   
                 reconciliation phase 
                   
               
               
                 Sensor identifiers 
                 Information used to detect the 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 event 
                   
               
               
                 Database ID 
                 Identifier of the event database 
                 event1 
               
               
                   
                 used 
               
               
                   
               
             
          
         
       
     
         [0211]    The following information is provided to the transaction system  7  by the broadcasting agent  3  as variables associated with the user&#39;s request: 
         [0000]    
       
         
               
               
               
             
           
               
                   
               
               
                 Information 
                 Description 
                 Example 
               
               
                   
               
             
             
               
                 Broadcasting 
                 Model of the broadcasting agent 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 agent ID 
                 having executed the action that 
                   
               
               
                 (encrypted) 
                 made it possible to initiate the 
                   
               
               
                   
                 transaction 
                   
               
               
                 Content 
                 Type of broadcast content 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                   
                   
               
               
                 Content identifier 
                 Identifier of the broadcast content 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 generated by the content 
                   
               
               
                   
                 database (optional) 
                   
               
               
                 Action 
                 Type of action executed that made 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 the transaction possible 
                   
               
               
                 Action identifier 
                 Identifier of the executed action 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                   
                   
               
               
                 Database ID 
                 Identifier of the content database 
                 content1 
               
               
                   
                 used 
                   
               
               
                 Selector agent ID 
                 Model of the selector agent(s) 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 having made it possible to select 
                   
               
               
                   
                 the action 
                   
               
               
                 Event (encrypted) 
                 Type of the detected event(s) 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                   
                 having made it possible to initiate 
                   
               
               
                   
                 the action 
                   
               
               
                 Event identifier 
                 Identifier of the detected event(s) 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 having made it possible to initiate 
                   
               
               
                   
                 the action 
                   
               
               
                 Database ID 
                 Identifier of the action database 
                 action1 
               
               
                   
                 BA used 
                   
               
               
                 Detector agent ID 
                 Model of the detector agent(s) 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 having made it possible to initiate 
                   
               
               
                   
                 the action 
                   
               
               
                 Sensor identifiers 
                 Information used to detect the 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 event 
                   
               
               
                 Database ID 
                 Identifier of the event database 
                 event1 
               
               
                   
                 used 
               
               
                   
               
             
          
         
       
     
         [0212]    The following information is provided by the transaction agent ( 1 ,  2  or  3 ) to the remote transaction database BT′ for each transaction T done in XML format: 
         [0000]    
       
         
               
               
               
             
           
               
                   
               
               
                 Information 
                 Description 
                 Example 
               
               
                   
               
             
             
               
                 Timestamp 
                 Date and time of the event 
                 “2010-03-15 20:05:15 GMT” 
               
               
                 Transaction 
                 Identifier of the transaction system 
                 “123 régie” 
               
               
                 system identifier 
                 having performed the transaction 
                   
               
               
                 Transaction 
                 Unique transaction identifier 
                 “XX-7448-22222” 
               
               
                 identifier 
                   
                   
               
               
                 Transaction 
                 Transaction details, making it 
                 CPC-            0.6 
               
               
                 details 
                 possible to calculate the revenue 
                   
               
               
                   
                 generated 
                   
               
               
                 Broadcasting 
                 Model of the broadcasting agent 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 agent ID 
                 having executed the action that 
                   
               
               
                 (encrypted) 
                 made it possible to initiate the 
                   
               
               
                   
                 transaction 
                   
               
               
                 Content 
                 Type of broadcast content 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                   
                   
               
               
                 Content identifier 
                 Identifier of the broadcast content 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 generated by the content 
                   
               
               
                   
                 database (optional) 
                   
               
               
                 Action 
                 Type of action executed that made 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 the transaction possible 
                   
               
               
                 Action identifier 
                 Identifier of the executed action 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                   
                   
               
               
                 Database ID 
                 Identifier of the content database 
                 content1 
               
               
                   
                 used 
                   
               
               
                 Selector agent ID 
                 Model of the selector agent(s) 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 having made it possible to select 
                   
               
               
                   
                 the action 
                   
               
               
                 Event (encrypted) 
                 Type of the detected event(s) 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                   
                 having made it possible to initiate 
                   
               
               
                   
                 the action 
                   
               
               
                 Event identifier 
                 Identifier of the detected event(s) 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 having made it possible to initiate 
                   
               
               
                   
                 the action 
                   
               
               
                 Database ID 
                 Identifier of the action database 
                 action1 
               
               
                   
                 used 
                   
               
               
                 Detector agent ID 
                 Model of the detector agent(s) 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 having made it possible to initiate 
                   
               
               
                   
                 the action 
                   
               
               
                 Sensor identifiers 
                 Information used to detect the 
                 “ba283ebd5467578484f3194e29a7bcfb” 
               
               
                 (encrypted) 
                 event 
                   
               
               
                 Database ID 
                 Identifier of the event database 
                 event1 
               
               
                   
                 used