Multicast ACK Consolidation via Access Point Mediation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In large multicast communication systems, the flood of acknowledgments can lead to system performance degradation due to the ACK implosion effect, resulting in lost acknowledgments and increased retransmissions.

Innovation Solution

Implementing a method where an access point waits for a multicast ACK from stations and sends an ACK-ACK, allowing stations to avoid re-acknowledging already received multicast packets, thereby reducing unnecessary acknowledgments and improving system efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If each endpoint sends an acknowledgement for every multicast packet, then reliability is improved, but the number of acknowledgements floods the system degrading performance

Engineering Contradiction:
Improvepacket delivery reliabilityVSAvoidACK implosion effect
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

Multiple individual ACKs from different endpoints are merged into a single grouped ACK message. The access point collects ACKs from multiple stations and transmits them as one consolidated message, reducing the total number of ACK messages in the system while maintaining reliability tracking for all endpoints.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The access point acts as an intermediary that collects and consolidates ACKs from multiple endpoints before transmitting them back to the source. This mediator role prevents direct endpoint-to-endpoint ACK flooding by centralizing the acknowledgment process at the access point.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If acknowledgements are lost due to system flooding, then system performance degrades, but retransmissions are needed to maintain reliability

Engineering Contradiction:
Improvepacket delivery reliabilityVSAvoidsystem throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

By merging multiple ACKs into one grouped ACK message, the system reduces the likelihood of ACK loss due to flooding. Fewer individual ACK messages mean lower probability of loss, thereby maintaining reliability without triggering excessive retransmissions that would reduce throughput.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If the multicast group is large, then multicasting capability is improved, but the number of acknowledgements floods the system

Engineering Contradiction:
Improvemulticast group size capabilityVSAvoidACK implosion effect
Core Design Contradiction:
Adaptability or versatilityVSObject-generated harmful factors

Solution Approach 1:

The system merges acknowledgements from all members of large multicast groups into single consolidated ACK messages. This allows the system to handle large multicast groups effectively, as the grouped ACK approach scales better than individual ACKs from each member, reducing the harmful flooding effect while maintaining the ability to serve large groups.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS7561599B2Method of reliable multicasting
Publication Date: 2009.07.14 MOTOROLA SOLUTIONS INC
  • US7561599B2 patent drawing
  • US7561599B2 patent drawing
  • US7561599B2 patent drawing

AI summary

A method for providing reliable multicasting is described. A transmitted multicast packet is received at second devices, each of which in response transmits a first acknowledgement. If a second acknowledgement, which acknowledges the first acknowledgement, is not received within a predetermined time period, the first acknowledgement is retransmitted. If all first acknowledgements are not received within a preset time period, the multicast packet is retransmitted. If the retransmitted multicast packet has been received, at each of the second devices, if the second acknowledgement has not been received the first acknowledgement is retransmitted, while if the second acknowledgement has been received, the retransmitted multicast packet is ignored and no additional first acknowledgement is transmitted.