Wireless Multicast Reliability via Client Acknowledgment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Wireless multicast transmissions in wireless networks are unreliable due to the lack of acknowledgments for multicast packets, leading to inefficiencies and unreliability, especially in dense deployments, which affects applications like video and audio that require reliable data.

Innovation Solution

Identifying a client as an acknowledger for a wireless multicast packet by placing its MAC address in the packet header and retrying the packet if no acknowledgment is received, allowing for improved reliability without increasing overhead or efficiency costs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multicast packets are transmitted without acknowledgments in wireless networks, then transmission efficiency is improved, but reliability deteriorates

Engineering Contradiction:
Improvetransmission efficiencyVSAvoiddata delivery reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system designates specific client devices to autonomously monitor and acknowledge multicast packet reception without requiring active participation from all recipients. The designated client self-services the acknowledgment function, reducing overall system overhead while ensuring reliability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

A designated client acts as an intermediary between the multicast transmitter and the network, receiving multicast packets and providing acknowledgments on behalf of the group. This intermediary approach maintains efficiency by avoiding multiple acknowledgments while ensuring reliability through dedicated monitoring.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multicast transmissions are converted to multiple unicast transmissions with acknowledgments, then reliability is improved, but overhead increases and efficiency decreases

Engineering Contradiction:
Improvedata delivery reliabilityVSAvoidtransmission overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system merges multiple acknowledgment functions into a single acknowledgment from one designated client. Instead of requiring separate acknowledgments from each recipient, the designated client consolidates the acknowledgment function, reducing overhead while maintaining reliability.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The designated client performs multiple functions: receiving multicast packets, monitoring transmission quality, and providing acknowledgments. This multi-functional approach eliminates the need for separate acknowledgment mechanisms for each recipient, reducing overall system complexity and overhead.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If media reservation schemes are implemented for every packet, then reliability is improved, but efficiency deteriorates

Engineering Contradiction:
Improvetransmission reliabilityVSAvoidtransmission efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Instead of implementing media reservation for every single packet transmission, the system applies partial action by using acknowledgments only when necessary (when packets are lost or not received). This selective approach maintains reliability for critical transmissions while avoiding the efficiency penalties of continuous media reservation.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS8457031B2System and method for reliable multicast
Publication Date: 2013.06.04 TRAPEZE NETWORKS INC
  • US8457031B2 patent drawing
  • US8457031B2 patent drawing
  • US8457031B2 patent drawing

AI summary

A technique for reliable multicast involves identifying a client as an acknowledger of a wireless multicast packet, and having the acknowledger acknowledge receipt of the multicast packet. An example of a method according to the technique may include receiving a multicast packet, selecting a client associated with a destination of the multicast packet, identifying the client in the multicast packet, forwarding the multicast packet to wireless, and retrying forwarding the multicast packet with the client identified in the multicast packet if no acknowledgement is received from the client. An example of a system according to the technique may include a means for identifying a client, a means for putting the client mac in the header of a multicast packet, a means for sending the multicast packet with the client mac to a wireless multicast destination, and a means for receiving acknowledgement from the client associated with the client mac.