Method of establishing control relationships, configuration device, networked device and computer program product

• US 9,774,637 B2
• Filed: 08/30/2013
• Issued: 09/26/2017
• Est. Priority Date: 08/31/2012
• Status: Active Grant

• Current Assignee: NXP B.V. (NXP Semiconductors NV)
• Original Assignee: NXP B.V. (NXP Semiconductors NV)
• Inventors: Brandsma, Ewout, Pennings, Maarten Christiaan, Syed, Aly Aamer, van Roermund, Timo
• Primary Examiner(s): Meky, Moustafa M
• Assistant Examiner(s): Islam, Sm Z
• Application Number:
  US14/015,132
• Publication Number:
  US 20140068089A1
• Time in Patent Office: 1,488 Days
• CPC Class Codes: G05B 15/02 electric
• CPC Class Codes: G05B 2219/25295 Identification has information on relationship with other controllers
• CPC Class Codes: G05B 2219/2642 Domotique, domestic, home control, automation, smart house
• CPC Class Codes: G05B 2219/31197 Near field communication nfc
• CPC Class Codes: H04L 12/2809 indicating that an appliance service is present in a home automation network monitoring functionality H04L43/0817; discovery or management thereof, e.g. service location protocol [SLP] or web services, H04L67/51
• CPC Class Codes: H04L 41/04 Network management architectures or arrangements
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/34 Signalling channels for network management communication
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment

Abstract

A method for establishing control relationships between at least two networked devices is conceived. Further a corresponding configuration device, networked device and non-transitory computer program product are provided.

Claims

1. A method for establishing control relationships between at least two networked devices, the method comprising the following steps:

(a) a configuration device reads identification data of a first networked device from a first machine-readable tag, said first machine-readable tag being connected to said first networked device;

(b) the configuration device writes the identification data of the first networked device to a second machine-readable tag, while supplying a power necessary to accomplish said writing to the second machine-readable tag, said second machine-readable tag being connected to a second networked device;

(c) a controller unit of the second networked device reads the identification data of the first networked device from the second machine-readable tag;

(d) the controller unit of the second networked device uses the identification data of the first networked device to establish a control relationship between the first networked device and the second networked device.

2. A method as claimed in claim 1, wherein the second machine-readable tag comprises an RFID interface and the configuration device comprises an RFID interface, and wherein, in step (b), the configuration device writes the identification data of the first networked device to the second machine-readable tag via an RFID connection between the RFID interface of the second machine-readable tag and the RFID interface of the configuration device.

3. A method as claimed in claim 2, wherein the second machine-readable tag is connected to the controller unit via a wired connection, and wherein, in step (c), the controller unit reads the identification data of the first networked device from the second machine-readable tag via said wired connection.

4. A method as claimed in claim 1, wherein the first machine-readable tag comprises any one of an RFID transponder, a barcode element and a QR-code element.

5. A method as claimed in claim 1, wherein the identification data of the first networked device comprises any one of a unique identifier of the first machine-readable tag, a M[edia] A[ccess] C[ontrol] address of the first networked device, and a dynamic network address of the first networked device.

6. A method as claimed in claim 1, wherein the identification data of the first networked device include type data of the first networked device, and wherein said type data determine the semantics of the control relationship.

7. A method as claimed in claim 1, wherein the first networked device is one of a plurality of first networked devices.

8. A method as claimed in claim 7, wherein the configuration device reads the identification data of all first networked devices prior to the establishment of the control relationship.

9. A method as claimed in claim 7, wherein the configuration device comprises a user interface which provides for selecting specific ones of the plurality of first networked devices, and wherein selected specific ones of the plurality of first networked devices are included in the control relationship.

10. A method as claimed in claim 9, wherein the user interface further provides for deselecting specific ones of the plurality of first networked devices, and wherein deselected specific ones of the plurality of first networked devices are excluded from the control relationship.

11. A method as claimed in claim 1, wherein the configuration device further provides for copying an existing control relationship between the first networked device and a third networked device from said first networked device to the second networked device.

12. A method as claimed in claim 1, wherein the control relationship comprises a membership of a group of networked devices.

13. A method as claimed in claim 1, wherein, when the second networked device is in an off or low-power state, the second networked device is woken up as a result of an interaction between the configuration device and the second machine-readable tag, and/or wherein, when the first networked device is in an off or low-power state, the first networked device is woken up as a result of an interaction between the configuration device and the first machine-readable tag.

14. A method as claimed in claim 1, wherein, when the second networked device is in an off or a low-power state, the second networked device verifies, after or upon waking up, whether the identification data of the first networked device has been written to the second machine-readable tag, and if so, then the second networked device uses the identification data of the first networked device to establish a control relationship between the first networked device and the second networked device.

15. A method as claimed in claim 1, wherein the second networked device transmits a setup message to the first networked device in order to establish said control relationship, and wherein the second networked device retransmits said setup message if it has not received a confirmation of receipt of said setup message from the first networked device after a predetermined amount of time.

16. A method as claimed in claim 1, wherein the second networked device transmits a setup message to the first networked device in order to establish said control relationship, and wherein, when the first networked device is in an off or low-power state, the first networked device transmits, after or upon waking up, a broadcast message into the network in order to retrieve said setup message.

17. A method as claimed in claim 1, wherein the second networked device transmits a setup message to a central registry in order to establish said control relationship, and wherein, when the first networked device is in an off or a low-power state, the first networked device queries, after or upon waking up, the central registry for said setup message.

18. A method as claimed in claim 1, wherein the configuration device, upon reading the identification data of the first networked device from the first machine-readable tag, sets a flag in said first machine-readable tag, and wherein, when the first networked device is in an off or a low-power state, the first networked device verifies, after or upon waking up, whether said flag is set, and if so, the first networked device checks for the presence of a setup message intended to establish said control relationship.

19. A method as claimed in claim 18, wherein the configuration device, upon reading the identification data of the first networked device from the first machine-readable tag, further writes contact data into the first machine-readable tag, and wherein, when the first networked device is in the off or low-power state, the first networked device uses, after or upon waking up, said contact data to query a device identified by said contact data for the presence of said setup message.

20. A method as claimed in claim 18, wherein the configuration device, upon reading the identification data of the first networked device from the first machine-readable tag, further writes a relationship identifier into the first machine-readable tag, said relationship identifier uniquely identifying a specific control relationship and a corresponding specific setup message, and wherein the first networked device checks for the presence of said specific setup message after or upon waking up.

21. A method as claimed in claim 1, wherein a validation step is performed to determine whether the first networked device and the second networked device form part of the network.

22. A method as claimed in claim 21, wherein, if the first networked device and/or the second networked device do not form part of the network, the first networked device and/or the second networked device are joined into the network prior to establishing the control relationship.

23. A method as claimed in claim 1, wherein the configuration device writes the identification data of the first networked device to the second machine-readable tag via a secure communication channel.

24. A configuration device for use in a method as claimed in claim 1,

said configuration device being adapted to read identification data of a first networked device from a first machine-readable tag, said first machine-readable tag being connected to said first networked device;

said configuration device further being adapted to write the identification data of the first networked device to a second machine-readable tag while supplying power necessary to accomplish said writing to the second machine-readable tag, said second machine-readable tag, said second machine-readable tag being connected to a second networked device,

such that a controller unit of the second networked device may read the identification data of the first networked device from the second machine-readable tag;

and such that the controller unit of the second networked device may use the identification data of the first networked device to establish a control relationship between the first networked device and the second networked device.

25. A configuration device as claimed in claim 24, the configuration device being an NFC-enabled smart phone or a web tablet.

26. A second networked device for use in a method as claimed in claim 1,

said second networked device comprising a controller unit adapted to read identification date of a first networked device from a second machine-readable tag connected to said second networked device;

wherein the controller unit of the second networked device is further adapted to use the identification data of the first networked device to establish a control relationship between the first networked device and the second networked device,

said identification data of the first networked device having been read from a first machine-readable tag by a configuration device, said first machine-readable tag being connected to said first networked device;

and said identification data of the first networked device having been written to the second machine-readable tag by said configuration device while said configuration device has supplied the power necessary to accomplish said writing to the second machine-readable tag.

27. A computer program product comprising program elements executable by a configuration device or a second networked device, wherein each program element comprises program instructions which, when being executed by the configuration device or the second networked device, cause said configuration device and second networked device to carry out or control respective steps of a method as claimed in claim 1.