Abort Signaling in Wireless Packet Headers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Wireless communication systems face challenges in efficiently terminating ongoing packet transmissions, leading to undesired delays and increased data-packet error rates due to rigid transmission protocols that lack preemptive termination mechanisms, especially in segmented packet communications.
Innovation Solution
The implementation of a code-point in the data unit header to indicate the abortion of an ongoing communication, utilizing either a dedicated abort data unit field or a combination of predefined header fields with invalid or unlikely values, allows for efficient signaling of transmission termination, thereby mitigating disruption and conserving channel capacity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a rigid transmission protocol is used for segmented packet communication, then packet transmission can be maintained with standard protocols, but preemptive termination of ongoing packet communications cannot be achieved, leading to increased delays and error rates
Solution Approach 1:
The patent applies dynamics by transforming the rigid transmission protocol into a dynamic system that supports preemptive termination. The MAC header is enhanced with an abort indication field that can dynamically change the transmission state from mandatory completion to optional termination, allowing the protocol to adapt to changing network conditions and priority requirements during ongoing packet communications.
Solution Approach 2:
The patent changes the parameter structure of the MAC header by adding an abort indication field with specific values (e.g., '1' for abort, '0' for continue). This parameter change enables the system to signal termination intentions without altering the fundamental packet structure, allowing preemptive termination while maintaining protocol compatibility.
2Productivity
If ongoing packet communications are not aborted preemptively, then transmission completion can be ensured, but channel capacity is wasted and transmission disruptions occur
Solution Approach 1:
The patent implements preliminary action by allowing the transmitter to signal abort intentions before the packet transmission is fully completed. The abort indication field is set in advance when termination becomes necessary, enabling the receiver to prepare for early termination and release channel resources before the full packet is transmitted, thus avoiding wasted channel capacity and reducing transmission disruptions.
3Adaptability or versatility
If a dedicated abort field is added to the data unit header, then preemptive termination signaling is enabled, but header structure complexity increases
Solution Approach 1:
The patent applies universality by designing the abort indication field to serve multiple functions within the MAC header structure. The same field can indicate both normal transmission continuation (value '0') and abort intentions (value '1'), and can be combined with existing header fields to provide different termination scenarios. This multi-functionality reduces the need for separate dedicated fields and minimizes overall header complexity.
4Device complexity
If existing header fields are combined to indicate abort, then no additional fields are needed, but the likelihood of collision with legitimate values increases
Solution Approach 1:
The patent applies local quality by assigning specific, unique values to existing header fields for abort indication purposes. Instead of using arbitrary combinations, the patent designates specific value ranges or patterns (e.g., particular combinations of flag bits) that are reserved exclusively for abort indications. This localized assignment ensures that legitimate data values cannot be confused with abort signals, eliminating collision risks while maintaining header field count efficiency.
Data Source
AI summary
Systems and methods are provided for a signaling an ongoing communication of a data unit in a data packet is to be aborted. Upon a determination to abort an ongoing communication is made, a code-point in a data unit header is utilized to indicate the ongoing communication is to be aborted. A first class of code-point is a dedicated, predefined abort data unit field header. A second class of code-point is a combination of a set of existing, predefined data unit header fields, at least one data unit header field in the combination holds a value that is either invalid or legitimate yet unlikely to occur. Conveying code-point(s) to indicate termination of an ongoing communication of a data unit in a data packet in a regular communication mitigates transmission disruption and saves channel capacity.