Method for configuring communication between a device and a coordinator in a home automation system

Abstract

The invention relates to a method for connecting a device (DD1) to an internal network (LNT) of a home automation system. The device comprises a first communication interface (CI1) implementing a first communication protocol for connecting to the internal network. The method comprises the steps of: receiving a communication channel identifier (CHN) of the internal network via a second communication interface (CI2) of the device (DD1), the second interface implementing a second communication protocol; attempting to connect to the internal network via a communication channel corresponding to the channel identifier received by the first communication interface (CI1); receiving a network key (NKY) via the first interface; and establishing, using the network key, an encrypted communication link between the device and the internal network via the communication channel corresponding to the received channel identifier. Figure 3

Description

Title of the invention: Method for configuring communication between a device and a coordinator in a home automation system technical field

[0001] The present invention relates to a home automation system comprising devices and a coordinator, also called a "home automation hub," which notably provides functions for managing an internal communication network linking the devices to the coordinator and for routing and communication between the internal network and an external terminal, such as a mobile device. Thus, the terminal can remotely control the devices connected to the internal network individually via the coordinator. The devices can be actuators, light fixtures, thermostatic valves, a siren, and / or sensors. The actuators can control roller shutters, blinds, a door, a gate, a multimedia projection screen, or even a ventilation flap. The present invention relates more particularly to adding a new device to such an internal network. Prior art

[0002] There are various known home automation internal networks, notably based on one or more of the communication protocols Zigbee®, Thead®, Bluetooth® or Bluetooth Low Energy (BLE®), IO Homecontrol® and WiFi®. To be integrated into an internal network, a new device must be able to communicate according to the internal network's communication protocol, on a channel chosen for the internal network and corresponding to a predefined frequency or frequency band within the frequency band authorized for the communication protocol.

[0003] The Zigbee® protocol provides a procedure for connecting a new device to an internal network. According to this protocol, a coordinator must activate a network mode called "open network" for a certain period. The device to be added must first perform an inventory of primary channels in the network in open mode. Then, the device must attempt to connect to the network by successively testing the primary channels in the inventory. As soon as a connection attempt succeeds, the device receives encryption keys from the coordinator to encrypt the data transmitted in the channel thus discovered. If these attempts fail, the device must perform an inventory of secondary channels in the network in open mode and attempt to connect to one of the secondary channels.If these attempts fail, he must repeat the entire procedure several times in case an attempt failed due to a temporary network disruption, before entering a . sleep mode. The execution time of this procedure can be long, especially when installing a large number of devices during the installation of a home automation system, knowing that the number of channels to test can reach about fifteen.

[0004] To reduce this execution time, some manufacturers have defined a list of preferred primary and secondary channels. In this case, the connection procedure performed by the device to be connected first includes a test of the preferred primary channels, then, if this test fails, a test of the preferred secondary channels, before testing the other listed channels. Thus, connecting a device can be faster if the channel to be used is on the list of preferred channels. These preferred channels may be selected, in particular, because they are less likely to be disrupted, for example, by other wireless networks such as Wi-Fi or by regulatory constraints.

[0005] However, there is a need to further accelerate the procedure for connecting a new device. Summary

[0006] Embodiments relate to a method of connecting a device to an internal home automation system network, implementing a first wireless communication protocol, the device comprising a first communication interface implementing the first communication protocol, the method comprising steps consisting of: receiving a communication channel identifier from the internal home automation system network by a second communication interface of the device, the second communication interface implementing a second communication protocol; attempting to connect to the internal network by means of a communication channel corresponding to the received communication channel identifier, by the first communication interface of the device; receiving a network key by the first communication interface;and establish, using the network key, an encrypted communication link between the device and the internal network, via a communication channel of the internal network, corresponding to the received communication channel identifier.

[0007] Thus, the device to be connected has the communication channel identifier directly available to connect to the home automation system's internal network, and can therefore attempt to connect directly to the communication channel used by the internal network. It is therefore unnecessary to perform the standard procedure of searching for the communication channel identifier. This feature can save considerable time, particularly when installing a complete home automation system with several devices to be connected. Furthermore, this The new connection procedure remains compatible with the communication protocol implemented in the internal network.

[0008] According to one embodiment, the method includes network search steps to determine if one or more compatible networks are open for a connection of the device to be connected, the compatible network search being carried out on a communication channel corresponding to the received communication channel identifier.

[0009] According to one embodiment, the method includes, in the absence of receipt of a network key within a period of time after the attempt to connect to the internal network, a new attempt to connect to the internal network via the communication channel corresponding to the received communication channel identifier.

[0010] This provision makes it possible to overcome a temporary disruption of the internal network, and avoids in this situation having to execute the classic connection procedure involving the testing of a large number of communication channels.

[0011] According to one embodiment, the method includes, in the absence of receipt of a network key within a period of time after the attempt to connect to the internal network, a new attempt to connect the device to the internal network by a communication channel other than that corresponding to the received communication channel identifier.

[0012] This provision makes it possible to deal with the case where the channel identifier received from the terminal is incorrect, by allowing the use of other privileged communication channel identifiers, while avoiding having to execute the classic connection procedure involving the testing of a large number of communication channels.

[0013] According to one embodiment, the first communication protocol is the Zigbee® or Thread® protocol.

[0014] According to one embodiment, the second communication protocol is a wireless communication protocol and in particular the Bluetooth®, BLE® or WiFi® protocol.

[0015] According to another embodiment, the second communication protocol is a wired communication protocol.

[0016] These protocols have the advantage of presenting a connection procedure that does not require knowledge of a communication channel identifier to be used to establish a connection.

[0017] According to one embodiment, the method includes steps for establishing a communication link between a terminal and the second communication interface of the device to be connected, using an identifier of the device to be connected and an installation code.

[0018] According to one embodiment, the method includes steps of reading by the terminal an optical code affixed to a casing of the device to be connected and of decoding by the terminal the optical code to obtain the identifier of the device to be connected and the installation code.

[0019] According to one embodiment, a coordinator selects a communication channel for the internal network elements and transmits an internal network communication channel identifier to the terminal.

[0020] Embodiments may also relate to a home automation device comprising: a home automation device, a first communication interface implementing a first wireless communication protocol, a second communication interface implementing a second communication protocol, and a processor connected to the home automation device and to the first and second communication interfaces and configured to implement the method defined above, and to communicate in the internal network via the first communication interface and to receive at least one communication channel identifier from the internal network via the second communication interface.

[0021] According to one embodiment, the first and second communication interfaces include a common antenna.

[0022] According to one embodiment, the first and second communication interfaces each include an antenna. Brief description of the figures

[0023] The present invention will be better understood with the aid of the following description of exemplary embodiments with reference to the accompanying figures, in which identical reference signs correspond to structurally and / or functionally identical or similar elements.

[0024] [Fig. 1] Figure 1 schematically represents a home automation system, according to one embodiment,

[0025] [Fig.2] Figure 2 schematically represents a home automation device, according to a method of implementation,

[0026] [Fig. 3] Figure 3 shows steps in a process for connecting a new device to a home automation system network, according to a specific embodiment, Detailed description

[0027] Figure 1 represents a home automation system comprising devices 1, 2, DD, such as actuators, light fixtures, thermostatic valves, a siren, and / or sensors. The actuators can be roller shutter 1, 2, blind, projection screen, door, gate, or ventilation hatch actuators. Devices DD, 1, 2 are connected via an internal home automation network LNT to An RTR coordinator. The RTR coordinator is configured to manage the internal LNT network connecting devices to the coordinator and to provide communication functions between devices connected to the internal LNT network and an external MT terminal, such as a mobile terminal. Hereafter, the external terminal will be referred to interchangeably as an external terminal, terminal, or mobile terminal. The internal LNT network is a wireless mesh network and implements a primary communication protocol, such as Zigbee® or Thread®. The MT terminal is connected to the RTR coordinator, for example, via a wireless link implementing a secondary communication protocol, such as Bluetooth® or Wi-Fi®. Thus, the secondary communication protocol used between the RTR coordinator and the MT mobile terminal may differ from the primary communication protocol used by the DD devices to communicate with the RTR coordinator and potentially with each other.The MT terminal runs a dedicated application that controls devices DD, 1, 2 connected to the internal LNT network and receives data from them, notably via the RTR coordinator. The coordinator also selects a communication channel for the elements of the internal LNT network.

[0028] Figure 2 shows a new home automation device DD1 configured to connect to the internal LNT network, according to one embodiment. The device DD1 includes a home automation component OD, such as a shutter actuator, and a communication circuit CCT connected to the home automation component OD. The communication circuit CCT includes a processor PRC and a first communication interface Cil for connecting the PRC processor to the internal LNT network. The PRC processor is configured to control the home automation component OD based on commands received via the Cil interface and to transmit data, such as a status, provided by the component OD through the CIL interface. According to one embodiment, the device DD1 includes a second communication interface CI2 for connecting the PRC processor to a device external to the internal LNT network, such as the MT terminal.The PRC processor is further configured to establish communications using the second communication interface CI2. Each of the communication interfaces CI1, CI2 can be connected to a respective antenna A1, A2 or a common antenna.

[0029] The first communication interface Cil implements the first wireless communication protocol such as Zigbee® or Thread®. The second communication interface CI2 implements the second or a third wireless communication protocol such as Bluetooth®, BLE® or WiFi®, or a wired communication protocol, such as that supported by a serial, USB or RS485 port.

[0030] Figure 3 represents steps SI to S12 of a method for connecting a new device such as device DD1 to the internal LNT network, according to one embodiment. The MT terminal runs a dedicated application that includes a new device addition function, implementing steps SI through S5. The MT mobile terminal is connected to the internal LNT network, specifically to the RTR coordinator. In step SI, the MT terminal obtains an IDD identifier from device DD1, as well as an IC installation code from device DDL. In step S2, the MT terminal establishes a connection with the RTR coordinator and transmits the IDD identifier and the IC installation code from device DDL to the latter. The IC installation code is a random code assigned to the device during its manufacture and may not be unique.

[0031] In step S3, the RTR coordinator transmits to the MT terminal a CHN channel identifier shared and used by the various elements of the internal LNT network. Note that the CHN channel identifier may be associated with additional data necessary to determine the channel to be used. In step S4, the MT terminal and the DD1 device execute a BCP connection procedure implementing the second communication interface CI2 of the DD1 device and using the IDD identifier and the IC installation code. During step S5, the MT terminal transmits to the DD1 device, via the second interface CI2, a message containing a CHN channel identifier to be used to connect to the internal LNT network.

[0032] In step S6, device DD1 performs a network search to detect one or more CNT-compatible networks in open mode and accessible, i.e., capable of accepting a new device. This network search consists primarily of transmitting BCN beacon messages on the channel identified by the received CHN channel identifier. In step S7, if a CNT-compatible network is found, steps S8 to S10 are executed. In step S8, device DD1 sends a secure connection request to the internal CNT network using the CHN channel identifier and waits for a response in step S10. At step S9, if the CHN channel is used by the internal LNT network, which is the case if the DD1 device has received the CHN channel identifier in step S5, the RTR coordinator connected to the network via the CHN channel responds to the connection request by issuing a response message containing a network key NKEY.The NKEY network key can be derived from the IC installation code of the new DDL device. At step S10, if the DD1 device receives a response message from the RTR coordinator containing an NKEY network key, it executes the SU step; otherwise, it executes the S12 step.

[0033] In step SI 1, the DD1 device activates a ZFC connection finalization procedure with the RTR coordinator using the CHN channel. This finalization step establishes an encrypted communication link with the RTR coordinator via the LNT network.

[0034] At step S12, the DD1 device activates a ZNCP connection procedure conforming to the first communication protocol to determine primary channels and secondary channels and successively test all of these channels until a response is obtained from the RTR coordinator.

[0035] Before executing step S12, the DD1 device may execute steps S8 to S10 several times to take into account the fact that the absence of reception of a reply message issued by the RTR coordinator at step S9 (within a certain time frame) may be due to a temporary disturbance of the internal LNT network, which prevents the transmission or reception of the connection request at step S8 and / or the transmission or reception of the reply message at step S9.

[0036] According to one embodiment, the DD1 device receives or has several channel identifiers that can be used by the DD1 device to connect to the LNT network. Before executing step S12, the DD1 device can also repeat steps S8 to S10 one or more times to attempt to connect to the LNT network and receive an NKY network key using one or more of the other channel identifiers at its disposal.

[0037] According to one embodiment, the SI step is carried out by reading steps by the MT terminal of an optical code (barcode or QR code) affixed to a housing of the device DD1, and decoding the optical code to obtain the IDD identifier of the device DD1 and the installation code IC.

[0038] It will be evident to those skilled in the art that the present invention is susceptible to various embodiments and applications. In particular, the CHN identifier of the communication channel received by the CI2 interface of the device to be connected DD1 can be obtained in various other ways. For example, it may be known to the operator installing the device and entered directly on the MT terminal.

[0039] The invention is also not limited to the alternative treatments described above implemented in the event of no response from the network following step S8. Other alternative treatments can be implemented, such as repeating all or part of steps S1 to S8. For example, the transmission of the channel number CHN in step S3 or S5 may be error-ridden, justifying the repetition of that step.

Claims

Demands

1. 1. A method for connecting a device (DD, DD1) to an internal network (LNT) of a home automation system, implementing a first wireless communication protocol, the device comprising a first communication interface (CI2) implementing the first communication protocol, the method comprising the steps of: receiving a communication channel identifier (CHN) of the internal network (LNT) of the home automation system by a second communication interface (CI2) of the device (DD, DD1), the second communication interface implementing a second communication protocol; attempting to connect to the internal network by means of a communication channel corresponding to the received communication channel identifier, by the first communication interface (CI2) of the device; receiving a network key (NKY) by the first communication interface;and establish, using the network key, an encrypted communication link between the device and the internal network, via a communication channel of the internal network, corresponding to the received communication channel identifier.

2. 2. Method according to claim 1, comprising network search steps to determine if one or more compatible networks (CNTs) are open for connection of the device to be connected (DD, DD1), the compatible network search being performed on a communication channel corresponding to the received communication channel identifier (CHN).

3. 3. Method according to claim 1 or 2, comprising, in the absence of receipt of a network key (NKY) within a time period after the attempt to connect to the internal network (LNT), a new attempt to connect to the internal network via the communication channel corresponding to the received communication channel identifier (CHN).

4. 4. A method according to any one of claims 1 to 3, comprising, in the absence of receipt of a network key (NKY) within a time period following the attempted connection to the internal network, a new Attempt to connect the device to the internal network (LNT) via a communication channel other than the one corresponding to the received communication channel identifier.

5. 5. A method according to any one of claims 1 to 4, wherein the first communication protocol is the Zigbee® or Thread® protocol.

6. 6. A method according to any one of claims 1 to 5, wherein the second communication protocol is a wireless communication protocol and in particular the Bluetooth®, BLE® or WiFi® protocol.

7. 7. A method according to any one of claims 1 to 5, wherein the second communication protocol is a wired communication protocol.

8. 8. A method according to any one of claims 1 to 7, comprising steps of establishing a communication link between a terminal (MT) and the second communication interface (CI2) of the device to be connected (DD1), using an identifier (IDD) of the device to be connected and an installation code (IC).

9. 9. Method according to claim 8, comprising steps of reading by the terminal (MT) an optical code affixed to a housing of the device to be connected (DD, DD1) and of decoding by the terminal (MT) the optical code to obtain the identifier (IDD) of the device to be connected and the installation code (IC).

10. 10. Method according to claim 8, wherein an internal network coordinator (RTR) (LNT) selects a communication channel for the internal network elements and transmits an internal network communication channel identifier (CHN) to the terminal (MT).

11. 11. A home automation device comprising: a home automation unit (DO), a first communication interface (CI1) implementing a first wireless communication protocol, a second communication interface (CI2) implementing a second communication protocol, and a processor (PRC) connected to the home automation unit and to the first and second communication interfaces and configured to implement the method according to any one of claims 1 to 10, and to communicate in the internal network (LNT) via the first communication interface (Cil) and to receive at least one internal network communication channel identifier (CHN) via the second communication interface.

12. 12. Device according to claim 11, wherein the first and second communication interfaces comprise a common antenna.

13. 13. Device according to claim 11, wherein the first and second communication interfaces each comprise an antenna.

Images