IP Library Granted Patent US 9,912,446
Granted Patent B2
US 9,912,446 · App. 15/378,895 · Granted Mar 6, 2018

Device, method and computer readable medium for communication on a ZigBee network

Inventors: James Roger Hargrave (Wylie, TX); Kelvin Hui Xu (Plano, TX); David Alan Escamilla (Wylie, TX)
Assignee: AMX LLC
H04L1/08H04L1/12H04L12/66H04L47/625H04W4/008H04W28/06H04W28/10H04W76/02H04W84/18H04W88/16H04W92/02Y02B60/50
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,912,446
App. No.
15/378,895
Granted
Mar 6, 2018
Kind
B2
Abstract

In a zigbee network, reliable communications are provided by maintaining messages transmitted from a device in a message queue in the device. If no successful acknowledgement is received for a transmitted message, the message is re-transmitted when the message queue executes. Messages are deleted from the queue when the message is successfully transmitted or when a maximum number of re-tries has been exhausted.

Claims (32)

1. A method, comprising:

determining that a message that was transmitted from a first queue of a device has not been received;

re-transmitting the message and transmitting one or more subsequent messages associated therewith in a batch in a particular order from a re-try queue that is different from the first queue,

wherein each batch message is repeatedly transmitted until at least one of a maximum number of re-tries is reached and an acknowledgment message is received, and when the maximum number of re-tries is reached or the acknowledgment message is received, deleting the respective batch message from the re-try queue.

2. The method according to claim 1 wherein when the message was not successfully transmitted, determining when the message can be re-transmitted.

3. The method according to claim 2 further comprising determining whether the message can be re-transmitted by determining whether a maximum number of re-tries requirement has been met.

4. The method according to claim 1 wherein the step of re-transmitting the message further comprises incrementing a re-try counter.

5. The method according to claim 4 wherein the step of re-transmitting the message comprises executing the re-try queue.

6. The method according to claim 4 wherein the re-try queue is executed periodically.

7. The method according to claim 4 wherein each of a plurality of messages in the batch are transmitted from the re-try queue sequentially.

8. The method according to claim 1 further comprising re-transmitting the message and transmitting all subsequent messages in the batch until the batch of messages is successfully transmitted.

9. The method according to claim 1 further comprising determining whether the message was successfully transmitted.

10. The method according to claim 1 further comprising storing the message and the one or more subsequent messages in the batch with a message order requirement in the re-try queue.

11. The method according to claim 1 further comprising executing the re-try queue.

12. A device, comprising:

a transmitter;

a processor electrically connected to the transmitter; and

a memory electrically connected to the processor;

wherein the processor determines that a message that was transmitted from a first queue of the device has not been received;

wherein the transmitter re-transmits the message and one or more subsequent messages associated therewith in a batch in a particular order from a re-try queue that is different from the first queue,

wherein each batch message is repeatedly transmitted until at least one of a maximum number of re-tries is reached and an acknowledgment message is received, and the processor is configured to delete the respective batch message from the re-try queue when the processor determines that the maximum number of re-tries is reached or the acknowledgment message is received.

13. The device according to claim 12 wherein, when the message was not transmitted successfully, the processor determines when the message can be re-transmitted.

14. The device according to claim 13 further comprising a counter, wherein the processor determines whether the message can be re-transmitted using said counter.

15. The device according to claim 12 wherein the processor increments the counter when the message is re-transmitted.

16. The device according to claim 12 , wherein the transmitter re-transmits the message and all subsequent messages in the batch until the batch of messages is successfully transmitted.

17. The device according to 15 wherein the processor is configured to execute the re-try queue periodically.

18. The device according to claim 15 wherein the processor is configured to execute the re-try queue by causing messages in the re-try queue to be re-transmitted sequentially.

19. The device according to claim 12 , wherein the processor determines whether the message was transmitted successfully.

20. A non-transitory computer-readable storage device comprising computer-executable instructions for execution by at least one processor that, when executed, cause the at least one processor to perform:

determining that a message that was transmitted from a first queue of a device has not been received;

re-transmitting the message and transmitting one or more subsequent messages associated therewith in a batch in a particular order from a re-try queue that is different from the first queue,

wherein each batch message is repeatedly transmitted until at least one of a maximum number of re-tries is reached and an acknowledgment message is received, and when the maximum number of re-tries is reached or the acknowledgment message is received, deleting the respective batch message from the re-try queue.

Assignments (1)
MERGER AND CHANGE OF NAME Recorded Aug 6, 2019
From: AMX LLC; HARMAN PROFESSIONAL, INC.
To: HARMAN PROFESSIONAL, INC.
Reel/Frame 049976/0124 →
Continuity (5)
Continuation 14960406 · Dec 6, 2015
Continuation 14325952 · Jul 8, 2014
Continuation 12075742 · Mar 13, 2008
Provisional Application 60918392 · Mar 14, 2007
Related Publication 20170093531A1 · Mar 30, 2017