Design and control systems, commissioning tools, configuration adapters and method for wireless and wired networks design, installation and automatic formation
25 claims: 2 independent, 23 dependent
- 1A method of design, installation, and formation of a network that comprises wired and wireless links, the method comprising the stages of:creating a design of said network (105,106), said design comprising parameters and design configuration data of devices (201,202) designed to be in said network (105,106) and binding information defining bindings to allow connections between devices to run an application;installing said devices (201,202) according to said created design by accessing said created design by a commissioning tool (104) and downloading data from said commissioning tool (104) into a configuration adapter (204) comprised in said devices (201,202) before the devices are initialized;and forming said network (105,106) and bindings according to said created design by initializing said devices (201,202) by reading said downloaded data from the configuration adapter (204) and forming said network (105,106) once the devices are initialized.
- 17A system for forming and controlling networks (105,106) that comprise wired and wireless devices (201,202) and wired and wireless links, the system comprising:a design system (101) configured to create and store a design of a network, said design system (101) comprising parameters and design configuration data of devices (201,202) designed to be in said network (105,106) and binding information defining bindings to allow connection between devices (201,202) to run an application;configuration adapters (204) comprised in devices (201,202) configured to be installed according to said design;and a control system (102) comprising at least one commissioning tool (104), the control system (102) configured to install said devices (201,202) by accessing said created design by a commissioning tool (104) and downloading data from said commissioning tool (104) into said configuration adapters (204) before the devices (201,202) are initialized;the installed devices (201,202) configured to form the network (105,106) and the bindings according to the created design by initializing said devices (201,202) by reading said downloaded data from the configuration adapters (204) and to form the netword (105,106) once the devices (201,202) are initialized.
Independent claims2
189 paragraphs, as filed
<u>FIELD OF TIE INVENTION</u>
0001The present invention relates to a new and improved method for wireless and wired networks design, installation and automatic formation including binding of the networks devices by creating logical links between two or more devices.
<u>BACKGROUND OF THE INVENTION</u>
0002Wireless control of networks provides the capability of remotely controlling and monitoring devices in many areas such as home and commercial automation, industrial automation, lighting, and heating, ventilation and air conditioning (HVAC) control.
0003Wireless control networks are attractive for deployment of advanced control systems because they save the cost of cabling, labor, materials, testing and verification of the wiring and installation. However the installation, configuration of parameters for binding of the wireless devices requires highly skilled professionals, special equipment and complicated manual procedures.
0004As an example, the standard manual pairing/binding procedure of a light switch and a lamp (after the devices are installed and the network parameters are loaded) is:
0005Entering the switch's set up mode by pressing a specific push button and having a set amount of time to connect a lamp by pressing and holding an activation button on the lamp. This is a time consuming procedure that is prone to errors and is suitable only for small-scale installations.
0006Installing a wireless control network requires several main procedures to be performed on each wireless device after the network scheme, parameters, and activation are defined. These main procedures are: <ol id="ol0001" compact="compact"><li>1. Entering a unique ID (UID) such as a unique radio ID.</li><li>2. Entering a startup attribute set (SAS) such as a personal area network (PAN) ID of the network.</li><li>3. Identifying (connecting) the physical location of the device with its UID and its logical location and function on the network scheme.</li><li>4. Pairing/binding of controlling devices and sensors.</li></ol>
0007This installation challenge is increased when a large quantity of sensing devices needs to be paired to corresponding controlling devices.
0008There have been several attempts to solve these problems which are described in the following paragraphs. Most of them are time consuming and require expensive equipment and highly qualified personnel.
0009Culbert describes a RFID network arrangement, which is a system for automatic configuration and authentication of network devices in <patcit id="pcit0001" dnum="US22020505A" dnum-type="L"><text>U.S. Patent Application 11/220,205 (2005</text></patcit>).
0010Culbert does not solve the problem of locating wireless devices and performing post installation configuration tasks. At installation time the devices are given "various communication setup and security parameters" from the base station. These parameters are configured by the user or by the factory.
0011Culbert does not specify how this information is stored in the base station, and specifically does not mention how devices are distinguished from one another.
0012Wang describes an initialization of wireless-controlled lighting systems in <patcit id="pcit0002" dnum="US6859644B"><text>U.S. patent No. 6,859,644 (2005</text></patcit>).
0013Device initialization according to Wang is a complex post-installation process. After devices are installed, there is a complex phase of initialization in which each device transmits a request for initialization and a local control master responds and verifies initialization. This process requires devices to be turned on, which consumes energy (critical for battery operated devices). In addition, in case there are many devices in the network, the process of initializing all the devices is time consuming.
0014Pereira describes a method and system for automated distributed pairing of wireless nodes of a. communication network in <patcit id="pcit0003" dnum="US12079905A" dnum-type="L"><text>U.S. Patent Application No. 11/120,799 (2005</text></patcit>).
0015Pereira uses a context manager node to determine location of devices and enable automated distributed pairing.
0016The technology used to determine location of devices is expensive and the algorithms are complex for a network where devices are mostly static. Furthermore, the user usually determines which nodes should be paired. The process of determining which nodes should be paired cannot be automated.
0017Combs describes a method to wirelessly configure a wireless device for wireless communication over a secure wireless network in <patcit id="pcit0004" dnum="USAPPLICATIONNO11150376A" dnum-type="L"><text>U.S. Patent Application No. 11/150,376 (2005</text></patcit>).
0018The method according to Combs contains two phases of configuration. In the first phase devices are configured so they can communicate securely with the administrator. This phase can either be done by the manufacturer, or at the customer's site. The second phase takes place over a secure channel and configures devices so they can join the secure network. The method according to Combs requires pre-configuring the devices and bringing them close to an administrator (such as PC), requires software manipulation, is time consuming and is suitable only for small networks (such as networks of printers).
0019Kruse describes an independent radio frequency programming device and method for the automation of the setup process for a lighting system with lighting control devices and master controllers in <patcit id="pcit0005" dnum="US7126291B2"><text>U.S. Patent No. 7,126,291 B2</text></patcit>. In the method, according to Kruse, it is assumed that before the setup programming the system is powered-up and the devices are identified by the master controller. The programming device eavesdrops on the messaging traffic between the master controller and each device and is capable of automatically programming each one of the devices. Kruse doesn't mention how the devices are identified by the master controller. The pairing/binding and device locations are not mentioned.
0020It is known from <patcit id="pcit0006" dnum="US20050165919A"><text>US 2005/0165919</text></patcit> to provide a system and method to simulate and manage a WLAN. The system includes a characteristic and configurations receiving logic for causing the processing system to determine a set of original characteristics and configurations of the WLAN. As well, a simulation logic for causing the processing system to simulate an outcome based upon a set of configurations in accordance with a goal. The goal may be user defined or based upon historical data.
0021It is known from <patcit id="pcit0007" dnum="US20070232288A"><text>US 2007/0232288</text></patcit> to provide a service tool for wireless automation systems. The service tool accesses a building automation system to configure and confirm design of an installation, monitor and optimize functionality, commission communication protocols, diagnose, analyze and troubleshoot problems, analyze communications between components, adjust and/or reconfigure parameters, monitor, analyze and debug a building automation system, its components and the like. The service tool provides a man-machine interface to the building automation system and its components by communicating directly and/or indirectly with the system and its components.
0022It is known from <patcit id="pcit0008" dnum="US7184770B"><text>US 7,184,770</text></patcit> to provide a system and method for positioning and calibrating wireless network devices. The method comprises determining locations within a site for a plurality of network devices. The calibration of each network device is performed separately and successively through the transmission of wireless signals by the access points.
0023There is a need for a simple automated method and system for initialization, location and binding of devices in large wireless networks.
<u>SUMMARY OF THE INVENTION</u>
0024The prior arts do not teach or suggest a simple automated method and system for initialization, location and binding of wireless and wired devices in large communication networks.
0025Design and control systems, commissioning tools, configuration adapters and a method according to the present invention, allow for large wireless and wired networks design, installation and automatic formation including binding of networks devices.
0026Wireless network devices are devices interconnected by wireless communication links. Wired network devices are devices interconnected by wired communication links. For illustrative purposes, consider an example of a wireless lighting control system for networks that include devices such as wired network lamp ballasts connected to a wireless device, wireless sensors (such as light intensity and presence), wireless switches, a master controller that wirelessly controls the networks through a wireless access point and a commissioning tool (used for operations such as the configuration of devices).
0027In the design system the networks may be designed, according to the present invention, in two main stages, the architectural and the electrical design stages.
0028In the architectural design stage, according to the present invention, networks scheme may be created and logical binding information (logical links) between the devices may be prepared. The scheme and the binding information may be created by the architectural designer and may be stored in a standard storage means (such as a database or CD). The networks scheme describes the networks in a human-friendly way and allows to easily locate devices on it. For example, the networks scheme may be a diagram which represents a floor .in a building, the rooms on the floor and the physical location of the lamp ballasts and the lighting switches. The networks scheme uniquely identifies each device by its type and its physical location parameters, and combines both sets of parameters to a unique (wired or wireless) logical ID. The type will later be used by the networks installers to select a device from the set of available devices to be physically installed in the location specified by the networks scheme. For example, the type of a device can represent the serial ID of its version that is written on a tag of each device, the location of a device can be in the form of [building name, floor number, room number]. Binding information contains information that will later be used to link devices. It may be prepared using the networks scheme to create logical links between devices. The information contains pairs of devices as identified by the networks scheme. For example, the logical bindings can indicate which switch controls which lamp ballast.
0029In the electrical design stage, according to the present invention, two device mapping tables that contain configuration data may be formed: wired device mapping for wired devices, and wireless device mapping for wireless devices. The device mappings map between the devices on the networks scheme and their valid configuration data such as radio IDs and startup attribute sets for wireless devices, and wired communication link addresses for wired devices. The mappings may be used to correctly initialize the devices in the system. The mappings may also be used in order to locate each logical device described by the predefined scheme on the actual networks to be formed. Locating each device in the network allows to access, bind and reconfigure it using its valid configuration data. The wireless device mapping table may also contain an address translation sub-table. For each wireless device, the address translation sub-table maps the wired communication link address of each connected wired device to its endpoint (addressable component in a wireless device) used by the wireless protocols. The address translation sub-table allows each wireless device to locate and communicate with each attached wired device, providing an indirect communication link between the wireless and wired networks.
0030The data prepared in the design system may be transferred to or accessed by a master controller in the control system and may be transferred to or accessed by dedicated commissioning tools.
0031The next stage after the networks design, according to the present invention, may be the networks installation. The installers may locate each device in the mapping table in the commissioning tools according to its physical location and type as defined in the networks scheme. The data from the commissioning tools may be downloaded into the wireless devices through their dedicated configuration adapters. The download may be carried out by contactless technologies (such as RFID/NFC) or by contact technologies (such as 1-Wire). The data may be downloaded into the wired network devices through their dedicated configuration adapters. The download can be carried out in the same way as for the wireless devices or for simple cases, manually (for example, by setting switches). After the device is loaded it is mounted in its physical location as defined in the networks scheme. The devices and the configuration adapters do not necessarily have to be powered-up during configuration data loading.
0032During the initialization stage, according to the present invention, the networks may be powered-up and initialized. The wireless devices update themselves with the downloaded configuration data. For each wireless device, part of this data may be the address translation sub-table entries, which include the wired communication link address and endpoint (addressable component in a wireless device) of each wired device connected to its wired communication link. The wired communication link address of each wired device is updated according to the address loaded in its configuration adapter.
0033After the networks are initialized, all the devices are recognized by the master controller. The master controller uses the wireless device mapping and the address translation sub-table in the wireless device mapping to translate the design system prepared binding information to valid binding commands containing valid configuration data: Radio IDs, endpoints, and additional data as required by wireless protocols. The binding commands are transmitted to the wireless devices for creating logical links between different devices and the bindings are automatically formed. The binding information may be downloaded into devices together with the other configuration data if the memory/storage in the configuration adapter is large enough.
0034According to a first aspect of the present invention, there is provided a method of design, installation and formation of a network that comprises wired and wireless links, as set forth in claim 1 of the appended claims.
0035Further features of the method are set out in the appended claims depending from the main independent method claim.
0036According to a second aspect of the present invention, there is provided a system for forming and controlling a network that comprises wired and wireless links, as set forth in claim 17 of the appended claims.
0037Further features of the system are set out in the appended claims depending from the main independent system claim.
0038According to other further features of the method there is the stage of automatically forming the networks.
0039According to further features of the method the main stage of starting the networks design, installation, and formation includes the stage of: (i) providing a design system.
0040According to further features of the method the main stage of designing the networks includes the stages of: (i) defining at least two devices type and physical locations of the at least two devices; (ii) defining binding links between the at least two devices; (iii) defining a wired device mapping; (iv) defining wireless device mapping; and (v) defining an address translation sub-table for wireless devices.
0041According to further features of the method the main stage of starting the networks design, installation, and formation includes the stage of: (i) providing a design system.
0042According to still further features of the method-the main stage of installing the networks includes the stage of (i) installing at least one wireless device.
0043According to still further features of the main stage of installing the networks further includes the stages of: (ii) installing at least one wired device.
0044According to still further features of the method the main stage of automatically forming the networks includes the stages of: (i) initializing the at least one wireless device; (ii) initializing the at least one wired device; and (iii) bindings formation.
0045According to other further features of the method-the main stage of installing the networks includes the stage of: (i) forming at least one wireless network.
0046According to still further features of the method the main stage of forming the networks further includes the stages of: (i) initializing at least one wired device; and (ii) bindings formation.
0047According to the present invention there is provided a method of networks installation and formation, the method including the stages of: (i) installing at least one wireless device.
0048According to further features of the method further including the stages of: (ii) installing at least one wired device; (iii) initializing the at least one wireless device; (iv) initializing the at least one wired device; and (v) bindings formation.
0049According to other features of the method the stage of defining a wired device mapping includes the sub-stages of: (A) using a master controller to automatically insert a wired logical ID of at least one wired device to a device mapping; and (B) using the master controller to automatically allocate addresses for the at least one wired device.
0050According to other features of the method the stage of defining a wireless device mapping includes the sub-stages of: (A) defining a SAS for each of the wireless devices on a networks scheme; (B) using a master controller to automatically start to create a device mapping from a wireless logical ID of each of the wireless devices and its the SAS; (C) using a master controller to initiate a radio ID allocation; (D) using the master controller to allocate a radio ID for each of the wireless logical IDs; and (E) forming an additional address translation sub-table which specifies wired communication link addresses and an endpoint for each of the wired devices attached to each one of the wireless devices.
0051According to other features of the method the stage of defining an address translation sub-table for wireless devices includes the sub-stages of: (A) using a master controller to initiate address translation sub-table calculation; (B) using the master controller to automatically take a wired logical sub-ID and wired communication link address for each wired device from the wired device mapping and fill it in the address translation sub-table; and (C) entering an endpoint identifier.
0052According to other features of the method the stage of installing at least one wireless devices includes the sub-stages of: (A) physically installing the at least one wireless device according to type and location taken from a networks scheme as it appears on a commissioning tool; (B) marking the physically installed at least one wireless device on the commissioning tool; (C) bringing the commissioning tool into at least proximity of a physically installed configuration adapter of wireless device; and (D) initiating data download from the commissioning tool to the configuration adapter of wireless device using a tool's user interface, wherein there is no need to power-up configuration adapter of the wireless device.
0053According to other features of the method the stage of installing at least one wired device includes the sub-stages of: (A) physically installing the at least one wired device according to type and location taken from a networks scheme as it appears on a commissioning tool; (B) marking the physically installed at least one wired device on the commissioning tool; (C) bringing into at least proximity the commissioning tool with the at least one installed wired device; and (D) initiating data download from the commissioning tool to the at least one wired device using a tool's user interface, wherein there is no need to power-up the wired device.
0054According to other features of the method the stage of initializing at least one wireless device including the sub-stages of: (A) powering up the at least one wireless device; (B) reading an ID, which is downloaded from a commissioning tool into a configuration adapter of the at least one wireless device; (C) reading address translation sub-table entries, and using the entries to locate and communicate with each attached wired device; (D) providing an indirect communication link between the wireless and wired networks; (E) using the ID as its radio ID; and (F) reading a SAS, which is downloaded from the commissioning tool into the configuration adapter of wireless device, and using the SAS and radio ID to join a designated wireless network.
0055According to another feature of the method the stage of initializing at least one wired device includes the sub-stages of: (A) powering up the at least one wired device; and (B) reading data, which is downloaded from a commissioning tool into the configuration adapter of the wired device, and using an address for the specific wired communication protocol.
0056According to another feature of the method the stage of bindings formation includes the sub-stages of: (A) using a master controller to initiate a binding process; (B) reading binding information by the master controller, and using a wireless device mapping and an address translation sub-table in a wireless device mapping in order to translate wired logical IDs of wired devices found in the binding information to radio IDs and endpoints; and (C) transmitting binding commands by the master controller.
0057According to the present invention there is provided a control system for controlling of wireless and wired networks, the control system including: (a) a wired network, wherein the wired network includes at least one wired device; and (b) a wired communication link, wherein the wired communication link is connecting the at least one wired device in the wired network.
0058According to further features of the control system, the control system further includes: (c) a wireless device, wherein the wireless device has a wired communication interface for communicating with the wired network through the wired communication link; (d) a wireless network, the wireless network including at least one wireless device; and (e) a wireless communication link, wherein the wireless communication link is interconnecting the at least one wireless devices in the wireless network.
0059According to further features of the control system, the control system further includes: (f) at least one access point, the access point is connected to at least one network wherein the network is selected from a group consisting of the wired network and the wireless network; (g) a master controller with access to a networks scheme; and (h) at least one configuration adapter with a configuration interface and a device contact interface.
0060According to further features of the control system, at least one wired device, at least one commissioning tool, the wireless device, and the at least one access point has a configuration adapter for a complementary configuration link, wherein only the configuration adapter of the commissioning tool must be powered-up during a configuration data loading.
0061According to further features of the control system, the control system further including: (g) a configuration link for downloading configuration data; (h) at least one device contact interface for connecting to each of the at least one wired devices device for reading configuration data; (i) at least one contact device interface for connecting to each of the at least one wireless devices for reading configuration data; (j) a configuration link operating powerless; (k) at least one commissioning tool for downloading configuration data into the configuration adapter of wired devices, into the configuration adapter of access point and into the configuration adapter of wireless devices; (i) at least one device contact interface for connecting to each of the at least one commissioning tools for writing configuration data; and (j) at least one device contact interface for connecting to each of the at least one access point for reading configuration data.
0062According to further features of the control system at least one configuration adapter includes binding information.
<u>BRIEF DESCRIPTION OF THE DRAWINGS</u>
0063The invention is herein described, by way of example only, with reference to the accompanying drawings, wherein: <ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">Figure 1</figref> is a schematic diagram of an embodiment of a design and control systems according to the present invention.</li><li><figref idref="f0002">Figure 2</figref> is a schematic diagram of an embodiment of a control system, according to the present invention.</li><li><figref idref="f0003">Figure 3</figref> is a schematic diagram of an embodiment of a design system, according to the present invention.</li><li><figref idref="f0004">Figure 4</figref> is a schematic block diagram of a commissioning tool, according to the present invention.</li><li><figref idref="f0004">Figure 5</figref> is a schematic block diagram of a wireless device, according to the present invention.</li><li><figref idref="f0005">Figure 6</figref> is a schematic block diagram of an access point, according to the present invention.</li><li><figref idref="f0005">Figure 7</figref> is a schematic block diagram of a configuration adapter, according to the present invention.</li><li><figref idref="f0006">Figure 8</figref> is an example of a networks scheme, installed on a floor of a building, according to the present invention.</li><li><figref idref="f0007">Figure 9</figref> is a flow chart of a process of defining the wired device mapping, according to a method of the present invention.</li><li><figref idref="f0008">Figure 10</figref> is a flowchart of a process of defining the wireless device mapping, according to a method of the present invention.</li><li><figref idref="f0009">Figure 11</figref> is a flowchart of a process of defining an address translation table for wireless devices, according to a method of the present invention.</li><li><figref idref="f0010">Figure 12</figref> is a flowchart of a process of wireless device installation, according to a method of the present invention.</li><li><figref idref="f0011">Figure 13</figref> is a flowchart of a process of wired device installation, according to a method of the present invention.</li><li><figref idref="f0012">Figure 14</figref> is a flowchart of a process of wireless device initialization, according to a method of the present invention.</li><li><figref idref="f0013">Figure 15</figref> is a flowchart of a process of wired device initialization, according to a method of the present invention.</li><li><figref idref="f0014">Figure 16</figref> is a flowchart of a process of bindings formation, according to a method of the present invention.</li><li><figref idref="f0015">Figure 17</figref> is a flowchart of a process of networks design, installation and automatic formation, according to a method of the present invention.</li></ul>
<u>DETAILED DESCRIPTION OF EMBODIMENTS</u>
0064The present invention is of design and control systems, commissioning tools, configuration adapters and a method for wireless and wired networks design, installation and automatic formation including binding of networks devices.
0065The principles and operation of the design and control systems, commissioning tools, configuration adapters and a method for design, installation and automatic networks formation including binding of networks devices according to the present invention may be better understood with reference to the drawings and the accompanying description.
0066Before explaining at least one embodiment of the invention in detail, it is to be understood that the invention is not limited in its application to the details of construction and the arrangement of the components set forth in the following description or illustrated in the drawings.
0067Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The materials, dimensions, methods, and examples provided herein are illustrative only and are not intended to be limiting.
0068The following list is a legend of the numbering of the application illustrations: <dl id="dl0001"><dt>100</dt><dd>design and control systems</dd><dt>101</dt><dd>design system</dd><dt>102</dt><dd>control system</dd><dt>103</dt><dd>master controller</dd><dt>104</dt><dd>commissioning tool</dd><dt>105</dt><dd>wireless network</dd><dt>106</dt><dd>wired network</dd><dt>107</dt><dd>backbone network</dd><dt>200</dt><dd>access point</dd><dt>201</dt><dd>wired device</dd><dt>202</dt><dd>wireless device</dd><dt>203</dt><dd>wireless communication link</dd><dt>204</dt><dd>configuration adapter</dd><dt>205</dt><dd>RF (radio frequency) transceiver</dd><dt>206</dt><dd>wired communication link</dd><dt>207</dt><dd>configuration link</dd><dt>300</dt><dd>design system controller with design application</dd><dt>301</dt><dd>database</dd><dt>302</dt><dd>design system communication interface</dd><dt>400</dt><dd>CT (commissioning tool) controller</dd><dt>401</dt><dd>(design/control) system interface</dd><dt>402</dt><dd>CT (commissioning tool) user interface</dd><dt>500</dt><dd>wireless device controller</dd><dt>501</dt><dd>wired communication interface</dd><dt>502</dt><dd>wireless device user interface</dd><dt>503</dt><dd>sensor interface</dd><dt>600</dt><dd>AP (access point) controller</dd><dt>700</dt><dd>control and memory module</dd><dt>701</dt><dd>device contact interface</dd><dt>702</dt><dd>configuration interface</dd><dt>800</dt><dd>networks scheme</dd><dt>801</dt><dd>wireless large fluorescent</dd><dt>802</dt><dd>wireless standard device</dd><dt>803</dt><dd>wired standard fluorescent in the left wing</dd><dt>804</dt><dd>wired standard fluorescent in the right wing</dd><dt>805</dt><dd>wireless 1- gang switch</dd><dt>806</dt><dd>wireless 3- gang switch</dd><dt>807</dt><dd>left switch</dd><dt>808</dt><dd>middle switch</dd><dt>809</dt><dd>right switch</dd><dt>810</dt><dd>floor #2</dd><dt>811</dt><dd>hallway</dd><dt>812</dt><dd>room #1</dd><dt>813</dt><dd>room #2</dd><dt>814</dt><dd>single switch</dd><dt>815</dt><dd>large fluorescent</dd></dl>
0069As used herein in the specification and in the claim section that follows, the terms: access point, address translation sub-table, binding, cluster, coordinator, commissioning tool, configuration adapter, configuration data, (communication) link, device, end device, end point, HVAC, I<sup>2</sup>C, network, NFC, master controller, PAN, RFID, router, system, networks scheme, SAS, SPI, USB, wired device, wireless device, wireless logical ID , wired logical sub-ID, wired logical ID, wireless device mapping, and wired device mapping, are as specified in the following list: <ul id="ul0002" list-style="none" compact="compact"><li>The term "access point" and the like substantially refer to a device that connects (directly or through communication adapters such as switches) the master controller to the wireless and wired networks.</li><li>The term "address translation sub-table" and the like substantially refer to a translation of the wireless device endpoint identifiers of attached wired devices to their wired communication link address.</li><li>The term "binding" and the like substantially refer to a unidirectional logical link between a source endpoint and a destination endpoint that run the same application.</li><li>The term "cluster" and the like substantially refer to a collection of commands and attributes/states.</li><li>The term "coordinator" and the like substantially refer to a wireless device responsible for starting and maintaining a wireless network.</li><li>The term "commissioning tool" and the like substantially refer to a (usually portable) unit used to deploy and configure devices.</li><li>The term "configuration adapter" and the like substantially refer to a component in a device or connected to a device which receives and stores configuration data.</li><li>The term "configuration data" and the like substantially refer to a set of attributes (such as radio ID and startup attribute set) that determines the initial behavior of the wireless device.</li><li>The term "(communication) link" and the like substantially refer to a means of connecting one device to another for the purpose of transmitting and receiving data.</li><li>The term "device" and the like substantially refer to a system/network component (either a wired device or a wireless device).</li><li>The term "end device" and the like substantially refer to a device that can only communicate with the routers and the coordinator (can't relay messages).</li><li>The term "end point" and the like substantially refer to an addressable component in a wireless device.</li><li>The term "HVAC" and the like substantially refer to heating, ventilation and air conditioning.</li><li>The term "I<sup>2</sup>C" and the like, substantially refer to an inter integrated circuit bus.</li><li>The term "network" and the like substantially refer to a series of devices interconnected by communication links.</li><li>The term "NFC" and the like substantially refer to a near field communication.</li><li>The term "master controller" and the like, substantially refer to a component responsible for the control system management.</li><li>The term "PAN" and the like, substantially refer to a personal area network.</li><li>The term "RFID" and the like substantially refer to radio frequency identification.</li><li>The term "router" and the like substantially refer to a device providing routing/relay services to the network/system.</li><li>The term "system" and the like substantially refer to a collection of elements (hardware & software) that are organized for a common purpose.</li><li>The term "networks scheme" and the like substantially refer to a diagram of the installation site that uniquely identifies each device by its type and its physical location (e.g. a map, or a table on which every device is located by coordinates).</li><li>The term "SAS" and the like, substantially refer to a Startup Attribute Set.</li><li>The term "SPI" and the like substantially refer to a serial peripheral interface bus.</li><li>The term "USB" and the like, substantially refer to a universal serial bus.</li><li>The term "wired device" and the like substantially refer to a device without a wireless transceiver.</li><li>The term "wireless device" and the like substantially refer to a device with a wireless transceiver.</li><li>The term "wireless logical ID" and the like substantially refer to an identifier that identifies each wireless device on the networks scheme by the wireless device location and the wireless device type.</li><li>The term "wired logical sub-ID" and the like substantially refer to an identifier that identifies each wired device attached to each wireless device on the networks scheme by the wired device location and the wired device type.</li><li>The term "wired logical ID" and the like substantially refer to an identifier that identifies each wired device on the networks scheme by the wireless logical ID to which it is attached and its own wired logical sub-ID.</li><li>The term "wireless device mapping" and the like substantially refer to a table which maps the wireless logical ID of each wireless device to its radio ID, SAS and address translation sub-table entries.</li><li>The term "wired device mapping" and the like substantially refer to a table which maps the wired logical ID of each wired device to its wired network address.</li></ul>
Detailed System Description
0070A method for wireless and wired networks design, installation and automatic formation, according to the present invention, is shown in Table 1. <tables id="tabl0001" num="0001"><table frame="all"><title><u>Table 1</u></title><tgroup cols="4"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="35mm" /><colspec colnum="3" colname="col3" colwidth="61mm" /><colspec colnum="4" colname="col4" colwidth="60mm" /><thead><row><entry align="center" valign="top"><b>No</b></entry><entry align="center" valign="top"><b>Stage Name</b></entry><entry align="center" valign="top"><b>Output</b></entry><entry align="center" valign="top"><b>Process</b></entry></row></thead><tbody><row><entry morerows="1"><b>A</b></entry><entry morerows="1">Architectural design</entry><entry morerows="1">Networks scheme and binding table</entry><entry>Define device type and physical location <b>A1</b></entry></row><row><entry>Define binding links between devices <b>A2</b></entry></row><row><entry morerows="4"><b>B</b></entry><entry morerows="4">Electrical design</entry><entry morerows="4">Devices mapping tables</entry><entry>Allocate SAS (Startup Attribute Set) for each device <b>B1</b></entry></row><row><entry>Allocate radio ID <b>B2</b></entry></row><row><entry>Allocate endpoints <b>B3</b></entry></row><row><entry>Allocate wired link addresses <b>B4</b></entry></row><row><entry>Address translation table/sub-table created <b>B5</b></entry></row><row><entry morerows="3"><b>C</b></entry><entry morerows="3">Networks installation</entry><entry morerows="3">Configured and physically installed devices</entry><entry>Remotely access or download the data created in the design stages into the commissioning tool <b>C1</b></entry></row><row><entry>Download configuration data into the configuration adapter of each wired device <b>C2</b></entry></row><row><entry>Download configuration data into the configuration adapter of each wireless device <b>C3</b></entry></row><row><entry>Physically install each device according to its location in the networks scheme <b>C4</b></entry></row><row><entry morerows="1"><b>D</b></entry><entry morerows="1">Networks initialization</entry><entry morerows="1">Powered-up and initialized networks</entry><entry>Wireless devices read the downloaded data and join a wireless network <b>D1</b></entry></row><row><entry>Wired devices read the downloaded data and a wired network is formed <b>D2</b></entry></row><row><entry morerows="1"><b>E</b></entry><entry morerows="1">Bindings formation</entry><entry morerows="1">Binding links between devices</entry><entry>Master controller accesses the data created in the design stages <b>E1</b></entry></row><row><entry>Master controller sends binding commands to the wireless devices <b>E2</b></entry></row></tbody></tgroup></table></tables>
0071The method for wireless and wired networks design, installation and automatic formation includes the follows stages: <b>A)</b> architectural design; <b>B)</b> electrical design; <b>C)</b> networks installation; <b>D)</b> networks initialization and <b>E)</b> bindings formation.
0072During the architectural design stage <b>A,</b> the device types and physical location <b>A1</b> and the binding links <b>A2</b> may be defined. The output of architectural design <b>A</b> may be the networks scheme and the binding table.
0073During the electrical design stage <b>B</b> startup attribute set <b>B1,</b> radio ID <b>B2,</b> endpoints <b>B3</b> and wired (communication) link addresses <b>B4</b> may be allocated to each device and an address translation sub-table may be created <b>B5.</b> The address translation sub-table allows the wireless devices to locate and communicate with each attached wired device, providing an indirect communication link between the wireless and wired networks. The output of the electrical design stage <b>B</b> may be the device mapping tables for the wired and the wireless devices. The device mapping tables map between the devices on the networks scheme and their allocated parameters.
0074During the networks installation stage <b>C</b> the data created in the design stages <b>A</b> and <b>B</b> may be remotely accessed or downloaded into the commissioning tool <b>C1,</b> configuration data from the commissioning tool may be downloaded/set into the configuration adapter of each wired device <b>C2,</b> configuration data from the commissioning tool may be downloaded into the configuration adapter of each wireless device <b>C3</b> and each device is physically installed according to its location in the networks scheme <b>C4.</b> The output of the networks installation <b>C</b> may be configured and physically installed devices.
0075During the networks initialization stage <b>D,</b> the devices are powered-up, the wireless devices may read the downloaded data initialize themselves and join a wireless network <b>D1</b> and the wired devices may read the downloaded/set data, initialize themselves and a wired network is formed. The output of the networks initialization <b>D</b> may be the powered-up and initialized networks.
0076During the bindings formation stage <b>E,</b> data created in the design stages <b>A</b> and <b>B</b> may be accessed by the master controller <b>E1,</b> the master controller may send binding commands to the wireless devices to form logical links between network devices <b>E2.</b> The output of the bindings formation stage E may be binding links between the network devices.
0077Referring now to the drawings, <figref idref="f0001">Figure 1</figref> is a general schematic diagram of an embodiment of a design and control systems <b>100,</b> according to the present invention.
0078The design data created in the architectural and electrical design stages and stored in a design system <b>101</b> may be downloaded into or accessed and used by a master controller <b>103</b> of a control system <b>102</b> to control wireless <b>networks 105</b> and wired networks <b>106.</b> The design data may also be downloaded into or accessed and used by commission tools <b>104</b> for the wireless networks <b>105</b> and wired networks <b>106</b> installation and formation, as explained in the following.
0079The master controller <b>103</b> may have a provision to connect to a backbone network <b>107,</b> a higher level network (such as of a BMS - building management system).
0080The continuous line with arrows indicates that the communication between the connected units is continuous during the systems operation.
0081The dotted lines with arrows indicate that the communication between the connected units may be temporary for specific purposes, as explained in the following.
0082<figref idref="f0002">Figure 2</figref> is a schematic diagram of an embodiment of a control system <b>102</b> according to the present invention.
0083The control system's <b>102</b> main components include wired devices <b>201,</b> wireless devices <b>202,</b> a master controller <b>103,</b> configuration adapters <b>204,</b> access points <b>200</b> and commissioning tools <b>104.</b>
0084Wired devices <b>201</b> are connected through a wired communication link <b>206,</b> such as digital addressable lighting interface (DALI) to wireless devices <b>202</b> or to the access points <b>200.</b> Wireless devices <b>202</b> and access points <b>200</b> may have 0, 1, or more attached wired communication links <b>206.</b> The total number of wired devices <b>201</b> connected to the wireless device <b>202</b> is limited by the maximum number of endpoints available in the wireless device <b>202,</b> as defined by the specific wireless protocol. Wireless devices <b>202</b> with attached wired devices <b>201</b> transfer the network control functions to the wired devices <b>201</b> via the wired communication link <b>206</b> using a wired communication protocol (such as DALI). The wireless devices <b>202</b> include a <b>RF</b> transceiver <b>205</b> for the wireless communication link <b>203,</b> (such as ZigBee) and a configuration adapter <b>204</b> for a complementary contactless or contact configuration link <b>207</b> (such as contactless RFID or wired 1-Wire). The configuration adapter <b>204</b> is used for transferring the configuration data that determines the initial behavior of the device, (wire devices <b>201</b> or wireless devices <b>202)</b> or access points <b>200.</b> Each wired device <b>201</b> has a configuration adapter <b>204</b> for receiving the configuration data required for the initial operation of it. In some networks the configuration adaptor <b>204</b> may be implemented internally in the wired devices <b>201</b> or wireless devices <b>202,</b> and in other networks, the configuration adapter <b>204</b> may be an external component.
0085A master controller <b>103</b> (such as a PC), controls groups of wireless devices <b>202,</b> called wireless networks <b>(105)</b> and groups of wired devices <b>201</b> called wired networks <b>(106).</b>
0086The networks control functions from the master controller <b>103</b> are transferred through the access point <b>200</b> through the wireless communication link 203 or through the wired communication link <b>206.</b>
0087The master controller <b>103</b> may control a plurality of wireless networks <b>(105)</b> and wired networks <b>(106)</b> through different access points <b>200.</b>
0088Commissioning tools <b>104</b> (such as a PDA) may access/download and use the design data created in the design system <b>101</b> to download configuration data through the configuration link <b>207</b> of the configuration adapter <b>204</b> into the wireless devices <b>202</b> into the wired devices <b>201</b> and into the access points <b>200.</b>
0089The master controller <b>103</b> may use the access points <b>200</b> with configuration adapters <b>204</b> as commissioning tools <b>104.</b>
0090<figref idref="f0003">Figure 3</figref> is a schematic diagram of an embodiment of the design system <b>101</b> according to the present invention.
0091The design system's <b>101</b> main components include database <b>301,</b> design system controller with design application <b>300</b> and design system communication interface <b>302.</b>
0092The design data created by the design system controller with the design application <b>301</b> (such as a PC) may be stored in the database <b>301.</b> The database <b>301</b> stores the networks scheme, device mapping tables and binding information. The database <b>301</b> may be accessed by downloaded into or the master controller <b>103</b> and by the commissioning tools <b>104</b> through the design system communication interface <b>302.</b>
Detailed Devices Description
0093<figref idref="f0004">Figure 4</figref> is a schematic block diagram of a CT (commissioning tool) <b>104,</b> according to the present invention.
0094The control/design system interface <b>401</b> may be a standard serial communication interface (such as USB or Ethernet), wireless interface (such as Wi-Fi) or a cellular interface (such as GSM) and is used to connect the commissioning tool 104, to the master controller <b>(103),</b> not shown in the present illustration, to a local storage media (such as a CD) not shown in the present illustration, or to the design system <b>(101),</b> not shown in the present illustration, and to remotely access or load the design data. The configuration adapter <b>204</b> is used to download the configuration data, through the configuration link <b>207,</b> into the configuration adapter <b>204</b> in the devices.
0095The download can be carried out by contactless technologies (such as RFID/NFC) or by contact technologies (such as 1-Wire). The RF transceiver <b>205</b> is used to connect to the wireless network <b>105</b> through the wireless communication link 203 for purposes such as testing and maintenance.
0096The wireless network <b>105</b> may be implemented by a low-rate, low-power wireless standard protocol (such as ZigBee). The CT controller 400 coordinates the functioning of the device and may be implemented by a standard microcontroller. The CT user interface <b>402</b> allows the user to perform operations such as to browse through the networks scheme or device mapping tables, to select the appropriate downloadable data and to initiate operations such as download data, read back, etc. The CT user interface <b>402</b> may be implemented by standard interface technologies (such as touch screen and push buttons).
0097<figref idref="f0004">Figure 5</figref> is a schematic block diagram of a wireless device <b>202,</b> according to the present invention.
0098The wired communication interface <b>501</b> may be a standard communication interface for control (such as DALI) and is used to connect the wireless device <b>202</b> to the wired network <b>106,</b> through the wired communication link <b>206.</b> The configuration adapter <b>204</b> is used to receive the configuration data, through the configuration link <b>207,</b> downloaded from the commissioning tool <b>(104),</b> and not shown in the present illustration. In case that the master controller <b>(103),</b> not shown in the present illustration, is used as a commissioning tool <b>(104),</b> not shown in the present illustration, the configuration adapter (of access point) <b>204</b> is used to download the configuration data into the configuration adapter <b>204</b> of the devices, through the configuration link <b>207.</b>
0099The download may be carried out by contactless technologies (such as RFID/NFC) or by contact technologies (such as 1-Wire). The RF transceiver <b>205</b> may be used to connect to the wireless network <b>(105)</b> through the wireless communication link <b>203.</b> It may be implemented by a low-rate, low-power wireless standard protocol (such as ZigBee). The sensor interface <b>503</b> connects the wireless device <b>(202),</b> not shown in the present illustration, to different types of sensors (such as presence, temperature and lighting intensity) through a standard sensor interface bus (such as I<sup>2</sup>C or 1-Wire). The wireless device controller <b>500</b> coordinates the functioning of the device and may be implemented by a standard microcontroller. The wireless device user interface <b>502</b> allows the user to perform operations such as to manually control the wired devices <b>(201),</b> set parameters for interaction with sensors, not shown in the present illustration, etc. The wireless device user interface <b>502</b> may be implemented by standard interface technologies (such as touch screen and push buttons).
0100<figref idref="f0005">Figure 6</figref> is a schematic block diagram of AP (access point) <b>200,</b> according to the present invention.
0101The design/control system interface <b>401</b> may be a standard communication interface (such as USB, Ethernet or Wi-Fi) and is used to connect the access point (200), not shown in the present illustration, (directly or through an interface gateway) to the master controller <b>(103),</b> not shown in the present illustration. The wired communication interface <b>501</b> may be a standard communication interface for control (such as DALI) and is used to connect the access point <b>200</b> to wired networks <b>106</b> through the wired communication link <b>206.</b> The access point <b>(200),</b> not shown in the present illustration, allows the master controller <b>(103),</b> not shown in the present illustration, to control the wireless networks <b>105,</b> through the wireless communications link <b>(203),</b> or to control the wired networks <b>106</b> through the wired communications link <b>(206).</b> The configuration adapter <b>204</b> is used to receive the configuration data, through the configuration link <b>207,</b> downloaded from the commissioning tool <b>(104),</b> and not shown in the present illustration. The download may be carried out by contactless technologies (such as RFID/NFC) or by contact technologies (such as 1-Wire). The RF transceiver <b>205</b> may be used to connect to the wireless network <b>(105)</b> through the wireless communication link <b>203.</b> The wireless network <b>(105)</b> may be implemented by a low-rate, low-power wireless standard protocol (such as ZigBee). The AP controller <b>600</b> coordinates the functioning of the device and may be implemented by a standard microcontroller.
0102<figref idref="f0005">Figure 7</figref> is a schematic block diagram of a configuration adapter <b>204,</b> according to the present invention.
0103The configuration interface <b>702</b> is used to load the configuration data downloaded from the commissioning tool <b>(104),</b> not shown in the present illustration, through the configuration link <b>207.</b>
0104The configuration adapter <b>204</b> may be differently implemented in hardware in the CT (commissioning tool), AP (access point) and in the wired and wireless devices, but the configuration interface <b>702</b> implements identical configuration link communication protocols (such as ISO 14443).
0105The data load may be carried out by contactless technologies (such as RFID/NFC) or by contact technologies (such as 1-Wire). The control and memory module <b>700</b> may be used to store the loaded configuration data and to control the adapter. The configuration adapter <b>204</b> in the wireless devices <b>(202),</b> wired devices <b>(201)</b> and access points <b>(202)</b> (not shown in the present illustration), may not necessarily be powered-up during the configuration data load. The configuration data may be read by the devices through the device contact interface <b>701.</b> The device contact interface <b>701</b> may be a standard communication interface (such as SPI or 1-Wire) or a standard control interface (such as DALI).
Detailed Method Description
Architectural Design
(No. A of Table 1)
0106A networks scheme of the system <b>102</b> to be installed may be defined, where each wireless and wired device has a (wired or wireless) logical ID that specifies its type and a physical location. The type of the device may be later used by the networks installers to install the correct type of device in the specified physical location.
0107<figref idref="f0006">Figure 8</figref> is an example of a networks scheme <b>800,</b> installed on a storey of a building, according to the present invention. The system includes the following components: master controller <b>103,</b> access point <b>200,</b> a wireless large fluorescent <b>801,</b> a wireless standard device <b>802</b> connected to wired standard fluorescents in the left wing <b>803</b> and to wired standard fluorescents in the right wing <b>804,</b> a wireless 1-gang switch <b>805</b> and a wireless 3-gang switch <b>806.</b>
0108The networks scheme <b>800</b> is a map of the installation site, and the physical location for each device may be its coordinates on the map. In the example a physical location of the wireless 3-gang switch <b>806</b> may be [floor#2 <b>810,</b> hallway <b>811].</b> The physical location may contain additional parameters such as building number, wall or ceiling, etc. The type of the switch wireless device is wireless 3-gang switch <b>806.</b> The pair (type, physical location) is referred to as wireless logical ID and uniquely identifies each device (i.e. no two devices have the same logical ID). In the example, the wireless logical ID for the device is (wireless 3-gang switch 806, [floor#2 <b>810,</b> hallway <b>811]).</b> The type may further include more parameters such as manufacturer name, production date, version number, etc.
0109For wired devices <b>201,</b> the device wired logical ID may be comprised of its wireless device's wireless logical ID and the wired devices own wired logical sub-ID. In the example, a wired logical ID of a wired device <b>201</b> may be: (wireless 3-gang switch, <b>806</b> [floor#2 <b>810,</b> hallway <b>811],</b> left switch <b>807,</b> [floor#2 <b>810,</b> hallway <b>811]).</b> In this case the wired logical sub-ID of the switch is (left switch <b>807,</b> [floor#2 <b>810,</b> hallway <b>811]).</b>
0110Binding information may be defined. A binding is a unidirectional logical link between a source endpoint (which initiate an operation) and a destination endpoint (which is designated to perform the operation) that run the same application. Bindings allow connections between different devices running a similar application. For example a switch and ballast that run a home automation application. The binding information is a set of entries. Each entry contains a pair of wired logical IDs of the bound devices. A binding entry may also contain other data needed to bind the devices. This information may vary according to the communication protocol. An example of other data contained in each binding entry, (incase ZigBee is used as the communication protocol), is a list of cluster IDs. A cluster ID identifies a cluster and is associated with data flowing out of, or into the device. Cluster IDs are unique within the scope of a specific application. For example, a cluster may be associated with turning a device on/off in a home automation application.
0111An example of binding information entries is shown in Table 2. <tables id="tabl0002" num="0002"><table frame="all"><title><b><u>Table 2</u></b></title><tgroup cols="4"><colspec colnum="1" colname="col1" colwidth="14mm" /><colspec colnum="2" colname="col2" colwidth="66mm" /><colspec colnum="3" colname="col3" colwidth="66mm" /><colspec colnum="4" colname="col4" colwidth="22mm" /><thead><row><entry align="center" valign="top"><b>Entry</b></entry><entry align="center" valign="top"><b>Output Wired Logical ID</b></entry><entry align="center" valign="top"><b>Input Wired Logical ID</b></entry><entry align="center" valign="top"><b>Cluster IDs</b></entry></row></thead><tbody><row><entry align="center">21</entry><entry align="center">(wireless 3-gang switch, [floor#2, hallway], right switch, [floor#2, hallway])</entry><entry align="center">(wireless large fluorescent, [floor#2, room#1], large fluorescent, [floor#2, room#1])</entry><entry align="center">ID1, ID2</entry></row><row><entry align="center">22</entry><entry align="center">(wireless 3-gang switch, [floor#2, hallway], middle switch, [floor#2, hallway])</entry><entry align="center">(wireless standard device, [floor#2, hallway], wired standard fluorescent, [floor#2, hallway, right wing])</entry><entry align="center">ID1, ID2</entry></row><row><entry align="center">23</entry><entry align="center">(wireless 3-gang switch, [floor#2 hallway], left switch, [floor#2, hallway])</entry><entry align="center">(wireless standard device, [floor#2, hallway], wired standard fluorescent, [floor#2, hallway, left wing])</entry><entry align="center">ID1, ID2</entry></row><row><entry align="center">24</entry><entry align="center">(wireless 1-gang switch, [floor#2, hallway], single switch, [floor#2, hallway])</entry><entry align="center">(wireless standard device, [floor#2, room#1], large fluorescent, [floor#2, room#1])</entry><entry align="center">ID1, ID2</entry></row><row><entry align="center">25</entry><entry align="center">(wireless 1-gang switch, [floor#2, hallway], single switch, [floor#2, hallway])</entry><entry align="center">(wireless standard device, [floor#2, hallway], wired standard fluorescent, [floor#2, hallway, right wing])</entry><entry align="center">ID1, ID2</entry></row><row><entry align="center">26</entry><entry align="center">(wireless 1-gang switch, [floor#2, hallway], single switch, [floor#2, hallway])</entry><entry align="center">(wireless standard device, [floor#2, hallway], wired standard fluorescent, [floor#2, hallway, left wing])</entry><entry align="center">ID1, ID2</entry></row></tbody></tgroup></table></tables>
0112In the example of Table 2, which refers to the example networks scheme shown in <figref idref="f0006">Figure 8</figref>, the right switch <b>809</b> is bound to the large fluorescent <b>815</b> in room#1 <b>812,</b> the middle switch <b>808</b> is bound to the wired standard fluorescent in the right wing <b>804</b> of the hallway <b>811,</b> the left switch <b>807</b> is bound to the wired standard fluorescent in the left wing <b>803</b> of the hallway <b>811,</b> and the single switch <b>814</b> is bound to the large fluorescent <b>815</b> in room#1 <b>812,</b> to the wired standard fluorescent in the right wing <b>804</b> of the hallway <b>811</b> and to the wired standard fluorescent in the left wing <b>803</b> of the hallway <b>811.</b>
0113The binding information is organized in the table as follows: Entry <b>21</b> contains the wired logical ID of the right switch device <b>809</b> (comprised of the wireless device's wireless logical ID and its own wired logical sub-ID within the context of the wireless device, wireless 3-gang switch <b>806),</b> and the wired logical ID of the large fluorescent <b>815</b> in room #1 <b>812.</b> Entry <b>22</b> contains the wired logical ID of the middle switch device <b>808,</b> and the wired logical ID of the wired standard fluorescent <b>804</b> in the right wing of the hallway <b>811.</b> Entry <b>23</b> contains the wired logical ID of the left switch device <b>807,</b> and the wired logical ID of the wired standard fluorescent <b>803</b> in the left wing of the hallway <b>811.</b>
0114Entry <b>24</b> contains the wired logical ID of the single switch device <b>814</b> (comprised of the wireless device's wireless logical ID and its own wired logical sub-ID within the context of the wireless device, wireless 1-gang switch - <b>805),</b> and the wired logical ID of the large fluorescent <b>815</b> in room #1 <b>812.</b> Entry <b>25</b> contains the wired logical ID of the same single switch device <b>814,</b> and the wired logical ID of the wired standard fluorescent in the right wing <b>804</b> of the hallway <b>811.</b> Entry <b>26</b> contains the wired logical ID of the single switch device <b>814,</b> and the wired logical ID of the wired standard fluorescent in the left wing <b>803</b> of the hallway <b>811.</b>
0115In this example (where ZigBee is used as the communication protocol and the devices are running a home automation application), each entry also contains a list of cluster IDs associated with lighting control (last column in the Table 2).
0116An illustration of a wired devices mapping table is shown in Table 3. <tables id="tabl0003" num="0003"><table frame="all"><title><b><u>Table 3</u></b></title><tgroup cols="3"><colspec colnum="1" colname="col1" colwidth="14mm" /><colspec colnum="2" colname="col2" colwidth="93mm" /><colspec colnum="3" colname="col3" colwidth="60mm" /><thead><row><entry valign="top"><b>Entry</b></entry><entry align="center" valign="top"><b>Wired Logical ID</b></entry><entry align="center" valign="top"><b>Wired Communication Link Address</b></entry></row></thead><tbody><row><entry>31</entry><entry>(wireless 3-gang switch, [floor#2, hallway], right switch, [floor#2, hallway])</entry><entry align="center">11</entry></row><row><entry>32</entry><entry>(wireless 3-gang switch, [floor#2 hallway], middle switch, [floor#2, hallway])</entry><entry align="center">12</entry></row><row><entry>33</entry><entry>(wireless 3-gang switch, [floor#2, hallway], left switch, [floor#2, hallway])</entry><entry align="center">13</entry></row><row><entry>34</entry><entry>(wireless standard device, [floor#2, hallway], wired standard fluorescent, [floor#2, hallway, right wing])</entry><entry align="center">11</entry></row><row><entry>35</entry><entry>(wireless standard device, [floor#2, hallway], wired standard fluorescent, [floor#2, hallway, left wing])</entry><entry align="center">12</entry></row><row><entry>36</entry><entry>(wireless 1-gang switch, [floor#2, hallway], single switch, [floor#2, hallway])</entry><entry align="center">34</entry></row><row><entry>37</entry><entry>(wireless large fluorescent, [floor#2, room#1], large fluorescent, [floor#2, room#1])</entry><entry align="center">46</entry></row></tbody></tgroup></table></tables>
Electrical Design
(No. B of Table 1)
0117A wired device mapping may be created for the wired devices <b>201.</b> For example, Table 3 illustrates the wired devices' mapping table for the example control system scheme shown in <figref idref="f0006">Figure 8</figref>, according to the method of the present invention. For each wired device <b>201</b> on the networks scheme of <figref idref="f0006">Figure 8</figref>, the wired device <b>201</b> mapping maps the wired logical ID of the wired device <b>201</b> to its wired communication link <b>206</b> address used by the implemented wired communication protocol. The wired communication link <b>206</b> address for each wired device <b>201</b> may be automatically allocated by the master controller <b>103,</b> (stage <b>902</b> of the process of defining the wired device mapping, according to a method of the present invention, shown as a flowchart in <figref idref="f0007">Figure 9</figref>).
0118This address may be later loaded into or accessed by the commissioning tool <b>104</b> and downloaded into the wired device <b>201.</b> The entry <b>31</b> of the wired devices mapping (Table 3) specifies that the right switch <b>809</b> (in the hallway <b>811</b> of floor #2 <b>810)</b> that is connected to the wireless 3-gang switch <b>806</b> (in the hallway <b>811</b> of floor #2 <b>810)</b> has an address of 11 (arbitrary number) in the wireless 3- gang switch <b>806</b> wired communication link, not shown in this example. The entry <b>32</b> of the wired devices mapping table example of table 3 specifies that the middle switch <b>808</b> (in the hallway <b>811</b> of floor #2 <b>810)</b> that is connected to the wireless 3-gang switch <b>806</b> (in the hallway <b>811</b> of floor #2 <b>810)</b> has an address of 12 (arbitrary number) in the wireless 3-gang switch <b>806</b> wired communication link, not shown in this example. The entry <b>33</b> of the wired devices mapping table example (Table 3) specifies that the left switch <b>807</b> (in the hallway <b>811</b> of floor <b>#2 810)</b> that is connected to the wireless 3-gang switch <b>806</b> (in the hallway <b>811</b> of floor #2 <b>810)</b> has an address of 13 (arbitrary number) in the wireless 3-gang switch <b>806</b> wired communication link, not shown in this example. The entry <b>34</b> of the wired devices mapping table example (Table 3) specifies that the wired standard fluorescent in the right wing <b>804</b> (in the hallway <b>811</b> of floor #2 <b>810)</b> that is connected to the wireless standard device <b>802</b> (in the hallway <b>811</b> of floor #2 <b>810)</b> has an address of 11 (arbitrary number) in the standard fluorescent wired communication link. The entry <b>35</b> of the wired devices mapping table example (Table 3) specifies that the wired standard fluorescent in the left wing <b>803</b> (in the hallway <b>811</b> of floor #2 <b>810)</b> that is connected to the wireless standard device <b>802</b> (in the hallway <b>811</b> of floor #2 <b>810)</b> has an address of 12 (arbitrary number) in the standard fluorescent wired communication link (not shown in this example). The entry <b>36</b> of the wired devices <b>201</b> mapping table example (Table 3) specifies that the single switch <b>814</b> (in the hallway <b>811</b> of floor #2 <b>810)</b> that is connected to the wireless 1-gang switch <b>805</b> (in the hallway <b>811</b> of floor #2 <b>810)</b> has an address of <b>34</b> (arbitrary number) in the single switch <b>814</b> wired communication link, not shown in this example. The entry <b>37</b> of the wired devices mapping table example (Table 3) specifies that the large fluorescent <b>815</b> (in the room #1 <b>812</b> of floor #2 <b>810)</b> that is connected to the wireless large fluorescent <b>801</b> (in the room #1 <b>812</b> of floor #2 <b>810)</b> has an address of <b>46</b> (arbitrary number) in the large fluorescent wired communication link, not shown in this example.
0119<figref idref="f0007">Figure 9</figref> is a flowchart of a process of defining the wired device mapping, according to a method of the present invention.
0120The process of defining the wired device mapping including the sub-stages of: <ul id="ul0003" list-style="none" compact="compact"><li>● starting the process of defining the wired device mapping <b>900;</b></li><li>● using the master controller to automatically insert the wired logical ID of each wired device to wired device mapping <b>901;</b></li><li>● using the master controller to automatically allocate addresses for wired devices <b>902;</b> and</li><li>● ending the process of defining the wired device mapping <b>903.</b></li></ul>
0121<figref idref="f0008">Figure 10</figref> is a flowchart of a process of defining the wireless device mapping, according to a method of the present invention.
0122A wireless device mapping is created for wireless devices. For each wireless device (202) on the networks scheme, the wireless device mapping maps the wireless logical ID of the device to a unique radio ID (wireless communication link address) and startup attribute set (SAS).
0123The SAS of a wireless device is a set of attributes that determines the initial behavior of the device. Such a set may include: <ul id="ul0004" list-style="none" compact="compact"><li>● Startup parameters which determine how the device should join a network. <ul id="ul0005" list-style="none" compact="compact"><li>● The PAN (personal area network) ID of the network.</li></ul></li><li>● The channel mask which determines the channels that the device should scan to find a network to join.</li><li>● Security data e.g. network key.</li><li>● Additional parameters (such as operation mode).</li></ul>
0124The SAS for each wireless device may be defined, (stage <b>1001),</b> after a study at the installation site to determine desired parameters (e.g. available PAN IDs, available channels).
0125The unique radio ID, (stage <b>1004),</b> for each wireless device is automatically defined by the master controller <b>(103).</b>
0126The process of defining the wireless device mapping including the stages of: <ul id="ul0006" list-style="none" compact="compact"><li>● starting the process of defining the wireless device mapping <b>1000;</b></li><li>● defining the SAS for each wireless device on the networks scheme <b>1001;</b></li><li>● using the master controller to start creating a device mapping from the wireless logical ID of each wireless device and its SAS <b>1002;</b></li><li>● using the master controller to initiate radio ID allocation <b>1003;</b></li><li>● using the master controller to allocate radio ID for each wireless logical ID <b>1004;</b></li><li>● forming an additional address translation sub-table which specifies, for each wireless device, the attached wired devices' wired communication link address and endpoint <b>1005;</b> and</li><li>● ending the process of defining the wireless device mapping <b>1006.</b></li></ul>
0127An illustration of a wireless devices mapping table is shown in Table 4. <tables id="tabl0004" num="0004"><img file="EP2215872B1_D0001.tif" /></tables>
0128The entry (A) of the wireless device mapping table example (Table 4) specifies that the access point device (200) (in the room #1 (S12) of floor #2 (810)) is assigned a radio ID (wireless communication link address) of 16 (arbitrary number), and is also assigned a startup attribute set (SAS) which includes its join mode (as a coordinator) and other startup attributes.
0129The second entry (B) of the wireless device mapping table example (Table 4) specifies that the wireless 3-gang switch (806) (in the hallway (811) of floor #2 (810)) is assigned a radio ID of 13 (arbitrary number), and is also assigned a startup attribute set (SAS) which includes its join mode (as an end device) and other startup attributes.
0130<figref idref="f0009">Figure 11</figref> is a flowchart of a process of defining an address translation sub-table for a wireless device (202), according to a method of the present invention.
0131The process of defining an address translation sub-table for wireless devices including the stages of: <ul id="ul0007" list-style="none" compact="compact"><li>● starting the process of defining an address translation sub-table for wireless devices 1100;</li><li>● using the master controller to initiate address translation sub-table calculation 1101;</li><li>● using the master controller to automatically take for each wireless device, the wired logical sub-ID and wired communication link address for each wired device attached to the wireless device from the wired device mapping and fill them in the address translation sub-table 1102;</li><li>● entering for each wired device its endpoint manually, or automatically after calculating it by the master controller 1103; and</li><li>● ending the process of defining an address translation sub-table for wireless devices 1104.</li></ul>
0132The address translation sub-table (in Table 4), of the wireless device mapping (Table 4) translates endpoint identifiers (used in the implemented wireless protocol) of wired devices, attached to each wireless device, to their wired communication link address used by the implemented wired communication protocol. The address translation sub-table (in Table 4) allows the wireless device (202) to address wired devices 201 in the wired network (106).
0133The wired logical sub-ID and wired communication link address parameter of each wired device (201) in the address translation sub-table (in Table 4) is calculated by the master controller (103), by reading the wired logical IDs and wired communication link addresses of attached wired devices from the wired device mapping 1102.
0134The endpoint parameter of each wired device in the address translation sub-table (in Table 4) may be either manually entered or automatically calculated by the master controller 1103.
0135In the example of Table 4, consider the three entries of the address translation sub-table that correspond to the second entry (B) of the wireless device mapping table example (entries 42, 43, 44). These address translation sub-table entries contain the address translation data of the wired devices attached to the wireless 3-gang switch (806) in the hallway (811) of floor #2 810. The first entry (entry 42), specifies that the wired right switch device (809) connected to the wireless 3-gang switch (806) is assigned an endpoint of 1 (arbitrary number) and a wired communication link address of 11 (as specified in entry 31 of the wired device mapping in Table 3). The second entry, (entry 43), specifies that the middle switch (808) is assigned an endpoint of 2 (arbitrary number) and a wired communication link address of 12 (as specified in entry 32 of the wired device mapping in Table 3). The third entry (entry 44), specifies that the left switch <b>807</b> is assigned an endpoint of 3 (arbitrary number) and a wired communication link address of 13 (as specified in entry 33 of the wired device mapping in Table 3).
0136The entry <b>(C)</b> of the wireless device mapping table example (Table 4) specifies that the wireless standard device <b>(802)</b> (in the hallway <b>(811)</b> of floor #2 <b>(810))</b> is assigned a radio ID of 24 (arbitrary number), and is also assigned a startup attribute set (SAS) which includes its join mode (as a router) and other startup attributes.
0137Consider the two entries of the address translation sub-table that correspond to the entry <b>(C)</b> of the wireless device mapping table example (entries <b>45, 46).</b> These address translation sub-table entries contain the address translation data of the wired devices attached to the wireless standard device <b>(802)</b> in the hallway <b>(811)</b> of floor #2 <b>810.</b> The first entry (entry <b>45),</b> specifies that the wired standard fluorescent in the right wing device <b>(804)</b> connected to the wireless standard device <b>(802)</b> is assigned an endpoint of 1 (arbitrary number) and a wired communication link address of 11 (as specified in entry <b>34</b> of the wired device mapping in Table 3). The second entry (entry <b>46),</b> specifies that the wired standard fluorescent in the left wing <b>(803)</b> is assigned an endpoint of 2 (arbitrary number) and a wired communication link address of 12 (as specified in entry <b>35</b> of the wired device mapping in Table 3).
0138The entry <b>(D)</b> of the wireless device mapping table example (Table 4) specifies that the wireless large fluorescent <b>(801)</b> (in the room #1 <b>(812)</b> of floor #2 <b>(810))</b> is assigned a radio ID of 25 (arbitrary number), and is also assigned a startup attribute set (SAS) which includes its join mode (as a router) and other startup attributes.
0139Consider the entry of the address translation sub-table that corresponds to entry <b>(D)</b> of the wireless device mapping table example (entry <b>47).</b> This entry specifies that the large fluorescent device <b>(815)</b> in the room #1 <b>(812)</b> of floor #2 <b>(810),</b> (connected to the wireless large fluorescent device <b>(801),</b> is assigned an endpoint of 5 (arbitrary number) and a wired communication link address of 46 (as specified in entry 37 of the wired device mapping in Table 3).
0140The entry (E) of the wireless device mapping table example (Table 4) specifies that the wireless 1-gang switch <b>(805)</b> (in the hallway <b>(811)</b> of floor #2 <b>(810))</b> is assigned a radio ID of 18 (arbitrary number), and is also assigned a startup attribute set (SAS) which includes its join mode (as an end-device) and other startup attributes.
0141Consider the entry of the address translation sub-table that corresponds to entry (E) of the wireless device mapping table example (entry <b>48).</b> This entry specifies that the single switch device <b>(814)</b> in the hallway <b>(811)</b> of floor #2 <b>(810),</b> (connected to the wireless 1-gang switch device <b>(805),</b> is assigned an endpoint of 4 (arbitrary number) and a wired communication link address of 34 (as specified in entry <b>36</b> of the wired device mapping in Table 3).
0142The master controller <b>(103)</b> has access to the device mappings. Access may either be local (e.g. CD), or remote access (e.g. a remote database <b>(301)).</b>
Networks Installation
(Item C of Table 1)
0143In this stage the wireless devices and wired devices are installed.
0144<figref idref="f0010">Figure 12</figref> is a flowchart of a process of wireless device <b>(202)</b> installation, according to a method of the present invention.
0145The process of defining a wireless device installation including the stages of: <ul id="ul0008" list-style="none" compact="compact"><li>● starting the process of defining a wireless device installation <b>1200;</b></li><li>● physically installing a wireless device <b>(202)</b> according to type and location taken from the networks scheme as it appears on the commissioning tool <b>1201;</b></li><li>● marking the physically installed wireless device <b>(202)</b> on the commissioning tool <b>1202;</b></li><li>● attaching/bringing into proximity (or contact) the commissioning tool with the physically installed configuration adapter of wireless device <b>1203;</b></li><li>● initiating data download from the commissioning tool to the configuration adapter <b>204</b> of the wireless device using the tool's user interface (no need to power-up the configuration adapter <b>204</b> of the wireless device and the wireless device) <b>1204;</b> and</li><li>● ending the process of defining a wireless device installation <b>1205.</b></li></ul>
0146The commissioning tool <b>(104)</b> is attached or brought into proximity or contact with the configuration adapter <b>204</b> of wireless device <b>(202),</b> (stage <b>1203).</b> Configuration data taken from the wireless device mapping is downloaded from the commissioning tool into the configuration adapter <b>204</b> of wireless device <b>(202),</b> (stage <b>1204).</b> For each wireless device, the configuration data includes its radio ID, SAS (Startup Attribute Set) and its address translation sub-table entries.
0147The configuration data may also include the binding information if the memory size in the configuration adapter is large enough. The order of the stages <b>1203/1204</b> and <b>1201</b> can be interchanged for the convenience of the installer.
0148<figref idref="f0011">Figure 13</figref> is a flowchart of a process of wired device <b>(201)</b> installation, according to a method of the present invention. <ul id="ul0009" list-style="none" compact="compact"><li>● The process of defining a wired device <b>(201)</b> installation including the stages of:</li><li>● starting the process of defining a wired device installation <b>1300;</b></li><li>● physically installing a wired device according to type and location taken from the networks scheme as it appears on the commissioning tool <b>(104) 1301;</b></li><li>● marking the physically installed wired device on the commissioning tool <b>(104) 1302;</b></li><li>● attaching/bringing into proximity (or contact) the commissioning tool <b>(104)</b> with the physically installed configuration adapter <b>204</b> of the wired device <b>(201) 1303;</b></li><li>● initiating data download from the commissioning tool <b>(104)</b> to the configuration adapter <b>204</b> of the wired device <b>(201)</b> using the tool's user interface (no need to power-up the configuration adapter <b>204</b> of the wired device and the wired device) <b>1304;</b> and</li><li>● ending the process of defining a wired device installation <b>1305.</b></li></ul>
0149For the wired devices <b>(201),</b> the configuration data taken from the wired device mapping that was downloaded to the commissioning tool <b>(104)</b> includes the wired communication link address of each wired device. This data is downloaded into the configuration adapter <b>204</b> of wired devices <b>(202).</b>
0150The order of the stages <b>1303/1304</b> and <b>1301</b> can be interchanged for the convenience of the installer.
0151The configuration adapter <b>204</b> of wireless devices <b>(201)</b> and the wired devices <b>(202)</b> don't need to be powered up during this stage.
Networks Initialization
(Item D of Table 1)
0152The wireless devices <b>(202)</b> and wired devices <b>(201)</b> may be powered up and automatically initialize themselves.
0153<figref idref="f0012">Figure 14</figref> is a flowchart of a process of wireless device <b>(202)</b> initialization, according to a method of the present invention.
0154The process of defining wireless device initialization including the stages of: <ul id="ul0010" list-style="none" compact="compact"><li>● starting the process of defining wireless device initialization <b>1400;</b></li><li>● powering up wireless device <b>(202) 1401;</b></li><li>● reading the radio ID, SAS and address translation sub-table entries (downloaded from the commissioning tool <b>(104))</b> from the configuration adapter <b>204</b> of the wireless device <b>(202) 1402;</b></li><li>● using the radio ID and SAS to join the designated wireless network accordingly, and using the address translation sub-table entries to locate and communicate with each attached wired device<b>1403</b>; and</li><li>● ending the process of defining wireless device initialization <b>1404.</b></li></ul>
0155After a wireless device <b>202</b> is powered-up, it initializes itself. Each wireless device <b>(202)</b> reads, from its configuration adapter <b>204,</b> the information downloaded by the commissioning tool <b>104</b> (stage <b>1402),</b> and uses the radio ID and SAS to join the wireless network according to the join mode (Table 4) either as a coordinator responsible for starting and maintaining the network, or as a specific device (router or end device), and uses its address translation sub-table entries to locate and communicate with each attached wired device (stage <b>1403).</b>
0156<figref idref="f0013">Figure 15</figref> is a flowchart of a process of wired device <b>(201)</b> initialization, according to a method of the present invention.
0157The process of defining wired device <b>(201)</b> initialization including the stages of: <ul id="ul0011" list-style="none" compact="compact"><li>● starting the process of defming wired device <b>(201)</b> initialization <b>1500;</b></li><li>● powering up wired device <b>(201) 1501;</b></li><li>● reading the data (downloaded from the commissioning tool <b>(104))</b> from the configuration adapter <b>204</b> of wired device <b>(201)</b> and using the wired communication link address for the specific wired communication protocol <b>1502;</b> and</li><li>● ending the process of defining wired device initialization <b>1503.</b></li></ul>
0158After a wired device <b>(201)</b> is powered-up, it initializes itself. Each wired device <b>(201)</b> reads from the configuration adapter <b>(204)</b> the information downloaded by the commissioning tool <b>(104).</b> The information may be used by the wired device <b>(201)</b> to initialize its wired communication link address for the specific wired communication protocol, (stage <b>1502).</b>
Bindings Formation
(Item E of Table 1)
0159<figref idref="f0014">Figure 16</figref> is a flowchart of a process of bindings formation, according to a method of the present invention.
0160The process of defining bindings formation includes the stages of: <ul id="ul0012" list-style="none" compact="compact"><li>● starting the process of defining bindings formation <b>1600;</b></li><li>● using the master controller to initiate binding process <b>1601;</b></li><li>● reading the binding information by the master controller <b>(103),</b> and using the address translation sub-table in the wireless device mapping in order to translate the wired logical IDs of the devices found in the binding information to radio IDs and endpoints <b>1602;</b></li><li>● transmitting binding commands by the master controller <b>1603;</b> and</li><li>● ending the process of defining bindings formation <b>1604.</b></li></ul>
0161Binding links are formed. The master controller <b>(103)</b> reads the binding information from the database <b>(301),</b> and uses the wireless device mapping and address translation sub-table in the wireless device mapping (Table 4) in order to translate the wired logical IDs of the devices found in the binding information to radio IDs and endpoints, (stage <b>1602).</b> After the translation, the master controller <b>(103)</b> sends binding commands. The binding commands contain the radio IDs of the bound wireless devices (202), their endpoints, and the other binding information that may exist in the binding Table 4 (e.g. a list of cluster IDs).
Attaching Devices to the System after the Networks Formation
0162The method of attaching a device to the control system <b>(102)</b> after the networks formation is similar to the initial method. The wireless <b>(202)</b> or wired device <b>(201)</b> is first added to the networks scheme and registered with all the required parameters (such as type, physical location and binding). The device is inserted to the relevant device mapping table and to the binding table (Table 2), if necessary (for wired devices). The configuration data from the commissioning tool is loaded into the configuration adapter <b>(204)</b> of the device, wireless device <b>(202)</b> or wired device <b>(201)</b> is physically installed in the designated location, and the master controller <b>(103)</b> sends binding commands, if necessary (for wired devices), using the updated binding table.
0163<figref idref="f0015">Figure 17</figref> is a flowchart of a method of networks design, installation and formation, according to the present invention.
0164The method of networks design, installation and formation comprises the main stages of: <ul id="ul0013" list-style="none" compact="compact"><li>● starting the networks design, installation and formation <b>1800;</b></li><li>● designing the networks <b>1801;</b></li><li>● installing the networks <b>1802;</b></li><li>● forming the networks <b>1803;</b> and</li><li>● ending the networks design, installation and formation <b>1804.</b></li></ul>
0165The main stage of starting the networks design, installation and formation <b>1800,</b> can comprise the stage of: <ul id="ul0014" list-style="none" compact="compact"><li>● providing a design system.</li></ul>
0166The main stage of designing the networks <b>1801</b> comprises the stages of: <ul id="ul0015" list-style="none" compact="compact"><li>● defining device type and physical location <b>1701;</b></li><li>● defining the binding links between devices <b>1702;</b></li><li>● defining the wired device mapping <b>1703,</b> the stage is described in <figref idref="f0007">Figure 9</figref>;</li><li>● defining the wireless device mapping <b>1704,</b> the stage is described in <figref idref="f0008">Figure 10</figref>; and</li><li>● defining an address translation sub-table for a wireless device <b>1705.</b></li></ul>
0167This stage is described in <figref idref="f0009">Figure 11</figref>.
0168The main stage of installation of the networks <b>1802</b> comprises the stages of: <ul id="ul0016" list-style="none" compact="compact"><li>● installing wireless devices <b>1706,</b> this stage is described in <figref idref="f0010">Figure 12</figref>;</li><li>● installing wired devices <b>1707,</b> this stage is described in <figref idref="f0011">Figure 13</figref>;</li></ul>
0169The main stage of forming the networks <b>1803</b> comprises the stages of: <ul id="ul0017" list-style="none" compact="compact"><li>● initializing wireless devices <b>1708,</b> this stage is described in <figref idref="f0012">Figure 14</figref>;</li><li>● initializing wired devices <b>1709,</b> this stage is described in <figref idref="f0013">Figure 15</figref>; and</li><li>● bindings formation <b>1710,</b> this stage is described in <figref idref="f0014">Figure 16</figref>.</li></ul>
0170While the invention has been described with respect to a limited number of embodiments, it will be appreciated that many variations, modifications and other applications of the invention may be made within the scope of the appended claims.
16 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| US2005165919A1 | Cites | United States of America |
| US2007232288A1 | Cites | United States of America |
| US7124101B1 | Cites | United States of America |
| US7184770B1 | Cites | United States of America |
| KNAUTH S ET AL: "SARBAU - an IP-fieldbus based building automation network", EMERGING TECHNOLOGIES AND FACTORY AUTOMATION, 2008. ETFA 2008. IEEE INTERNATIONAL CONFERENCE ON, IEEE, PISCATAWAY, NJ, USA, 15 September 2008 (2008-09-15), pages 13-16, XP031344578, ISBN: 978-1-4244-1505-2 | Non-patent | – |
9 members in 4 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 4794P | United States of America | – | |
| 479407 | United States of America | P | |
| 479407 | United States of America | P | |
| 2008001517 | Israel | W | |
| 2008001517 | Israel | W | |
| 4794P | – | – | – |
| IL2008001517 | – | – | – |
| US20070004794P | – | – | – |
| WO2008IL01517 | – | – | – |
Members9
| Document | Office | Kind | |
|---|---|---|---|
| WO2009069118A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2009069118A3 | World Intellectual Property Organization (WIPO) | A3 | |
| EP2215872A2 | European Patent Office (EPO) | A2 | |
| CN101919290A | China | A | |
| US2011007665A1 | United States of America | A1 | |
| EP2215872A4 | European Patent Office (EPO) | A4 | |
| EP2215872B1This record | European Patent Office (EPO) | B1 | |
| US8437276B2 | United States of America | B2 | |
| CN101919290B | China | B |
77 legal events, as 9 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Gb: european patent ceased through non-payment of renewal feeCeasedGBPC | GBPC | EP | |
| Application deemed withdrawn, or ip right lapsed, due to non-payment of renewal feeWithdrawnR119 | R119 | DE | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Amendment of ipc main classPREVIOUS MAIN CLASS: H04L0012240000R079 | R079 | DE | |
| Withdrawal/refusal of revocation action now finalR040 | R040 | DE | |
| Case pending at federal patent courtR008 | R008 | DE | |
| Revocation action filedR039 | R039 | DE | |
| Fee paymentPLFP | PLFP | FR | |
| Fee paymentPLFP | PLFP | FR | |
| Fee paymentPLFP | PLFP | FR | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| No opposition filed against granted patent, or epo opposition proceedings concluded without decisionGrantedR097 | R097 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent lapsedLapsedMM4A | MM4A | IE | |
| No opposition filedOpposition26N | 26N | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Invalidated european patentMG4D | MG4D | LT | |
| Discontinued in the netherlands as no translation has been filedVDEP | VDEP | NL | |
| Deletion acc. to par. 5 (withdrawal of the translation of the ep patent)MK05 | MK05 | AT | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| European patents granted designating irelandGrantedFG4D | FG4D | IE | |
| Reference to at number (ep patent validated in austria)REF | REF | AT | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Amendment of ipc main classPREVIOUS MAIN CLASS: H04W0040000000R079 | R079 | DE | |
| First examination report despatched17Q | 17Q | EP | |
| Supplementary search report drawn up and despatchedA4 | A4 | EP | |
| Request for extension of the european patent (deleted)DAX | DAX | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Request for extension of the european patentAX | AX | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 2215872
- Publication, DOCDB
- 2215872
- Publication, EPODOC
- EP2215872
- Application
- 8855279
- Application, DOCDB
- 08855279
- Application, EPODOC
- EP20080855279
Titles3
- German
- DESIGN- UND STEUERSYSTEME, KOMMISIONIERUNGSWERKZEUGE, KONFIGURATIONSADAPTER UND VERFAHREN FÜR DRAHTLOSEN UND VERDRAHTETEN NETZWERKEENTWURF, INSTALLATION UND AUTOMATISCHE BILDUNG
- English
- DESIGN AND CONTROL SYSTEMS, COMMISSIONING TOOLS, CONFIGURATION ADAPTERS AND METHOD FOR WIRELESS AND WIRED NETWORKS DESIGN, INSTALLATION AND AUTOMATIC FORMATION
- French
- SYSTÈMES DE CONCEPTION ET DE CONTRÔLE, OUTILS DE MISE EN SERVICE, ADAPTATEURS DE CONFIGURATION ET PROCÉDÉ POUR LA CONCEPTION L'INSTALLATION ET LA CONSTITUTION AUTOMATIQUE DE RÉSEAUX FILAIRES ET SANS FIL
Classification
- CPC, 6
- H04L41/145
- H04L41/0806
- H04L41/0846
- H04W16/18
- H05B47/175
- H05B47/199
- IPC, 2
- H04L12 24
- H04W16 18
Designated states1
- Contracting states, 1
- Türkiye
