WO2011070479A1 - Wireless communication method based on proxy redundancy - Google Patents
Wireless communication method based on proxy redundancy Download PDFInfo
- Publication number
- WO2011070479A1 WO2011070479A1 PCT/IB2010/055501 IB2010055501W WO2011070479A1 WO 2011070479 A1 WO2011070479 A1 WO 2011070479A1 IB 2010055501 W IB2010055501 W IB 2010055501W WO 2011070479 A1 WO2011070479 A1 WO 2011070479A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- proxy
- packet
- group
- resource
- destination
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
- H04W40/04—Communication route or path selection, e.g. power-based or shortest path routing based on wireless node resources
- H04W40/10—Communication route or path selection, e.g. power-based or shortest path routing based on wireless node resources based on available power or energy
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/22—Alternate routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
- H04W88/182—Network node acting on behalf of an other network entity, e.g. proxy
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
Definitions
- the present invention relates to a method for communication in a wireless control network. More particularly, the present invention relates to a method for ensuring maintenance of correct communication between a communication device and a destination device in a wireless network.
- This invention is, for example, relevant for wireless networks comprising resource- restricted devices having low power resources.
- the present invention is relevant for wireless networks using communication protocols compliant with the IEEE802.15.4 and also IEEE802.15.4-based protocols, e.g. ZigBee protocol, especially the ZigBee Green Power protocol.
- Wireless control networks have recently become a ubiquitous trend in the field of communication and connectivity/automation, especially for building management systems.
- Wireless technologies present major advantages in terms of freedom of device placement, device portability, and installation cost reduction, since there is no need for drawing cables and drilling.
- sensor devices such as light switches, light dimmers, wireless remote controllers, movement or light detectors, window or door openers, that have to be set up in distant places one from the other and from the devices they control, e.g. lights.
- One of the drawbacks appearing in networks of the like relates to device powering. Indeed, since the devices are not wired, they can not receive power necessary for performing all the operations required in the network from the mains or via the connection with the controller. Thus, it has been envisaged to equip such devices with built-in batteries. However, since the devices are quite size-restricted, batteries may not be of a large size, which results either in a reduced device lifetime, or in labour intensive battery replacement.
- a first type of solution aims at ensuring that, at any given time, one and only one proxy is forwarding frames on behalf of the resource-restricted device to the destination.
- the existing procedures of the like involve, for guaranteeing proxy redundancy, a large amount of additional communication, a large amount of additional proxy code, and considerable delay when a device moves in the network.
- some prior master proxies may remain undiscovered, thus leading to many master conflicts.
- Yet another object of the invention is to provide a method allowing master proxy election.
- the invention relates to a method for wireless communication in a network comprising a resource-restricted device, at least two proxy devices and at least one destination device, wherein the method comprises the following steps:
- the resource-restriced device transmitting a frame to be forwarded to a destination device in the network, said frame containing a unique source identifier of the resource-restricted device,
- At least one proxy device receiving the frame and identifying the frame as originating from a resource-restricted device, - the proxy device determining the unique source identifier and deriving a group identifier as a known function of the unique source identifier, the group identifier designating a group of devices in the network,
- the proxy if the proxy was not yet a member of the group identified by the derived group identifier: the proxy becoming a member of the group with the derived group identifier;
- the proxy constructing, from the frame, an appropriate packet to be forwarded, the proxy forwarding the packet by taking into account the group identifier.
- a resource-restricted device relates to a communicating device that is restricted at least in terms of energy-resource, acting as a reduced functionality device in the network.
- This formulation includes, but is not limited to, battery-powered devices with limited energy storage and energy-harvesting devices.
- a resource-restricted device is, for example, a light switch, a light sensor, a presence detector, or any device of the like used in control networks requiring high link reliability, such as lighting control networks, building or home automation network.
- the energy harvesting may be performed using electro -mechanical element, e.g. operated by the user; solar cells, or harvesting vibration, thermal, flow or other types of energy.
- a proxy device also called a router in the present specification, is a device having proxy capabilities, corresponding to capacities of routing messages received from an originating device to a destination device. Furthermore, proxy device has the capabilities of receiving the frames sent by the resource-restricted device and acting upon them.
- a destination device within the meaning of the present invention is a device for which a frame is intended in the network.
- a device can be a resource-restricted device, a proxy device, or any other type of device, with or without proxy capabilities.
- a method according to the invention allows all proxies to independently derive the same multicast identifier from the unique source identifier of the resource-restricted device, using a known function.
- the group identified by the identifier is a proxy maintenance group.
- the proxy maintenance group identifier (PGroupID) is used for proxy maintenance communication, thus allowing for reaching all interested parties and providing the keepalive feature between the proxies for free.
- the group comprises proxy devices involved in forwarding the frames on behalf of a resource-restricted device and the packet constructed from the frame is a notification packet for the master proxy device.
- the proxy receiving the frame is not a member of the group identified by the group identifier
- the proxy becomes a member of the group and starts a master proxy resolution procedure for determining a master proxy.
- Such a procedure is performed by sending a master request message to the group identified by the group identifier.
- the determined master proxy receives information on the destination devices, derives a packet from the frame sent by the resource-restricted device, determines a destination addressing mode, and forwards the packet by using the determined destination addressing mode.
- the destination addressing mode is, for example, unicast or multicast.
- the information regarding the destination devices is received by the elected master proxy via a configuration procedure, or from an older master proxy.
- the group designated by the identifier is a control group, comprising target devices, i.e. destination devices for which the frame sent by the resource- restricted device is intended.
- the Control group identifier (CGroupID) is used for multicast- based application control, allowing the proxies not to care about holding, maintaining and exchanging binding information, i.e. information about the destination devices, thus guaranteeing that resource-restricted device can immediately be operated at any location, without any delay, and thus supporting portability and mobility of resource-restricted device.
- the step of constructing the packet to be forwarded further comprises using a sequence number supplied by the resource-restricted device.
- the packet constructed from the frame is a data or command packet for the destination device(s), and is forwarded to the identified group.
- the resource- restricted device has a unique source identifier (SrcID), and the proxies are provided with predetermined functions fl and f2.
- the proxies have the capability, when located in the range of a resource-restricted device, to recognize frames as being sent by the resource-restricted device. For example, this recognition can be performed thanks to a special frame format used by the resource-restricted device, and identified by the proxy devices.
- the method comprises the step for the proxy device of scheduling the packet forwarding after a predetermined delay, wherein the delay is determined based on one or several of the following criteria: a link quality indicator of the reception of the resource-restricted device's frame, a reception success rate of the resource-restricted device's frame, a memory availability, the fact of being early to forward in the past, the knowledge of the destination device(s), the knowledge of the route to the destination device(s), and the path cost to the destination(s).
- the method comprises the step for the proxy device of listening, during the countdown, if a message corresponding to the same frame is being transmitted by other devices of the network, and if so, of forwarding this message and cancelling its own scheduled transmission or re-transmission.
- Another aspect of the invention relates to a method for wireless communication in a network comprising a resource-restricted device, at least two proxy devices, and at least one destination device, wherein the method comprises the following steps:
- the resource-restricted device transmitting a frame to be forwarded to a destination device in the network, said frame containing a unique source identifier of the resource-restricted device,
- At least one proxy device receiving the frame and identifying the frame as originating from a resource-restricted device
- the proxy device determining the unique source identifier and deriving a group identifier as a known function of the unique source identifier, the group identifier designating a source address to be used by a group of proxy devices in the network, the proxy constructing, from the frame, an appropriate packet to be forwarded to the destination device(s), using the derived group identifier as a group source address and using a sequence number supplied by the resource-restricted device,
- the proxy scheduling forwarding the frame to destination device(s) after a predetermined delay, wherein the delay is determined based on one or several criteria comprised in the group comprising a link quality indicator of the resource-restricted device's frame, a reception success rate of the resource-restricted device's frame, a memory availability, the knowledge of the destination device(s), the knowledge of the route to the destination device(s). the fact of being early to forward in the past,
- the proxy device listening, during the countdown of the delay, if a message corresponding to the same frame is being forwarded by other devices of the network, and if so, of forwarding this message and cancelling its own scheduled transmission.
- this method comprises the step of the destination device receiving the packet and sending an acknowledgement frame to the group identifier contained in the source address field of the received packet, using non-member multicast mode.
- this method comprises the step of a first proxy device being member of the source proxy group, receiving an acknowledgement in non-member mode, forwarding it in member-mode to the source proxy group, and second proxy device receiving the acknowledgement in the member-mode multicast and dropping the scheduled transmission or forwarding of the packet corresponding to this acknowledgement.
- the present invention relates to a method for wireless communication in a network comprising a resource-restricted device, at least two proxy devices and at least one destination device.
- the resource-restricted device is, for example, an energy-harvesting device, or a ZigBee Green Power device (ZGPD), using a dedicated frame format for sending frames (ZGP frame).
- the proxy devices (ZP1, ZP2, ZP3, ZP4 and ZP5) are, for example, devices having the capability of understanding such dedicated frame format, and of generating frames compliant with the ZigBee standard (ZB frames) from a ZGP frame.
- the destination device (DD) is controlled by the resource-restricted device, and has the capability to support the ZB format.
- a destination device might be a device fully compliant with the ZigBee specification.
- a destination device has, in addition, proxy capability, i.e. it can receive ZGP frames and/or ZGP proxy messages.
- the resource-restricted device has a unique identifier, which is, for example, distinct from an IEEE address and from a ZigBee network address.
- the size of the identifier is preferably comprised between 1 and 4 bytes.
- the resource-restricted frame i.e. the frame sent by the resource-restricted device contains a sequence number in the MAC header. In an example, this sequence number is not incremental, which means that there is no need for the resource-restricted device to reserve energy to store it in a non- volatile way.
- the packet derived from the resource-restricted frame contains a sequence number, either in the network or application layer, allowing the receiving device to check message freshness and/or to filter duplicate messages.
- proxies still keep forwarding the resource-restricted frame to the master proxy, although the master proxy already received and forwarded the resource-restricted frame. This adds to unnecessary medium occupation. It can also happen that several proxies forward the resource-restricted packet to the destination at approximately the same time, i.e. before the other simultaneously forwarding proxies can notice.
- the selected proxy master uses the CGroupID to forward the data to the destinations using the CGroupID, and all redundancy proxies drop scheduled resource-restricted packet transmission, as soon as they see the master forwarding the resource-restricted packet as a ZigBee packet to the destination(s), and drop the scheduled master notification as soon as they see some other proxy forwarding the resource-restricted packet to the master or as soon as they see the master forwarding the resource-restricted packet as a ZigBee packet to the destination.
- fl f2
- PGroupID CGroupID. It may be beneficial, to keep them separate, as it may allow for different handling already on NWK layer.
- This first procedure comprises, in an exemplary embodiment, the following steps:
- the resource-restricted device is triggered by external means, such as a user interaction or a sensor, or by internal means such as an internal timer.
- the device thus sends a ZGPD frame, containing data or command.
- This frame is sent with the MAC layer using a generic Personal Area Network Identifier (PANId), such as broadcast PANId or a special PANId dedicated for ZGP communication, and MAC broadcast Destination Address.
- PANId Personal Area Network Identifier
- the MAC layer header contains a random number within the sequence number field.
- the frame further contains unique a 4 bytes source identifier of the resource-restricted device and a sequence number.
- Step 2 All devices with proxy capabilities situated in the network in the radio range of the resource-restricted device identify the frame as being sent by a resource-restricted device and each of them checks whether the resource-restricted device is already known to it. This checking is performed by first deriving a proxy maintenance group identifier by applying a known function to the source identifier, and then by searching for the group identifier in a table, either the nwkGroupIDTable or the apsGroupTable.
- each proxy that does not find the group ID dervied from the source identifier of the resource-restricted device in an appropriate table adds itself to the group by including the PGroupID in the table.
- Inclusion into nwkGroupIDTable enables usage of NWK layer member-mode multicast; inclusion into apsGroupTable enables usage of application layer multicast a.k.a. groupcast.
- each proxy device which just became member of this PGroupID i.e. which does not yet have the information about the master proxy for this particular resource-restricted device, starts a master election procedure, by sending a Master_request packet comprising at least the source identifier of the resource-restricted device, to the PGroupID.
- Step 5 the newly elected master chooses a network-wide unique control GroupID, CGroupID to be controlled by ZigBee cluster derived from the ZGPD, and waits for commissioning to be performed locally on the master proxy or else for the binding information to be distributed in the PGroupID/network-wide broadcast
- Step 6 in the case where the resource-restricted device was known, it means that the master proxy having to forward the packet is known as well; thus, each proxy except the master proxy constructs a Master notification packet to notify the master proxy of the ZGPD frame, the packet comprising as payload the relevant contents of the ZGPD frame (such as source identifier of the resource-restricted device, sequence number from the ZGPD frame, the application layer payload from the ZGOD frame), the packet being addressed to this PGroupID, and the packet being sent using the individual source address and sequence number of the forwarding proxy device, to allow the master proxy to treat each notification sent as separate packet.
- the relevant contents of the ZGPD frame such as source identifier of the resource-restricted device, sequence number from the ZGPD frame, the application layer payload from the ZGOD frame
- Each proxy schedules the Master notification packet forwarding, with a delay as a function of one or several parameters among: a link quality indicator for reception of the ZGPD frame, the success rate of the reception of the ZGPD frames, and the fact of being early to forward in the past.
- Step 7 During the timeout, i.e. the time before forwarding the packet, the proxy listens to incoming frames: if the proxy receives a Master notification packet in member mode on PGroup ID, it forwards it according to member mode multicast rules to the PGroupID, and and drops the scheduled transmissions of Master_notification,as well as any packet to any binding destination resulting from the same SrcID and sequence number.
- Step 8 After the timeout, the proxy sends the packet constructed as described above to the PGroupID and starts a timer. If no Master Notification response is received until timeout, master re-election has to be started.
- Step 9 The master proxy receives the ZGPD frame or the Master notification packet and constructs ZigBee frame to be sent to the controlled destination device(s).
- the frame is built by using the control group identifier as non-member mode multicast or groupcast destination, the own source address of the master proxy, and the own sequence number of the master proxy, and it contains the command or data derived from the application layer payload of the ZGPD frame.
- Step 10 The master proxy forwards the packet to the CGroupID and constructs a Master Notification response packet, to be sent to the PGroupID with the source address of the master, and ignores subsequent notifications related to the same ZGPD packet and ZGPD packet repetitions (to be identified by the ZGPD SrcID and ZGPD sequence number).
- Step 11 The destination receives the ZGPD frame via the master only, so no duplicate detection should be required.
- Step 1 the resource-restricted device is triggered by external means, such as a user interaction or a sensor, or by internal means such as an internal timer.
- the device thus sends a ZGPD frame, containing data or command.
- This frame is sent with the MAC layer using a generic Personal Area Network Identifier (PANId), such as broadcast PANId or a special PANId dedicated for ZGP communication, and MAC broadcast Destination Address.
- PANId Personal Area Network Identifier
- the MAC layer header contains a random number within the sequence number field.
- the frame further contains unique 4 bytes source identifier of the resource-restricted device and a sequence number.
- Step 2 All devices with proxy capabilities situated in the network in the radio range of the resource-restricted device identify the frame as being sent by a resource-restricted device and each of them checks whether the resource-restricted device is already known to it. This checking is performed by first deriving a proxy maintenance group identifier by applying a known function to the source identifier, and then by searching for the group identifier in a table, either the nwkGroupIDTable or the apsGroupTable.
- each proxy that can not find the groupID derived from the source identifer of the resource-restricted device in an appropriate table, each proxy adds itself to the group by including the PGroupID in a table.
- Inclusion into nwkGroupIDTable enables usage of NWK layer member-mode multicast; inclusion into apsGroupTable enables usage of application layer multicast a.k.a. groupcast.
- Step 4 each proxy which just became member of this PGroupID, i.e. which does not yet have the information about the destination(s), waits for commissioning to be performed locally on the proxy or else for the binding information to be distributed in the PGroupID (or alternatively via network-wide broadcast) by the proxy with which the binding was performed.
- each proxy knowing the destination(s) for the resource-restricted device constructs a ZigBee packet to be forwarded to the controlled device(s).
- the packet is constructed by using the bound device(s) as a unicast destination, network and/or application layer sequence numbers derived from the number supplied by the resource- restricted device in the ZGPD frame, and the alias source address derived from the source identifier of the resource-restricted device, and contains as payload the data or command derived from the application layer payload of the ZGPD frame.
- each proxy schedules packet forwarding, with a delay as a function of the reception link quality indicator from the ZGPD, knowledge of the route to the destination(s), total path cost to each of the destination(s), and fact of being early to forward in the past.
- the proxy listens to incoming frames :if the proxy receives an acknowledgment message (either APS ACK or APPL response message) in unicast from the destination, it creates a ZGPD confirmation packet containing SrcID and sequence number corresponding to the received acknowledgment, as well as the short address of the destination which has sent the acknowledgment.
- an acknowledgment message either APS ACK or APPL response message
- the proxy forwards it to other proxies in the PGroupID using member mode multicast and using PGroupID as destination address and alias as source address, stops the timer and drops all scheduled transmissions for any packet to any binding destination resulting from the same ZGPD packet (the same ZGPD packet means a packet containing the same source identifier and the same sequence number).
- Step 6bis If the proxy receives the ZGPD confirmation packet in member mode multicast to PGroupID, the proxy forwards it according to member mode multicast rules to the PGroupID, stops the timer and drops all scheduled transmissions for any packet to any binding destination resulting from the same ZGPD packet.
- Step 6ter if the proxy receives the same ZigBee packet (i.e. derived from the same ZGPD frame and using the same destination and source aliasing information), which is unlikely, because it requires special receiving methods, such as promiscuous mode, the proxy stops the timer and drops all scheduled transmissions for any packet to any binding destination resulting from the same ZGPD packet.
- the proxy stops the timer and drops all scheduled transmissions for any packet to any binding destination resulting from the same ZGPD packet.
- Step 7 After the timeout, the proxy sends the packet constructed as described above to the bound destination(s) and schedules retransmissions after the acknowledgment timeout.
- Step 8 One or several destination device(s) receive the ZigBee packet. If the alias source address is new, the destination devices discover the reoute to the alias. Otherwise, and following the route discovery, the destination devices construct an acknowledgment packet and unicast it to the alias.
- Step 9 During the acknowledgment timeout, if the proxy receives an acknowledgment packet in unicast from a destination device, then the proxy creates a ZGPD confirmation packet containing the source identifier and a sequence number corresponding to the received acknowledgment, as well as the short address of the destination that forwarded the APS ACK; then it forwards it to other destinations in the PGroupID, using multicast member mode and using PGroupID as destination address and alias as source address; and drops the scheduled re-transmissions of this packet, resulting from the same ZGPD frame to this binding destination
- Step 9bis If the proxy receives the a ZGPD confirmation packet in member mode on PGroupID, the proxy forwards it according to member mode multicast rules to the PGroupID and drops the scheduled re-transmissions for this packet to this binding destination resulting from the same SrcID and sequence number.
- Step 10 If any proxy keeps seeing ZGPD packets, but does not receive acknowledgements from the destination(s), neither direct APS ACKs or APPL response commands, or indirectly via confirmation packets forwarded to the PGroupID, it should re-discover the route to the destination, so that the reverse route is also re-established - or the destination is discovered to be non-existent.
- a third procedure will now be described, wherein the destination devices are assumed to have proxy capabilities.
- the ZGPD frame, or a special notification frame derived from it can be forwarded all the way to the destinations.
- This allows the destination(s) to perform level duplicate filtering at proxy-endpoint level, without the need for the forwarding proxies to use special aliasing procedures, special multicast source address modes, or without the need for the complicated and bandwidth-consuming master proxy election procedure.
- the mentioned means may still be used, if minimizing the traffic to the destination(s) is desirable.
- binding information handling can still be simplified on the proxies. Broadcast communication can be used, because the proxy-capable destination is able to filter on the endpoint level, based on the packet content.
- non-unique CGroupIDs e.g. resulting from deriving a 2-bytes GroupID from a 4-bytes SrcID, can be used, because the destinations will be able to filter the packets, based on their content.
- an exemplary procedure according to this third method can contain the following steps:
- the proxies When receiving a packet from a previously unknown resource-restricted device, the proxies derive the CGroupID from the resource-restricted device's SrcID, and add themselves as group members. Each proxy constructs a notification packet, being ZigBee packet and containing the relevant fields of the ZGPD frame as a payload. When forwarding a packet to the destination on behalf of this resource-restricted device, the proxies use the derived CGroupID as NWK layer or APS layer destination address and use their individual source address and source sequence number.
- the proxy endpoint unicasts a notification response message back to the proxy having forwarded the notification.
- the proxy can then distribute the notification response among other proxies, by sending to PGroupID, so that other proxies can drop all scheduled transmissions and retransmissions of the resource-restricted packet with the corresponding sequence number.
- a fourth procedure will now be described, where source multicast group is used.
- source multicast group is used.
- it is required to receive an acknowledgment to the message derived from the ZGPD frame.
- sending acknowledgment messages is not trivial, especially when multiple proxies forward independently to the destination(s).
- address aliasing is used for source address determination by the proxies, the proxies are required to implement special procedures to respond to communication addressed both to their individual short address and to the alias.
- many proxy devices may act on behalf of the same resource-restricted device, thus leading to multiple potential destinations for the APS ACK, resulting in
- One possibility to accommodate that in ZigBee is to include the SGroupID in the Source Address field of the network layer header, indicate that it is a group address by using one of the now reserved values in the Multicast Mode sub-field of the Multicast Control Field of the network layer header of a data frame (all frame/field formats below as defined by ZigBee specification release rl7), no allow for network-layer multicast source addressing.
- Another possibility is to accommodate that in the APS layer, using the APS header Group Address field in combination with the reserved value of the Delivery Mode subfield of the Frame Control field of the APS header, so that the destination can respond with APS level multicast, rather than NWK level multicast.
- exemplary procedure according to this third method contains the following steps.
- the proxies When receiving a packet from a previously unknown resource-restricted device, the proxies add themselves as group members for the SGroupID derived from the resource- restricted device's SrcID; then, when forwarding a packet to the destination on behalf of this resource-restricted device, the proxies use this SGroupID as NWK layer source address and a source sequence number derived from the sequence number included in the resource- restricted frame, and further using CGrouplD as the destination address on either network or APS level.
- the proxies here are not members of the group CGrouplD themselves.
- the CGrouplD is preferably derived from the source identifier of the resource-restricted device, as described before, or can be configured and distributed among the proxies.
- the destination Upon receipt of such a packet with group source address, in non-member mode multicast, the destination forwards it to other destinations in the CGrouplD, changing multicast mode to member mode and using CGrouplD as destination address and SGroupID as source address and sends an acknowledgement to that SGroupID using non-member-mode multicast, with the CGrouplD in the source address field.
- the destination Upon receipt of such a packet with group source address, in member mode multicast, the destination forwards it according to member mode multicast rules.
- the proxy Upon receipt of the multicast-targeted acknowledgement packet, in non-member mode multicast, the proxy forwards it to other destinations in the SGroupID, changing multicast mode to member mode and using SGroupID as destination address and CGrouplD as source address.
- the proxy Upon receipt of the multicast-targeted acknowledgement packet, in member mode, the proxy forwards it according to member-mode multicast rules and drop all scheduled transmissions and re-transmissions of the resource-restricted packet with the corresponding sequence number.
- the proxies in the group SGroupID keep seeing and forwarding the ZGPD packets, but do not receive the acknowledgement from the destination anymore, neither directly or via the SGroupID-addressed multicast. This can indicate, that either the destination disappeared from the network (or moved), or that the reverse path to the SGroupID is broken, or that the previous entry point into the group SGroupID, i.e. the proxy with the best reverse cost to the destination disappeared. Then, the remaining proxies should force the destination to re-discover the reverse path to the group.
- a method according to the invention can be implemented into different procedures, some of them being above-described for illustrating purpose.
- the present invention is more especially dedicated to be used in any wireless network using resource-restricted devices, such as lighting control networks, building automation and home automation networks.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/512,425 US9036531B2 (en) | 2009-12-09 | 2010-11-30 | Wireless communication method based on proxy redundancy |
JP2012542654A JP5628340B2 (en) | 2009-12-09 | 2010-11-30 | Wireless communication method based on proxy redundancy |
BR112012013695A BR112012013695A8 (en) | 2009-12-09 | 2010-11-30 | METHOD FOR WIRELESS COMMUNICATION IN A NETWORK AND PROXY DEVICE CONFIGURED FOR WIRELESS COMMUNICATION IN A NETWORK |
CN201080055858.8A CN102652445B (en) | 2009-12-09 | 2010-11-30 | Based on the wireless communications method of Agent redundancy |
EP10805502.1A EP2510722B1 (en) | 2009-12-09 | 2010-11-30 | Wireless communication method based on proxy redundancy |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP09306201.6 | 2009-12-09 | ||
EP09306201 | 2009-12-09 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011070479A1 true WO2011070479A1 (en) | 2011-06-16 |
Family
ID=43770487
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/IB2010/055501 WO2011070479A1 (en) | 2009-12-09 | 2010-11-30 | Wireless communication method based on proxy redundancy |
Country Status (6)
Country | Link |
---|---|
US (1) | US9036531B2 (en) |
EP (2) | EP2750448B1 (en) |
JP (1) | JP5628340B2 (en) |
CN (1) | CN102652445B (en) |
BR (1) | BR112012013695A8 (en) |
WO (1) | WO2011070479A1 (en) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2014511627A (en) * | 2011-02-28 | 2014-05-15 | コーニンクレッカ フィリップス エヌ ヴェ | Method for operating and commissioning a device in a ZigBee network |
JP2014524205A (en) * | 2011-07-11 | 2014-09-18 | コーニンクレッカ フィリップス エヌ ヴェ | How to configure a node |
CN104106288A (en) * | 2012-02-16 | 2014-10-15 | 皇家飞利浦有限公司 | Method for managing proxy table in wireless network using proxy devices |
CN104115526A (en) * | 2012-02-16 | 2014-10-22 | 皇家飞利浦有限公司 | Efficient proxy table management in communication networks |
JP2014534779A (en) * | 2011-11-03 | 2014-12-18 | クアルコム,インコーポレイテッド | Multiple delivery route packet ordering |
US9059932B2 (en) | 2011-11-03 | 2015-06-16 | Qualcomm Incorporated | Packet ordering based on delivery route changes in communication networks |
EP3131271A1 (en) * | 2015-08-12 | 2017-02-15 | Philips Lighting Holding B.V. | Green power for dense large networks (proxy table scaling) |
EP3327987A1 (en) * | 2016-11-23 | 2018-05-30 | ABB Schweiz AG | Device, system and method for sending messages in a wireless building automation network |
CN108684030A (en) * | 2018-08-30 | 2018-10-19 | 新华三技术有限公司 | A kind of method and device of detection network identity conflict |
Families Citing this family (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8391194B2 (en) * | 2009-02-13 | 2013-03-05 | Qualcomm Incorporated | High rate packet data (HRPS) idle state handout from femto access point to macro access network |
KR101725889B1 (en) * | 2010-12-28 | 2017-04-12 | 삼성전자주식회사 | Method and apparatus using heterogeneous protocols |
US9118732B2 (en) * | 2011-05-05 | 2015-08-25 | At&T Intellectual Property I, L.P. | Control plane for sensor communication |
US9753797B1 (en) * | 2011-08-26 | 2017-09-05 | Amazon Technologies, Inc. | Reliable intermediate multicast communications |
WO2014109797A1 (en) * | 2013-01-14 | 2014-07-17 | Intel IP Corporation | Energy-harvesting devices in wireless networks |
US10652347B2 (en) | 2013-05-20 | 2020-05-12 | Nokia Corporation | Access to data source via proxy |
US10642968B2 (en) | 2014-09-24 | 2020-05-05 | Nokia Technologies Oy | Controlling a device |
US9801050B2 (en) * | 2015-09-30 | 2017-10-24 | Verizon Patent And Licensing Inc. | Formatting an endpoint as a private entity |
US10505839B2 (en) | 2015-10-13 | 2019-12-10 | Signify Holding B.V. | Unicast message routing using repeating nodes |
JP6958542B2 (en) * | 2016-03-23 | 2021-11-02 | 日本電気株式会社 | Information processing equipment, information processing methods, information processing programs and information processing systems |
CN107509219B (en) * | 2017-08-28 | 2020-12-01 | 四川长虹电器股份有限公司 | ZigBee data encapsulation analysis method based on reported data characteristics |
WO2020035148A1 (en) * | 2018-08-17 | 2020-02-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Control system |
CN114175750A (en) * | 2019-05-24 | 2022-03-11 | 马维尔亚洲私人有限公司 | Power saving and group addressing frames in a WLAN using several communication links |
US20220038372A1 (en) * | 2020-08-02 | 2022-02-03 | Mellanox Technologies Tlv Ltd. | Stateful filtering systems and methods |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2004109974A1 (en) | 2003-06-11 | 2004-12-16 | Koninklijke Philips Electronics N.V. | Configuring a radio network for selective broadcast |
US20050180447A1 (en) * | 2004-02-12 | 2005-08-18 | Samsung Electronics Co., Ltd. | Multicast method in zigbee network |
WO2008027615A1 (en) * | 2006-08-31 | 2008-03-06 | Sony Ericsson Mobile Communications Ab | Zigbee/ip gateway |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6407991B1 (en) * | 1993-05-06 | 2002-06-18 | Intermec Ip Corp. | Communication network providing wireless and hard-wired dynamic routing |
US7295525B2 (en) * | 2003-09-11 | 2007-11-13 | Sun Microsystems, Inc. | System and method for managing multicast group membership |
JP3963391B2 (en) * | 2004-02-12 | 2007-08-22 | 三星電子株式会社 | Multicast method in ZigBee network |
US7848223B2 (en) * | 2005-06-03 | 2010-12-07 | Honeywell International Inc. | Redundantly connected wireless sensor networking methods |
WO2007021269A1 (en) * | 2005-08-15 | 2007-02-22 | Mitsubishi Electric Research Laboratories | Method, apparatus and system for multicast communication in a wireless multi-hop network |
CN101287324B (en) | 2006-12-21 | 2012-10-03 | 秦毅 | Distant measurement, communication, control method supporting illumination of ZigBee road lamp and electronic ballast |
US20080205385A1 (en) * | 2007-02-26 | 2008-08-28 | Motorola, Inc. | Data frame formats to improve groupcast efficiency in multi-hop wireless networks |
US8344665B2 (en) * | 2008-03-27 | 2013-01-01 | Orion Energy Systems, Inc. | System and method for controlling lighting |
US20080316951A1 (en) * | 2007-06-20 | 2008-12-25 | Motorola, Inc. | Method for discovering a route to an intelligent access point (iap) |
CN101282605B (en) * | 2008-03-21 | 2011-12-07 | 浙江大学城市学院 | Energy-saving type interior illumination wireless intelligent control system and control method based on ZigBee sensing network |
CN101370334A (en) * | 2008-10-08 | 2009-02-18 | 天津理工大学 | Road lamp energy-saving remote management system based on Zigbee and GPRS |
US10772028B2 (en) * | 2009-02-13 | 2020-09-08 | Signify Holding B.V. | Method for communicating in a network comprising a batteryless ZigBee device, network and device therefor |
-
2010
- 2010-11-30 CN CN201080055858.8A patent/CN102652445B/en active Active
- 2010-11-30 EP EP14161331.5A patent/EP2750448B1/en active Active
- 2010-11-30 EP EP10805502.1A patent/EP2510722B1/en active Active
- 2010-11-30 WO PCT/IB2010/055501 patent/WO2011070479A1/en active Application Filing
- 2010-11-30 BR BR112012013695A patent/BR112012013695A8/en active Search and Examination
- 2010-11-30 US US13/512,425 patent/US9036531B2/en active Active
- 2010-11-30 JP JP2012542654A patent/JP5628340B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2004109974A1 (en) | 2003-06-11 | 2004-12-16 | Koninklijke Philips Electronics N.V. | Configuring a radio network for selective broadcast |
US20050180447A1 (en) * | 2004-02-12 | 2005-08-18 | Samsung Electronics Co., Ltd. | Multicast method in zigbee network |
WO2008027615A1 (en) * | 2006-08-31 | 2008-03-06 | Sony Ericsson Mobile Communications Ab | Zigbee/ip gateway |
Non-Patent Citations (1)
Title |
---|
HYOUNG SEOK LIM ET AL: "Efficient Data Gathering Mechanism for Mobile Sink node in ZigBee Network", INFORMATION NETWORKING, 2008. ICOIN 2008. INTERNATIONAL CONFERENCE ON, IEEE, PISCATAWAY, NJ, USA, 23 January 2008 (2008-01-23), pages 1 - 5, XP031238821, ISBN: 978-89-960761-1-7 * |
Cited By (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2014511627A (en) * | 2011-02-28 | 2014-05-15 | コーニンクレッカ フィリップス エヌ ヴェ | Method for operating and commissioning a device in a ZigBee network |
JP2014524205A (en) * | 2011-07-11 | 2014-09-18 | コーニンクレッカ フィリップス エヌ ヴェ | How to configure a node |
US9948504B2 (en) | 2011-07-11 | 2018-04-17 | Philips Lighting Holding B.V. | Method for configuring a node |
US9059932B2 (en) | 2011-11-03 | 2015-06-16 | Qualcomm Incorporated | Packet ordering based on delivery route changes in communication networks |
JP2014534779A (en) * | 2011-11-03 | 2014-12-18 | クアルコム,インコーポレイテッド | Multiple delivery route packet ordering |
CN104115526B (en) * | 2012-02-16 | 2019-07-16 | 飞利浦灯具控股公司 | Efficient proxy table management in communication network |
US9992727B2 (en) | 2012-02-16 | 2018-06-05 | Philips Lighting Holding B.V. | Method for managing a proxy table in a wireless network using proxy devices |
US10405258B2 (en) | 2012-02-16 | 2019-09-03 | Signify Holding B.V. | Method for managing a proxy table in a wireless network using proxy devices |
CN104106288A (en) * | 2012-02-16 | 2014-10-15 | 皇家飞利浦有限公司 | Method for managing proxy table in wireless network using proxy devices |
CN104115526A (en) * | 2012-02-16 | 2014-10-22 | 皇家飞利浦有限公司 | Efficient proxy table management in communication networks |
CN104106288B (en) * | 2012-02-16 | 2018-12-25 | 飞利浦灯具控股公司 | Method for using the proxy table in agent equipment management wireless network |
JP2015510360A (en) * | 2012-02-16 | 2015-04-02 | コーニンクレッカ フィリップス エヌ ヴェ | Efficient proxy table management in communication networks |
EP3131271B1 (en) | 2015-08-12 | 2018-05-02 | Philips Lighting Holding B.V. | Green power for dense large networks (proxy table scaling) |
WO2017025415A1 (en) * | 2015-08-12 | 2017-02-16 | Philips Lighting Holding B.V. | Green power for dense large networks (proxy table scaling) |
US10366245B2 (en) | 2015-08-12 | 2019-07-30 | Signify Holding B.V. | Green power for dense large networks (proxy table scaling) |
EP3131271A1 (en) * | 2015-08-12 | 2017-02-15 | Philips Lighting Holding B.V. | Green power for dense large networks (proxy table scaling) |
RU2717909C2 (en) * | 2015-08-12 | 2020-03-26 | Филипс Лайтинг Холдинг Б.В. | Environmentally friendly energy source for dense large networks (proxy table scaling) |
EP3327987A1 (en) * | 2016-11-23 | 2018-05-30 | ABB Schweiz AG | Device, system and method for sending messages in a wireless building automation network |
CN108684030A (en) * | 2018-08-30 | 2018-10-19 | 新华三技术有限公司 | A kind of method and device of detection network identity conflict |
CN108684030B (en) * | 2018-08-30 | 2020-12-11 | 新华三技术有限公司 | Method and device for detecting network identification conflict |
Also Published As
Publication number | Publication date |
---|---|
US20120236778A1 (en) | 2012-09-20 |
BR112012013695A2 (en) | 2017-10-10 |
CN102652445A (en) | 2012-08-29 |
EP2510722A1 (en) | 2012-10-17 |
US9036531B2 (en) | 2015-05-19 |
EP2750448B1 (en) | 2018-07-04 |
JP5628340B2 (en) | 2014-11-19 |
BR112012013695A8 (en) | 2017-12-05 |
EP2750448A1 (en) | 2014-07-02 |
CN102652445B (en) | 2016-02-03 |
JP2013513989A (en) | 2013-04-22 |
EP2510722B1 (en) | 2014-03-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2510722B1 (en) | Wireless communication method based on proxy redundancy | |
US8937935B2 (en) | Method for communicating in a network comprising a batteryless zigbee device, network and device therefor | |
EP2396952B1 (en) | Method for communicating in a network comprising a batteryless zigbee device, network and device therefor | |
US8908513B2 (en) | Method for communicating in a network comprising a batteryless zigbee device, network and device therefor | |
EP2622775B1 (en) | Device and method for scheduling data packet transmissions in wireless networks | |
EP2289266B1 (en) | A network interface unit for a node in a wireless multi-hop network, and a method of establishing a network path between nodes in a wireless multi-hop network. | |
US10505839B2 (en) | Unicast message routing using repeating nodes | |
CN117082482B (en) | Method for realizing multi-MESH network networking and node roaming | |
WO2013122228A1 (en) | Control device and communication control method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201080055858.8 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10805502 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010805502 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 4397/CHENP/2012 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13512425 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2012542654 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112012013695 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112012013695 Country of ref document: BR Kind code of ref document: A2 Effective date: 20120606 |