Service Flow Deletion via Missing Acknowledgement Feedback

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional IEEE 802.16 wireless communication standards can lead to ambiguous states during service flow establishment, resulting in wasteful resource usage and battery power consumption when the initiator station transmits payload traffic without a valid acknowledgement, assuming the service flow is established despite the receiver ignoring the transmissions.

Innovation Solution

Implementing a three-way handshake protocol in wireless network devices, where the responder station issues a service flow delete request if no valid acknowledgement is received, ensuring the initiator does not transmit payload traffic unnecessarily and freeing resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the initiator station transmits payload traffic without receiving a valid acknowledgement, then the service flow establishment appears complete from the initiator's perspective, but the receiver station ignores the transmissions resulting in resource wastage and battery power consumption

Engineering Contradiction:
Improveservice flow establishment reliabilityVSAvoidbattery power consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent implements a feedback mechanism where the responder station monitors whether it receives a valid acknowledgement from the initiator. If no valid acknowledgement is received within a specified time period, the responder sends a service flow delete request to the initiator, providing feedback that prevents the initiator from continuing to transmit payload traffic that would be ignored by the receiver.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent applies preliminary action by having the responder station proactively send a service flow delete request before the initiator can waste significant resources transmitting payload traffic. This preliminary termination action prevents the ambiguous state from persisting and causing extensive energy consumption and resource wastage.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the responder station continuously retransmits service flow response messages waiting for an acknowledgement, then the service flow establishment process remains open, but transmission resources are consumed without productive data transfer

Engineering Contradiction:
Improveacknowledgement receipt assuranceVSAvoidservice flow establishment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by setting a maximum time period for waiting for acknowledgements and proactively terminating the service flow establishment process if no valid acknowledgement is received within this period. This prevents indefinite waiting and resource consumption while ensuring reliable service flow establishment through timely detection of failed acknowledgements.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback mechanisms where the responder station monitors the absence of valid acknowledgements and responds by sending delete requests or timing out the establishment process, creating a closed-loop control that prevents resource wastage while maintaining reliability.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If the initiator station assumes service flow establishment is complete after sending an acknowledgement, then the establishment process is simplified, but the receiver station may ignore payload transmissions causing resource wastage

Engineering Contradiction:
Improveservice flow establishment simplicityVSAvoidtransmission resource wastage
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The patent maintains the simple assumption-based approach at the initiator while adding a feedback mechanism at the responder side. The responder monitors whether it receives valid acknowledgements and provides feedback by sending delete requests if acknowledgements are missing, thus preventing resource wastage without complicating the initiator's simple establishment process.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The service flow delete request acts as an intermediary mechanism that resolves the ambiguity between the initiator's assumption of successful establishment and the receiver's actual state. This intermediary message allows the system to maintain simplicity at the initiator while preventing resource wastage through coordinated termination at the responder.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8130653B2Deletion request after number of failed acknowledgements to addition requests
Publication Date: 2012.03.06 TEXAS INSTRUMENTS INC
  • US8130653B2 patent drawing
  • US8130653B2 patent drawing
  • US8130653B2 patent drawing

AI summary

Network circuitry and a method of operating the same in establishing and deleting a service flow in a wireless network. A network station receives a request, from an initiating network station, to establish a service flow. The network station receiving the request issues a response to that request, following which it expects an acknowledgement from the initiator. Upon absence of such an acknowledgement, the receiving station transmits a message, to the initiator, to explicitly delete the service flow. This ensures that the initiator is not placed into an ambiguous state of transmitting payload traffic to a receiver that is ignoring or not receiving that traffic, in the case in which the initiator is also the transmitter of the payload traffic. This circuitry and method also ensures that the initiator is not in an ambiguous state, in the case in which it is the intended receiver of the payload traffic.