Zigbee Router ACK Handling for Fragmented Sleepy End-Device Traffic

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The Zigbee protocol experiences significant communication overhead and power consumption due to redundant data exchanges and unnecessary re-transmissions in fragmented data transmissions, particularly affecting battery-powered 'sleepy' end devices (ZEDs) in personal area networks (PANs).

Innovation Solution

A Zigbee router device is configured to manage and optimize data transmission by decrypting network layer payloads, identifying fragmentation, and sending acknowledgement messages (APS ACKs) on behalf of the end device, reducing redundant communications and re-transmissions by maximizing the fragmentation window.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If fragmentation window is set to 1 for reliable data transmission, then data delivery reliability is improved, but communication overhead and power consumption increase due to frequent acknowledgements and re-transmissions

Engineering Contradiction:
Improvedata delivery reliabilityVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent dynamically adjusts the fragmentation window size based on network conditions and device states. Instead of using a fixed window size of 1, the system can adaptively increase the window size when conditions permit, reducing the frequency of acknowledgements and re-transmissions while maintaining reliability when needed.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The invention changes the parameter of fragmentation window size from a fixed value (1) to a variable parameter that can be adjusted based on network conditions, device capabilities, and transmission requirements. This allows optimization of both reliability and power consumption by selecting appropriate window sizes for different scenarios.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If fragmentation window is set to 1 for reliable data transmission, then data delivery reliability is improved, but communication overhead increases due to redundant data exchanges

Engineering Contradiction:
Improvedata delivery reliabilityVSAvoidcommunication overhead
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system dynamically adjusts the fragmentation window size to reduce communication overhead. By increasing the window size when network conditions allow, fewer acknowledgement frames and re-transmission attempts are needed, directly reducing the quantity of communication overhead while maintaining reliable delivery through adaptive error handling.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The invention changes the fragmentation window size parameter from fixed to variable, allowing the system to optimize the balance between reliability and communication overhead by selecting appropriate window sizes based on network conditions, device states, and transmission requirements.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If individual acknowledgements are sent for each data block, then data transmission reliability is improved, but power consumption and communication overhead increase

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent merges multiple individual acknowledgements into batched or consolidated acknowledgement mechanisms. Instead of sending separate ACK frames for each data block, the system can combine acknowledgements for multiple blocks, reducing the number of radio transmissions and associated power consumption while maintaining reliable delivery confirmation.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system dynamically determines whether to send individual or batched acknowledgements based on network conditions, device states, and transmission progress. This adaptive approach allows the system to maintain reliability through individual ACKs when needed while reducing power consumption through batched acknowledgements when conditions permit.

Inventive Principle:
Principle #15Dynamics

4Reliability

If re-transmission of data blocks is performed until acknowledgement is received, then data delivery reliability is improved, but communication overhead and transmission time increase

Engineering Contradiction:
Improvedata delivery reliabilityVSAvoidcommunication overhead
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent implements preliminary actions to prevent the need for re-transmissions. This includes proactive error detection, forward error correction mechanisms, and optimized transmission scheduling that reduces the likelihood of transmission failures, thereby reducing the frequency of re-transmission operations and associated communication overhead.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback mechanisms to monitor transmission success and adapt re-transmission strategies. By analyzing acknowledgement patterns, error rates, and network conditions, the system can adjust re-transmission parameters, reduce unnecessary re-transmissions, and optimize the balance between reliability and communication overhead.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20260082273A1Zigbee Router Device, Zigbee End Device, System and Methods for Reducing Redundancy
Publication Date: 2026.03.19 NXP USA INC
  • US20260082273A1 patent drawing
  • US20260082273A1 patent drawing
  • US20260082273A1 patent drawing

AI summary

A method for delivering data frames from a source device to a Zigbee end device, ZED, via a Zigbee router, ZR, comprises, at the ZR, receiving individual data blocks with a fragmentation window of ‘1’ data block between the ZR and the source, individually transmitting an APS acknowledgement for received data blocks identified by APS transmission parameters. Data blocks are re-transmitted until an acknowledgement of a successful receipt is transmitted to the source. The data block is transmitted to the ZED until an acknowledgement is received. Following a penultimate data block having been transmitted from the ZR and acknowledged by the ZED, the method further comprises at the ZED: transmitting a second data request to the ZR for a final data block; and transmitting an APS acknowledgement of successfully receiving the final data block to the ZR; and to the source.