Method of associating or re-associating devices in a control network

• US 9,049,038 B2
• Filed: 10/08/2010
• Issued: 06/02/2015
• Est. Priority Date: 10/12/2009
• Status: Active Grant

• Current Assignee: Signify Holding B.V. (Signify N.V.)
• Original Assignee: Koninklijke Philips N.V.
• Inventors: Cavalcanti, Dave Alberto Tavares
• Primary Examiner(s): Srivastava, Vivek
• Assistant Examiner(s): Asres, Hermon
• Application Number:
  US13/500,952
• Publication Number:
  US 20120203841A1
• Time in Patent Office: 1,698 Days
• Field of Search: 709/226, 709/204
• US Class Current: 1/1
• CPC Class Codes: G05B 19/4185 characterised by the network communication
• CPC Class Codes: H04L 12/2807 Exchanging configuration information on appliance services in a home automation network arrangements for maintenance or administration involving network analysis for automatically determining the actual topology of a network H04L41/12; hardware or software tools for network management using graphical user interfaces H04L41/22; address allocation H04L61/50
• CPC Class Codes: H04L 12/2838 Distribution of signals within a home automation network, e.g. involving splitting/multiplexing signals to/from different paths adaptations of television systems for transmission by electric cable for domestic distribution H04N7/106; hybrid transport H04L12/6418; home network arrangements specially adapted for distribution of digital video signals H04N7/24
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 69/28 Timers or timing mechanisms used in protocols
• CPC Class Codes: H04W 48/20 Selecting an access point
• CPC Class Codes: H04W 8/005 Discovery of network devices, e.g. terminals
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks
• CPC Class Codes: H04W 84/20 Master-slave selection or change arrangements
• CPC Class Codes: H05B 47/175 by remote control
• CPC Class Codes: Y02P 80/10 Efficient use of energy, e.g. using compressed air or pressurized fluid as energy carrier

Abstract

This invention relates to a method of associating or re-associating devices in a control network including control zones to respective zone controllers (ZCs) controlling the control zones. In a first step, an associating or re-associating timer (ZC_REASSC_TIMER) window is initialized at the (ZCs) defining the time during which said associating or re-associating of the devices takes place. In a second step, during the (ZC_REASSC_TIMER) window zone specific information (ZN_SPEC) message sage is transmitted, the (ZN_SPEC) message including information about the devices expected to be in the zones controlled by the (ZCs). In a third step, it is compared whether the zone specific information contained in the (ZN_SPEC) received by the devices includes device specific information that match with local device specific information associated to the devices. In case the comparing results in that a pre-defined matching criteria is fulfilled an association or re-association request message (RA_REQ) is sent from the devices to the zone controllers (ZCs) where the pre-defined matching criteria was met. The (RA_REQ) message including device description parameters and indicates a request from the devices to join the control zones controlled by said (ZCs). Finally, it is determined whether the association or re-association of the respective devices is to be confirmed by means of comparing, by the respective (ZCs) receiving the (RA_REQ) message, the device description parameters included in the (RA_REQ) message match with zone specific information included in the (ZN_SPEC).

Claims

1. A method of associating or re-associating devices in a control network including control zones to respective zone controllers (ZCs) controlling the control zones, comprising:

initializing an associating or re-associating timer (ZC_REASSC_TIMER) window at the (ZCs) defining the time during which said associating or re-associating of the devices takes place (101);

transmitting during the (ZC_REASSC_TIMER) window zone specific information (ZN_SPEC) message, the (ZN_SPEC) message including information about the devices expected to be in the zones controlled by the (ZCs) (103),

comparing whether the zone specific information contained in the (ZN_SPEC) message received by said devices includes device specific information that match with local device specific information associated to the devices, where in case the comparing results in that a pre-defined matching criteria is fulfilled (105);

sending an association or re-association request message (RA_REQ) from said devices to the zone controllers (ZCs) where said pre-defined matching criteria was met, the (RA_REQ) message including device description parameters and indicates a request from the devices to join the control zones controlled by said (ZCs) (107), and

determining whether the association or re-association of the respective devices is to be confirmed by means of comparing, by the respective (ZCs) receiving said (RA_REQ) message, the device description parameters included in the (RA_REQ) message match with zone specific information included in the (ZN_SPEC) message (109).

2. A method according to claim 1, the step of determining whether the association or re-association of the respective devices is to be confirmed includes checking whether the devices that responded to said (ZN_SPEC) message are indeed the devices expected to be in the zones controlled by the (ZCs), wherein in case said devices do not correspond to the devices expected to be in the zones controlled by the (ZCs) when the (ZC_REASSC_TIMER) expires said timer (ZC_REASSC_TIMER) window is re-initialized and a subsequent associating or re-associating process is performed (111), the method further comprising initializing a counter (ZC_REASSC_COUNTER) for counting the number of times said timer (ZC_REASSC_TIMER) window opened.

3. A method according to claim 2, wherein said step of checking whether the devices that responded to said (ZN_SPEC) message are indeed the devices expected to be in the zones controlled by the (ZCs) comprises:

comparing device identifiers associated to the (RA_REQ) message that uniquely identifies the devices match with a pre-defined list of device identifiers associated to the respective (ZCs), or

comparing device identifiers associated to the (RA_REQ) message that uniquely identifies the devices match with zone specific information associated to the respective (ZCs),

checking whether the type, capabilities and location information of the device associated to the (RA_REQ) message matches zone specific information associated to the respective (ZCs), or

counting the number of a given type and comparing the number of a number of devices of the same type expected to be zones, or

a combination thereof.

4. A method according to claim 2, further comprising defining a maximum counter number (MAX_REASSC_RETRIES), where in case said (ZC_REASSC_COUNTER) exceeds (MAX_REASSC_RETRIES) the process of associating or re-associating devices is terminated.

5. A method according to claim 4, wherein in case the (ZC_REASSC_COUNTER) exceeds (MAX_REASSC_RETRIES) and the expected devices to be in the zone have not successfully associated the respective (ZCs), the (ZCs) assume a commissioning error has occurred and report the error code to a Building Management System (BMS) and/or indicate to a user that an error has occurred.

6. A method according to claim 1, wherein the step of initializing an associating or re-associating timer (ZC_REASSC_TIMER) window is performed periodically so as to allow new devices to associate or existing device to re-associate.

7. A method according to claim 1, wherein said devices collect for a time period (ZC_SCAN_TIME) all received (ZN_SPEC) messages (113) prior to said step of comparing whether the zone specific information contained in the (ZN_SPEC) message received by said devices includes device specific information that match with local device specific information associated to the devices.

8. A method according to claim 7, wherein if a given device does not receive any (ZN_SPEC) messages within said (ZC_SCAN_TIME) period it broadcasts an association or re-association request message (RA_REQ) message including its own device specific information.

9. A method according to claim 1, further comprising issuing and sending a confirming or non-confirming message (RA_RSP) by the (ZCs) to the respective devices that previously sent the (RA_REQ) message to the (ZCs) indicating whether the respective devices are confirmed or not, where in case the respective devices are confirmed they respond by issuing an acknowledgement message (DEV_ACK) and send it back to the respective (ZCs) issuing said (RA_RSP) (115).

10. A method according to claim 9, wherein in case the (DEV_ACK) is not received within a given time (DEV_ACK_TIMEOUT) (117), the (ZC) assumes the re-association process for that specific device failed.

11. A method according to claim 10, wherein in case the respective devices are not confirmed within a given time (DEV_TIMEOUT) by the respective (ZCs) they re-transmit said (RA_REQ) up to a maximum number of times (MAX_REASSC_RETRY).

12. A method according to claim 8, wherein said devices initialize a device associating or re-associating timer (DEV_REASSC_TIMER) window and a counter (DEV_REASSC_COUNTER) (119), the (DEV_REASSC_TIMER) indicating an association or re-association time window at the device side and the (DEV_REASSC_COUNTER) indicates the number of times the (DEV_REASSC_TIMER) window is initialized, said step of collecting for the time period (ZC_SCAN_TIME) all received (ZN_SPEC) messages and following association attempt including transmission of (RA_REQ) being repeated while (DEV_REASSC_COUNTER) is less than said (MAX_REASSC_RETRY).

13. A method according to claim 12, wherein if said (DEV_REASSC_COUNTER) becomes greater that said (MAX_REASSC_RETRY) for a given device selected from said devices and the device has not yet successfully associated with a (ZC), an association or re-association error message (ASSC_ERROR) is issued and associated to a request message (RA_REQ), where the (RA_REQ) and the associated (ASSC_ERROR) message is either sent to a selected zone controller (ZC) or is sent as a broadcast if no (ZC) is known, where in case the selected (ZC) from said associating device or any other (ZC) receives said (RA_REQ) and (ASSC_ERROR) message, the (ZC) grants a temporary association or re-association to said device and sends a message indicating a temporal association or re-association (TEMP_GRANT) to said associating device, said error message (ASSC_ERROR) further being sent to a Building Management System (BMS) for notifying about said error.

14. A computer-readable, non-transitory medium having stored therein instructions for causing a processing unit to execute the method according to claim 1.

15. A system (300) for associating or re-associating devices in a control network including control zones (201-206) to respective zone controllers (ZCs) (207-210) controlling the control zones, comprising:

a timer (301) for initializing an associating or re-associating timer (ZC_REASSC_TIMER) window at the (ZCs) defining the time during which said associating or re-associating of the devices takes place;

a transmitter (302) for transmitting during the (ZC_REASSC_TIMER) window zone specific information (ZN_SPEC) message, the (ZN_SPEC) message including information about the devices expected to be in the zones controlled by the (ZCs),

a processor (303) for comparing whether the zone specific information contained in the (ZN_SPEC) message received by said devices includes device specific information that match with local device specific information associated to the devices, where in case the comparing results in that a pre-defined matching criteria is fulfilled;

a transmitter (302) for sending an association or re-association request message (RA_REQ) from said devices to the zone controllers (ZCs) where said pre-defined matching criteria was met, the (RA_REQ) message including device description parameters and indicates a request from the devices to join the control zones controlled by said (ZCs), and

a processor (303) for determining whether the association or re-association of the respective devices is to be confirmed by means of comparing, by the respective (ZCs) receiving said (RA_REQ) message, the device description parameters included in the (RA_REQ) message match with zone specific information included in the (ZN_SPEC) message.