Derivative works — US Patent 11664926

Defensive Disclosure: Derivatives for US Patent 11664926

This document outlines various technical derivatives and combinations of the subject matter described in US Patent 11664926. The intent is to establish prior art for future incremental improvements by competitors, demonstrating the obviousness or lack of novelty of such variations within the scope of aggregated MAC Protocol Data Unit (A-MPDU) handling and response frame mechanisms.

Derivatives for Claims 1 & 9 (Transmitter Side: A-MPDU Generation, Transmission, and Success Determination)

1. Material & Component Substitution: Optical Transceiver for A-MPDU Communication

Enabling Description:
A wireless communication terminal integrates a coherent optical transceiver operating in the 1550 nm wavelength band for data transmission, replacing traditional radio frequency (RF) communication. The terminal's processor generates A-MPDUs, encapsulating one or more MAC Protocol Data Units (MPDUs) that solicit an immediate response. These electrical A-MPDU signals are fed into an optical modulator (e.g., Mach-Zehnder modulator with an external laser source) which converts them into coherent optical pulses. These pulses are transmitted over a free-space optical (FSO) link using a collimated beam. Upon receiving an optical response frame, a photodetector (e.g., InGaAs avalanche photodiode) converts the optical signal back into an electrical signal. The processor then analyzes this electrical response frame, performing cyclic redundancy checks (CRCs) and sequence number verification, to determine the successful transmission status of the constituent MPDUs within the original A-MPDU. This system utilizes forward error correction (FEC) coding within the optical payload for channel robustness, augmenting the A-MPDU's inherent error detection.

graph TD
    A[Processor] --> B{Generate A-MPDU};
    B --> C[Electrical Signal];
    C --> D[Optical Modulator];
    D --> E[FSO Link];
    E --> F[Optical Demodulator];
    F --> G[Photodetector];
    G --> H[Electrical Response];
    H --> I{Determine Success};
    I --> J[Output Status];

2. Operational Parameter Expansion: Nanoscale Inter-Chip A-MPDU Aggregation

Enabling Description:
Within a high-performance multi-core processor or System-on-Chip (SoC) architecture, the inter-core communication fabric employs A-MPDU aggregation. The "communication unit" consists of on-chip optical waveguides, plasmonic interconnects, or advanced electrical through-silicon vias (TSVs). A dedicated hardware accelerator (functioning as the "processor") on a source core aggregates micro-instruction blocks, cache coherence messages (e.g., MESI protocol messages), or memory access requests into a nanoscale A-MPDU. These MPDUs solicit immediate responses (e.g., cache line grants, memory write acknowledgments). The aggregated A-MPDU is transmitted at picosecond latencies across the on-chip interconnect. A receiving core's hardware accelerator processes the A-MPDU and generates a compact response frame (e.g., a single bit-vector acknowledgment) indicating the successful processing or execution of the aggregated messages.

graph TD
    A[Source Core Processor] --> B{Aggregate Micro-Instructions / Coherence Msgs into A-MPDU};
    B --> C[On-chip Interconnect (Optical/Plasmonic/TSV)];
    C --> D[Receiving Core Processor];
    D --> E{Generate Response Frame};
    E --> F[On-chip Interconnect (Optical/Plasmonic/TSV)];
    F --> G[Source Core Processor];
    G --> H{Determine Success (e.g., Cache Hit/Miss, Instruction Complete)};

3. Cross-Domain Application: Maritime Acoustic A-MPDU for Underwater AUVs

Enabling Description:
In an underwater acoustic sensor network, Autonomous Underwater Vehicles (AUVs) utilize A-MPDU aggregation for efficient communication. The AUV's main controller (processor) aggregates various data types such as sonar pings, environmental sensor readings (temperature, salinity), and mission status updates into A-MPDUs. Each MPDU within the A-MPDU is tagged to solicit an immediate acoustic response. These A-MPDUs are then transmitted via a directional acoustic transducer (communication unit) using frequency-hopping spread spectrum or orthogonal frequency-division multiplexing (OFDM) acoustic modulation. Upon reception by another AUV or a surface buoy, an acoustic hydrophone array detects the signal. The receiving AUV's processor demodulates and decodes the A-MPDU, determines the integrity of individual MPDUs, and generates an acoustic response frame (e.g., a compressed BlockAck or an M-BA equivalent) indicating which aggregated data blocks were successfully received, which is then acoustically transmitted back.

sequenceDiagram
    participant A as AUV Transmitter
    participant B as Underwater Channel
    participant C as AUV Recipient

    A->>B: Transmit Aggregated Sensor Data A-MPDU (Acoustic)
    activate B
    B-->>C: A-MPDU Received
    deactivate B
    C->>C: Process A-MPDU; Determine MPDU success
    C->>C: Generate Acoustic Response Frame (e.g., M-BA)
    C->>B: Transmit Response Frame (Acoustic)
    activate B
    B-->>A: Response Frame Received
    deactivate B
    A->>A: Determine A-MPDU Transmission Success based on Response

4. Integration with Emerging Tech: AI-Driven A-MPDU Content & Schedule Optimization

Enabling Description:
A wireless communication terminal's processor is augmented with an integrated Artificial Intelligence (AI) inference engine (e.g., a specialized ASIC or a reconfigurable FPGA fabric running a lightweight neural network). This AI engine dynamically optimizes the A-MPDU generation process. It uses real-time channel quality indicators (CQI), predicted traffic load, historical retransmission rates, and application-specific Quality of Service (QoS) requirements as inputs. Before generating an A-MPDU, the AI engine predicts the optimal number of MPDUs to aggregate, the specific Traffic IDs (TIDs) to include for immediate response solicitation, and the optimal transmission parameters (e.g., MCS, transmit power). This dynamic optimization aims to maximize A-MPDU delivery success and minimize overall latency by predicting recipient acknowledgment capabilities and channel stability. The processor then generates the A-MPDU based on the AI's recommendations, transmits it, and uses the received response frame as feedback to further train or fine-tune the AI model.

graph TD
    A[Application Data] --> B{AI Optimizer};
    C[Channel State Info] --> B;
    D[Historical Tx Data] --> B;
    B --> E[Optimized A-MPDU Params];
    E --> F[Processor: Generate A-MPDU];
    F --> G[Communication Unit: Transmit A-MPDU];
    G --> H[Communication Unit: Receive Response];
    H --> I[Processor: Determine Success];
    I --> J[Feedback to AI Optimizer];
    I --> K[Output Tx Status];

5. Integration with Emerging Tech: IoT Sensor Gateway with Blockchain-Secured A-MPDU

Enabling Description:
An IoT sensor gateway, acting as a wireless communication terminal, aggregates data from a mesh network of low-power IoT devices. The gateway's processor collects sensor readings (e.g., temperature, humidity, vibration), device health metrics, and control signals from multiple devices. It then constructs an A-MPDU where each constituent MPDU contains not only the sensor data but also a cryptographic hash (e.g., SHA-256) of its payload and associated metadata (timestamp, sensor ID). The entire A-MPDU structure, including its sequence number and a Merkle tree root of all contained MPDU hashes, is digitally signed by the gateway's private key. This signed A-MPDU is transmitted to a central data sink. A blockchain integration module within the gateway (or the data sink) then records the Merkle root hash or the entire A-MPDU's metadata onto a distributed ledger, providing tamper-evident proof of data origin and integrity. The received response frame from the data sink or blockchain oracle confirms successful data reception and commitment to the ledger, enabling verifiable data provenance for critical IoT applications.

sequenceDiagram
    participant D as IoT Devices
    participant G as IoT Gateway (Tx)
    participant S as Data Sink (Rx)
    participant B as Blockchain Ledger

    D->>G: Send Sensor Data (Individual Frames)
    G->>G: Aggregate data into A-MPDU; Hash each MPDU; Create Merkle Tree; Sign A-MPDU
    G->>S: Transmit Blockchain-Secured A-MPDU
    S->>S: Validate A-MPDU Signature & Hashes
    S->>B: Commit A-MPDU Merkle Root/Metadata
    B-->>S: Confirmation of Ledger Entry
    S->>G: Transmit Response Frame (incl. Blockchain Status)
    G->>G: Determine A-MPDU Transmission Success & Blockchain Confirmation

6. The "Inverse" or Failure Mode: Degraded-Mode A-MPDU for Critical Infrastructure

Enabling Description:
In a wireless communication terminal deployed within critical infrastructure (e.g., an industrial control system managing a power plant), the processor implements a degraded-mode A-MPDU generation strategy upon detection of severe channel interference, high error rates, or partial network outages. In this mode, the processor strictly filters MPDUs, aggregating only safety-critical messages (e.g., emergency shutdown commands, alarm signals, essential telemetry) into the A-MPDU, while discarding or deferring non-essential traffic. The "communication unit" applies maximal redundancy coding (e.g., high-rate LDPC codes or repeat-until-correct schemes) to these critical MPDUs, sacrificing bandwidth for increased robustness. The A-MPDU format is simplified, potentially omitting non-critical header fields. The expected immediate response frame from the recipient is also simplified, possibly just a single bit acknowledgment or a concise error code indicating that only critical MPDUs were processed. If a full response (e.g., BlockAck with bitmap) is not received, the system assumes failure and immediately retransmits the critical A-MPDU in an even more robust format or triggers an alternative communication path.

stateDiagram
    [*] --> Normal_Mode: System Startup
    Normal_Mode --> Interference_Detected: Channel Degradation
    Interference_Detected --> Degraded_A-MPDU_Mode: Switch Mode
    Degraded_A-MPDU_Mode --> Generate_Critical_A-MPDU: Prioritize MPDUs
    Generate_Critical_A-MPDU --> Transmit_Robust_A-MPDU: Apply Max Redundancy
    Transmit_Robust_A-MPDU --> Await_Simplified_Response: Expect Minimal ACK
    Await_Simplified_Response --> Degraded_A-MPDU_Mode: Re-evaluate
    Await_Simplified_Response --> Critical_Failure_Detected: No Response / Unsuccessful Critical MPDUs
    Critical_Failure_Detected --> Activate_Alternative_Path: Switch to backup
    Degraded_A-MPDU_Mode --> Normal_Mode: Channel Restored

Derivatives for Claims 10 & 18 (Receiver Side: A-MPDU Reception, Response Format Determination, and Transmission)

1. Material & Component Substitution: Quantum-Accelerated Response Format Determination

Enabling Description:
A wireless communication terminal, acting as an A-MPDU recipient, utilizes a specialized quantum co-processor or a quantum-accelerated Field-Programmable Gate Array (FPGA) alongside its conventional processor for ultra-fast response frame format determination. Upon receiving an A-MPDU, the classical processor performs initial frame parsing. Complex decision logic for determining the response frame format (e.g., Ack, Compressed BlockAck (C-BA), Multi-STA BlockAck (M-BA))—which depends on factors like the number of Traffic IDs (TIDs) soliciting immediate responses, MPDU delimiter information (EOF field values), and the presence of specific acknowledgment policies across multiple MPDUs—is offloaded to the quantum accelerator. This accelerator performs parallel evaluation of all possible acknowledgment contexts (e.g., identifying conflicting BlockAck and immediate Ack requirements) at high speeds, exploiting quantum parallelism to quickly output the optimal response frame format. The classical processor then constructs and transmits the response frame using this determined format.

classDiagram
    class WirelessTerminal {
        -Processor classicalProcessor
        -QuantumAccelerator quantumCoProcessor
        -CommunicationUnit commUnit
        +receiveA-MPDU()
        +determineResponseFormat()
        +transmitResponseFrame()
    }
    class A-MPDU {
        -MPDU[] mpdus
        -TID[] tidsSolicitingResponse
        -MPDUDelimiter[] delimiters
    }
    class ResponseFrame {
        -ResponseFormat format
        -ACKContext ackContext
    }
    WirelessTerminal "1" *-- "1" A-MPDU : receives
    WirelessTerminal "1" *-- "1" ResponseFrame : transmits
    classicalProcessor "1" *-- "1" quantumCoProcessor : offloads_decision
    quantumCoProcessor ..> ResponseFrame : determines_format

2. Operational Parameter Expansion: Terahertz (THz) A-MPDU Receiver for High-Throughput Backhaul

Enabling Description:
A wireless communication terminal functioning as a network node (e.g., a backhaul aggregation point) in a Terahertz (THz) communication system (operating, for instance, at 300 GHz) is configured to receive A-MPDUs. The communication unit comprises a THz receiver front-end, employing highly directional parabolic antennas and ultra-low noise amplifiers, coupled with a high-speed analog-to-digital converter (ADC) capable of multi-GSPS sampling. The terminal's processor, implemented as a custom Application-Specific Integrated Circuit (ASIC) with specialized parallel processing units, is optimized for THz data rates. Upon reception of a THz A-MPDU, the ASIC performs rapid frame synchronization, channel equalization, and MAC layer parsing. It determines the response frame format (e.g., an extremely compact M-BA frame) by evaluating the successfully received MPDUs, their respective TIDs, and acknowledgment policies within picoseconds. This determination must occur within strict timing windows to maintain the high throughput and low latency characteristics of THz links, ensuring efficient acknowledgment and retransmission cycles.

graph TD
    A[THz Antenna Array] --> B[THz Receiver Front-End];
    B --> C[High-Speed ADC];
    C --> D[ASIC Processor];
    D --> E{Parse A-MPDU};
    E --> F{Determine Response Format (picosecond latency)};
    F --> G[Generate Response Frame];
    G --> H[THz Transmitter Front-End];
    H --> I[THz Antenna Array];

3. Cross-Domain Application: Autonomous Driving - Sensor Fusion A-MPDU Receiver

Enabling Description:
In an autonomous vehicle, the central sensor fusion unit acts as a wireless communication terminal receiving A-MPDUs from various on-board sensors (e.g., LiDAR, radar, camera, ultrasonic) and potentially from Vehicle-to-Everything (V2X) communications. Each sensor/V2X module aggregates its raw data or processed perceptions (e.g., object detection bounding boxes, distance measurements, road conditions) into A-MPDUs, which are then transmitted over an internal high-speed network (e.g., automotive Ethernet, proprietary wireless bus). The vehicle's main processor (acting as the recipient processor) receives these A-MPDUs. It rapidly determines the format of a control response frame based on the aggregated information's immediacy requirements and criticality. For example, a response could be an immediate "emergency braking" command (Ack-like for a single critical MPDU) or a consolidated "lane keeping assist adjustment" (M-BA-like for multiple non-critical but relevant MPDUs). This response frame is then transmitted directly to vehicle actuators (e.g., braking system, steering control) or broadcast to other V2X units, requiring ultra-low latency decision-making for real-time safety.

graph TD
    A[LiDAR Sensor] -- A-MPDU --> D(Sensor Fusion Unit Processor);
    B[Radar Sensor] -- A-MPDU --> D;
    C[Camera Module] -- A-MPDU --> D;
    D --> E{Determine Response Format (e.g., "Brake", "Steer")};
    E --> F[Generate Control Response Frame];
    F --> G[Actuator Controller];
    G --> H[Vehicle Actuators (Brakes, Steering)];

4. Integration with Emerging Tech: Neural Network-Based Adaptive Response Format Selection

Enabling Description:
A wireless communication terminal's processor for A-MPDU reception is enhanced with an embedded Deep Learning Neural Network (DNN) inference engine. This DNN, continuously updated through on-device learning or cloud-based training, receives as input the parsed contents of a received A-MPDU (e.g., number of TIDs, acknowledgment policies, MPDU types, measured signal-to-noise ratio, current network congestion status). Based on these inputs, the DNN predicts the optimal response frame format (Ack, C-BA, M-BA, or a fine-grained custom acknowledgment) that will maximize network throughput, minimize latency, and satisfy the sender's Quality of Service (QoS) requirements under current conditions. This adaptive format selection, moving beyond static rule-based decisions, allows for more nuanced and efficient acknowledgment strategies, particularly in highly dynamic and congested wireless environments.

graph TD
    A[Received A-MPDU] --> B{A-MPDU Parser};
    B --> C[Feature Extractor];
    C --> D[DNN Inference Engine];
    E[Channel Metrics] --> D;
    F[Network Load] --> D;
    D --> G[Optimal Response Format];
    G --> H[Processor: Generate Response Frame];
    H --> I[Communication Unit: Transmit Response];

5. Integration with Emerging Tech: Digital Twin Feedback Loop Response Generation

Enabling Description:
In a cyber-physical system, a wireless communication terminal located at an edge computing node hosts a digital twin of a complex physical asset (e.g., a robotic arm, a manufacturing assembly line, or an environmental monitoring station). This edge node acts as the recipient, receiving A-MPDUs containing aggregated real-time sensor data (e.g., motor temperatures, strain gauges, operational parameters) from the physical asset. The edge node's processor feeds this A-MPDU data into the digital twin's simulation engine. The digital twin processes the aggregated inputs, simulates the physical asset's current and predicted future state, and identifies any anomalies or required adjustments. Based on the digital twin's analysis, the processor determines the format of a control response frame. This response could be a detailed diagnostic report (M-BA-like with extensive per-component status), an immediate corrective action command (Ack-like), or a predictive maintenance alert (C-BA-like for grouped but less urgent information). The response frame is then transmitted back to the physical asset's local controllers.

sequenceDiagram
    participant P as Physical Asset (Sensors)
    participant E as Edge Node (Recipient/Digital Twin)
    participant C as Asset Controllers

    P->>E: Transmit Aggregated Sensor Data A-MPDU
    activate E
    E->>E: Process A-MPDU; Feed to Digital Twin
    E->>E: Digital Twin Simulates; Analyzes State
    E->>E: Determine Optimal Control Response Format
    E->>C: Transmit Control Response Frame
    deactivate E
    C->>P: Apply Control Actions

6. The "Inverse" or Failure Mode: Prioritized A-MPDU Response for Emergency Systems

Enabling Description:
In a wireless communication terminal designed for emergency services (e.g., a first responder's ruggedized communication device), the processor implements a prioritized A-MPDU response strategy during extreme network congestion or partial frame corruption. Upon receiving an A-MPDU, the processor first attempts to identify and parse mission-critical MPDUs (e.g., location coordinates, emergency alerts, critical voice packets). If the entire A-MPDU cannot be successfully received or fully processed (e.g., due to insufficient processing power or severe interference), the system defaults to generating a simplified response frame. This response might be a single, immediate Acknowledgement (Ack) specifically for the highest-priority MPDU that was successfully parsed, or a Negative Acknowledgement (NACK) combined with a limited error code indicating that only a subset of critical data was decipherable. The response frame explicitly omits bitmap-based BlockAck information for lower-priority TIDs to conserve transmission resources and provide timely, albeit partial, feedback to the sender regarding the most vital information.

stateDiagram
    [*] --> Idle_Rx
    Idle_Rx --> A-MPDU_Received: New A-MPDU
    A-MPDU_Received --> Parse_Critical_MPDUs: Prioritize Parsing
    Parse_Critical_MPDUs --> All_MPDUs_Valid: Full Success
    All_MPDUs_Valid --> Generate_Full_Response: (e.g., M-BA)
    Parse_Critical_MPDUs --> Partial_Success_Critical_Only: Critical MPDUs Valid, Others Failed/Corrupt
    Partial_Success_Critical_Only --> Generate_Partial_Response: (e.g., Ack for critical, NACK others)
    Parse_Critical_MPDUs --> All_Failed: No Critical MPDUs Parsed
    All_Failed --> Generate_Error_Response: (e.g., NACK with error code)
    Generate_Full_Response --> Transmit_Response
    Generate_Partial_Response --> Transmit_Response
    Generate_Error_Response --> Transmit_Response
    Transmit_Response --> Idle_Rx

Combination Prior Art Scenarios

1. US11664926 + IEEE 802.11ay (NG60) Standard

Description:
The inventive concepts of US Patent 11664926, pertaining to the dynamic generation and processing of Aggregate MAC Protocol Data Units (A-MPDUs) and the determination of corresponding response frame formats based on factors like the number of Traffic IDs (TIDs) soliciting immediate responses and MPDU delimiter information (e.g., EOF field values), are directly applied to the operational framework defined by the IEEE 802.11ay standard. IEEE 802.11ay, often referred to as Next Generation 60 GHz (NG60), is designed for extremely high throughput, typically in the multi-gigabit per second range, utilizing wide bandwidths in the 60 GHz spectrum. This standard extensively employs A-MPDU aggregation and multi-user MIMO (MU-MIMO) to achieve its performance targets. Integrating the patent's logic would enhance 802.11ay's efficiency by allowing transmitting devices to intelligently construct A-MPDUs tailored to anticipated channel conditions and recipient capabilities, and enabling receiving devices to precisely determine optimal acknowledgment frames (such as multi-STA BlockAck, M-BA) for rapidly acknowledging vast amounts of aggregated data across multiple users. This combination makes the patent's teachings a natural and obvious extension for optimizing data flow and acknowledgment processes in 60 GHz high-density, high-throughput wireless networks.

2. US11664926 + OpenWrt/Linux Wireless MAC Layer Implementation

Description:
The methodologies detailed in US Patent 11664926 for generating A-MPDUs, determining the success of MPDU transmissions (as in Claims 1 and 9), and for receiving A-MPDUs, determining appropriate response frame formats, and transmitting them (as in Claims 10 and 18), are implemented within the open-source Linux kernel's wireless subsystem, specifically the mac80211 framework, and/or within custom firmware/drivers integrated into an OpenWrt distribution. This involves modifying existing A-MPDU aggregation and de-aggregation routines within the MAC layer to incorporate the patent's logic concerning multi-TID A-MPDUs and the nuanced criteria for selecting response frame types (Ack, C-BA, M-BA) based on the characteristics of the received A-MPDU and reception status. For example, a patch to mac80211 could introduce a configurable policy that, upon detecting an A-MPDU containing MPDUs from multiple TIDs soliciting immediate responses, automatically generates an M-BA frame, as described in the patent. This integration transforms the patent's claims into core functionalities within widely adopted open-source wireless networking stacks, making such implementations an obvious engineering choice for enhancing Wi-Fi performance.

3. US11664926 + IETF QUIC Protocol (RFC 9000 series)

Description:
The principles of efficient data aggregation and selective acknowledgment described in US Patent 11664926 are applied to optimize the framing and acknowledgment mechanisms of the IETF QUIC (Quick UDP Internet Connections) transport layer protocol, as defined by RFC 9000 and subsequent specifications. A specialized network interface controller (NIC) or an optimized operating system's transport layer implementation, supporting QUIC, uses the patent's logic. On the transmitting side, the NIC aggregates multiple small QUIC STREAM frames or coalesces multiple QUIC ACK frames destined for the same recipient into a single A-MPDU-like structure before encapsulation in UDP and IP for physical transmission. On the receiving side, a "QUIC-aware" NIC or driver processes the incoming A-MPDU, extracts the individual QUIC frames, and utilizes the patent's method for determining the most efficient acknowledgment response. For example, if the received A-MPDU contains multiple QUIC STREAM frames across different application streams (analogous to TIDs) requiring acknowledgment, the NIC dynamically determines and generates a single, aggregated QUIC ACK frame (analogous to an M-BA or C-BA) that efficiently acknowledges all received streams, reducing overhead and improving QUIC's inherent latency advantages. This extension moves the patent's MAC layer optimization concepts into the realm of transport layer framing and acknowledgment.