Patent 6628629

Derivative works

Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.

Active provider: Google · gemini-2.5-flash

Derivative works

Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.

✓ Generated

Defensive Disclosure Document for US Patent No. 6,628,629

Patent Under Analysis: U.S. Patent No. 6,628,629 B1
Title: Reservation based prioritization method for wireless transmission of latency and jitter sensitive IP-flows in a wireless point to multi-point transmission system
Current Date: April 26, 2026
Role: Senior Patent Strategist and Research Engineer specializing in Defensive Publishing

This document outlines a series of derivative variations of the core inventive concepts disclosed in U.S. Patent No. 6,628,629. The aim is to proactively publish technical disclosures that render obvious or non-novel future incremental improvements by competitors, thereby establishing a broader body of prior art. These derivations expand upon the original patent's claims by exploring alternative materials and components, extreme operational parameters, cross-domain applications, integration with emerging technologies, and inverse/failure modes.

The independent claims of U.S. Patent No. 6,628,629 focus on:

  • Claims 1, 14, 26: A method, system, and machine-readable medium for assigning future time slots in a wireless telecommunication network system using an "advanced reservation algorithm" to place data packets of an Internet Protocol (IP) flow in an "isochronous manner."
  • Claims 38, 50: A telecommunications system and method for providing isochronous data packets in a wireless point-to-multipoint (PtMP) system, applying an "advanced reservation algorithm" to an IP flow to reserve succeeding slots in future transmission frames.

The derivations below address these core inventive concepts.


Derivative Variations

1. Material & Component Substitution

Derivative 1.1: Software-Defined Radio (SDR) with FPGA-Accelerated MAC

  • Enabling Description: The wireless base station and subscriber CPE stations (as described in Claims 14 and 50) are implemented using Software-Defined Radio (SDR) architectures. The "resource allocation means" and the "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) are executed on Field-Programmable Gate Arrays (FPGAs) at both the base station and CPE for ultra-low latency Medium Access Control (MAC) layer processing. This includes dedicated FPGA logic for parsing IP flow QoS requirements from packet headers, real-time calculation of future slot reservations, and dynamic reconfiguration of Time Division Multiple Access (TDMA) or Orthogonal Frequency-Division Multiple Access (OFDMA) frame structures. The radio front-end uses gallium nitride (GaN) power amplifiers for increased efficiency and linearity across a wide frequency spectrum, improving signal integrity critical for isochronous traffic.
  • Related Claims: Claims 1, 14, 26, 38, 50.
graph TD
    A[Wireless Base Station] --> B{SDR Transceiver};
    B --> C{FPGA: MAC/Scheduler};
    C --> D[IP Flow Analysis/Reservation Logic];
    D -- Calculates Slots --> E[Dynamic Frame Construction];
    E -- Allocates Slots --> F[Wireless Medium (GaN RF)];
    F --> G{SDR Transceiver};
    G --> H{FPGA: MAC/Scheduler};
    H --> I[Subscriber CPE];
    I --> J[User Application (IP Flow)];
    J -- QoS Req. --> D;
    C -- Control --> B;
    H -- Control --> G;

Derivative 1.2: Free-Space Optical (FSO) Link with Quantum-Key Distribution (QKD) for Secure IP-Flows

  • Enabling Description: The "wireless medium" (Claims 1, 14, 38, 50) is replaced with a Free-Space Optical (FSO) communication link operating in the infrared spectrum. The "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) is adapted to reserve optical pulse slots for isochronous IP flows. To enhance security for latency and jitter-sensitive IP flows (e.g., classified video conferencing), Quantum-Key Distribution (QKD) is integrated to establish highly secure cryptographic keys for encrypting the data payload, using entangled photon pairs or weak coherent pulses. The FSO transceivers utilize single-photon avalanche diodes (SPADs) for photon detection and micro-electromechanical systems (MEMS) mirrors for active beam steering and alignment, compensating for atmospheric turbulence. The isochronous placement of IP packets (Claim 1) then relies on deterministic optical slot allocation.
  • Related Claims: Claims 1, 14, 26, 38, 50.
graph TD
    A[Base Station] --> B{FSO Transceiver};
    B -- Optical Link --> C{FSO Transceiver};
    C --> D[Subscriber CPE];
    B -- QKD Channel --> B_QKD[QKD Emitter];
    C -- QKD Channel --> C_QKD[QKD Detector];
    B_QKD -- Entangled Photons --> C_QKD;
    B_QKD -- QKD Keys --> Crypto_BS[Crypto Module (Base Station)];
    C_QKD -- QKD Keys --> Crypto_CPE[Crypto Module (CPE)];
    A -- IP Flow --> Crypto_BS;
    Crypto_BS -- Encrypted Data --> B;
    C -- Encrypted Data --> Crypto_CPE;
    Crypto_CPE -- Decrypted IP Flow --> D;
    
    subgraph Scheduling and Reservation
        BS_Scheduler[Advanced Reservation Algorithm (BS)] -- FSO Slot Allocation --> B;
        CPE_Request[IP Flow QoS Request (CPE)] --> BS_Scheduler;
    end

Derivative 1.3: Millimeter-Wave (mmWave) Phased Array Antennas with Adaptive Beamforming

  • Enabling Description: The wireless transmission system (Claims 1, 14, 38, 50) operates in the millimeter-wave (mmWave) frequency bands (e.g., 28 GHz, 39 GHz) to leverage wider bandwidths. Both the base station and CPE employ phased array antennas, comprising hundreds of individual radiating elements controlled by a beamforming ASIC. The "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) dynamically allocates directional beams to individual IP flows or groups of IP flows, reserving specific time-frequency resource blocks within these beams. This allows for spatial multiplexing and interference mitigation. The isochronous delivery (Claim 1) is achieved by ensuring that the reserved time slots are allocated within a dedicated, high-gain, narrow beam directed at the CPE, minimizing multipath interference and maximizing signal-to-noise ratio (SNR) for latency-sensitive traffic.
  • Related Claims: Claims 1, 14, 26, 38, 50.
graph LR
    BS_App[Base Station Applications] -- IP Flows --> BS_Scheduler[Advanced Reservation Algorithm];
    BS_Scheduler -- Resource Block Allocation --> BS_PHY[Base Station PHY/MAC];
    BS_PHY -- Beamforming Control --> BS_Antenna[Phased Array Antenna (mmWave)];
    
    BS_Antenna -- Directed Beam --> Wireless_Medium[Wireless Medium];
    
    CPE_Antenna[Phased Array Antenna (mmWave)] -- Receives Beam --> CPE_PHY[CPE PHY/MAC];
    CPE_PHY -- Reserved Slots --> CPE_App[Subscriber Applications];
    
    CPE_App -- QoS Requests --> CPE_Feedback[CPE Feedback to BS];
    CPE_Feedback --> BS_Scheduler;
    
    style BS_Antenna fill:#f9f,stroke:#333,stroke-width:2px;
    style CPE_Antenna fill:#f9f,stroke:#333,stroke-width:2px;

2. Operational Parameter Expansion

Derivative 2.1: Nanoscale Wireless Interconnect for Intra-Chip Communication

  • Enabling Description: The "wireless telecommunication network system" (Claims 1, 14, 38, 50) is conceptualized as a nanoscale wireless interconnect within a System-on-Chip (SoC) or multi-chip module. IP flows represent inter-core or inter-accelerator data transfers. The "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) operates at picosecond-level resolution, reserving femtosecond-duration time slots for critical control signals or sensor data flows between heterogeneous cores (e.g., CPU, GPU, AI accelerator). These flows are considered "latency and jitter sensitive" due to tight timing constraints of high-performance computing. The "isochronous manner" (Claim 1) ensures deterministic communication for real-time processing tasks, using plasmonic or terahertz-band wireless links.
  • Related Claims: Claims 1, 14, 26, 38, 50.
graph TD
    A[CPU Core] -- IP Flow (Control) --> B[Wireless Nano-Interface];
    B -- THz Link (Picosecond Slots) --> C[Wireless Nano-Interface];
    C --> D[AI Accelerator];
    
    E[Memory Controller] -- IP Flow (Data) --> F[Wireless Nano-Interface];
    F -- THz Link (Picosecond Slots) --> G[Wireless Nano-Interface];
    G --> H[GPU Core];
    
    Nano_MAC[Nanoscale MAC/Scheduler] -- Reserving Slots --> B;
    Nano_MAC -- Reserving Slots --> F;
    
    subgraph SoC
        B; C; F; G; Nano_MAC;
    end

Derivative 2.2: Deep-Space Interplanetary Communication with Ultra-Long Latency Compensation

  • Enabling Description: The "wireless telecommunication network system" (Claims 1, 14, 38, 50) is a deep-space network for communication between Earth and distant spacecraft (e.g., Mars rover, Jupiter probe). The "latency and jitter sensitive IP-flows" (Claims 1, 14, 38, 50) are telemetry, command & control signals, and compressed scientific data streams. The "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) must account for propagation delays measured in minutes to hours. It schedules "future transmission frames" (Claim 1) days or weeks in advance, creating highly precise, recurring "isochronous" windows for data bursts, robust against deep-space noise and intermittent link availability. This involves predictive orbital mechanics and sophisticated error correction coding (e.g., LDPC codes). The "isochronous manner" of placing data packets (Claim 1) refers to their predictable arrival within the massive, pre-allocated time slots despite inherent latency.
  • Related Claims: Claims 1, 14, 26, 38, 50.
sequenceDiagram
    participant Earth_GS as Earth Ground Station
    participant Spacecraft as Deep Spacecraft
    participant Advanced_Algo as Advanced Reservation Algorithm (Earth)

    Earth_GS->>Spacecraft: Initial Link Setup (long delay)
    Spacecraft->>Earth_GS: State/QoS Capabilities
    Earth_GS->>Advanced_Algo: Request Isochronous Slot for Telemetry (QoS: high priority, regular intervals)
    Advanced_Algo->>Advanced_Algo: Calculate future slot reservations (days/weeks ahead)
    Advanced_Algo->>Earth_GS: Schedule confirmed (e.g., "Slot X on Day D, Time T")
    Earth_GS->>Spacecraft: Transmit Reservation Schedule (long delay)
    Spacecraft->>Spacecraft: Acknowledge & Configure
    loop Daily Telemetry Transmission
        Spacecraft->>Spacecraft: Prepare Telemetry IP Flow
        Spacecraft->>Earth_GS: Transmit Telemetry in Reserved Slot (isochronous bursts, long delay)
        Earth_GS->>Spacecraft: Acknowledge Reception
    end

Derivative 2.3: Ultra-High-Frequency (UHF) Underground Mine Mesh Network for Disaster Response

  • Enabling Description: The "wireless telecommunication network system" (Claims 1, 14, 38, 50) is deployed within an underground mine, where multi-path fading, signal absorption by rock, and dynamic network topology due to shifting environments are extreme challenges. The network operates using ultra-high-frequency (UHF) radio waves (e.g., 400-900 MHz) with mesh routing capabilities. "Latency and jitter sensitive IP-flows" (Claims 1, 14, 38, 50) include voice communication among rescue teams, biometric data from personnel (heart rate, oxygen levels), and remote sensor readings (methane detection). The "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) dynamically re-evaluates channel conditions every few milliseconds, reserving "future slots" (Claim 1) across multiple mesh nodes to ensure reliable, isochronous delivery of emergency data. The "isochronous manner" (Claim 1) must adapt to rapid changes in signal quality caused by moving personnel and equipment, maintaining critical voice and sensor data streams with minimal interruption.
  • Related Claims: Claims 1, 14, 26, 38, 50.
graph TD
    BS[Base Station (Surface)] --> M1[Mesh Node 1 (UHF)];
    M1 --> M2[Mesh Node 2];
    M2 --> M3[Mesh Node 3];
    M3 --> RT[Rescue Team (Wearable Sensors)];
    M2 --> VD[Ventilation Sensor];
    M1 -- Backhaul (Fiber/Coax) --> BS;

    subgraph Underground Network
        M1; M2; M3; RT; VD;
    end
    
    ARP[Advanced Reservation Processor] -- Dynamic Slot Res. --> M1;
    ARP -- Dynamic Slot Res. --> M2;
    ARP -- Dynamic Slot Res. --> M3;
    
    RT -- Biometric Data (IP Flow) --> M3;
    VD -- Methane Data (IP Flow) --> M2;
    M3 -- Emergency Voice (IP Flow) --> M2;
    M2 -- Prioritized Routing --> M1;
    M1 -- Isochronous Delivery --> BS;

3. Cross-Domain Application

Derivative 3.1: Autonomous Agricultural Robot Swarms (AgTech)

  • Enabling Description: In an agricultural setting, a "wireless point to multi-point transmission system" (Claims 38, 50) consists of a central farm controller (base station) and a swarm of autonomous agricultural robots (CPE stations) for planting, monitoring, and harvesting. "Latency and jitter sensitive IP-flows" (Claims 1, 14, 38, 50) include real-time swarm coordination commands (e.g., path planning, collision avoidance), precision spraying instructions, and high-resolution sensor data (e.g., spectral imaging for crop health). The "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) dynamically allocates communication slots for these critical IP flows to ensure synchronized robot movements and immediate response to environmental changes. The "isochronous manner" (Claim 1) of data packet placement is vital for maintaining the coherence of the robot swarm and preventing operational drifts or collisions, especially in diverse terrain.
  • Related Claims: Claims 1, 14, 26, 38, 50.
graph TD
    Farm_Controller[Farm Base Station] --> Wireless_Medium[Wireless Mesh Network];
    Wireless_Medium --> Robot_A[Agricultural Robot A];
    Wireless_Medium --> Robot_B[Agricultural Robot B];
    Wireless_Medium --> Robot_C[Agricultural Robot C];

    FC_QoS[QoS Scheduler (Advanced Reservation Algorithm)] -- Allocates Slots --> Wireless_Medium;

    Robot_A -- Swarm Coordination IP Flow --> FC_QoS;
    Robot_B -- Sensor Data IP Flow --> FC_QoS;
    Robot_C -- Command & Control IP Flow --> FC_QoS;

    FC_QoS -- Isochronous Reservation --> Robot_A;
    FC_QoS -- Isochronous Reservation --> Robot_B;
    FC_QoS -- Isochronous Reservation --> Robot_C;

Derivative 3.2: Air Traffic Control (ATC) System for Drone Delivery Networks (Aerospace)

  • Enabling Description: The "wireless point to multi-point transmission system" (Claims 38, 50) is an Air Traffic Control (ATC) ground station communicating with a fleet of commercial delivery drones (CPE stations). "Latency and jitter sensitive IP-flows" (Claims 1, 14, 38, 50) are highly critical: drone flight path updates, emergency landing commands, collision avoidance warnings, and real-time telemetry (altitude, speed, battery). The "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) is a deterministic scheduling algorithm that guarantees time-critical slots for command and control IP flows over a dedicated drone communication link (e.g., licensed band LTE or custom waveform). The "isochronous manner" (Claim 1) ensures commands reach drones within strict timing windows, vital for flight safety and mission reliability in congested airspace.
  • Related Claims: Claims 1, 14, 26, 38, 50.
graph TD
    ATC_Ground[ATC Ground Station] --> A[Advanced Reservation Algorithm (ATC)];
    A -- Schedule Slots --> Wireless_Link[Dedicated Drone Comm. Link];
    Wireless_Link --> Drone_Fleet[Drone Fleet (CPEs)];
    
    Drone_Fleet -- Telemetry IP Flow --> Wireless_Link;
    Wireless_Link --> A;
    
    A -- Flight Path Updates (Isochronous IP Flow) --> Wireless_Link;
    A -- Emergency Commands (Isochronous IP Flow) --> Wireless_Link;
    
    Wireless_Link -- Receives Data --> Drone_1[Drone 1];
    Wireless_Link -- Receives Data --> Drone_N[Drone N];

Derivative 3.3: High-Frequency Trading (HFT) Network in Financial Markets (Financial Services)

  • Enabling Description: The "wireless telecommunication network system" (Claims 1, 14, 38, 50) connects geographically dispersed high-frequency trading (HFT) servers (host workstations/CPE) to market exchange matching engines (base station) over a private, ultra-low latency microwave or millimeter-wave link. "Latency and jitter sensitive IP-flows" (Claims 1, 14, 38, 50) are order placements, market data feeds, and algorithmic trading signals. The "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) pre-reserves precise nanosecond-scale time slots on the wireless link for these trading messages, ensuring they arrive at the exchange with deterministic and minimal delay. The "isochronous manner" (Claim 1) is paramount for fair and predictable execution of trades, where even microsecond variations can lead to significant financial losses. The system utilizes atomic clocks for precise synchronization across all endpoints.
  • Related Claims: Claims 1, 14, 26, 38, 50.
sequenceDiagram
    participant HFT_Server as HFT Trading Server
    participant BS as Market Exchange BS
    participant ARA as Advanced Reservation Algorithm
    
    HFT_Server->>ARA: Request Reserved Slot for Order (QoS: Ultra-Low Latency)
    ARA->>ARA: Allocate Precise Nanosecond Slot (Future Frame)
    ARA->>BS: Confirm Reservation Schedule
    BS->>HFT_Server: Acknowledge Schedule
    
    loop Trading Session
        HFT_Server->>HFT_Server: Generate Order IP Flow
        HFT_Server->>BS: Transmit Order in Reserved Slot (Isochronous)
        BS->>HFT_Server: Receive Order / Send Confirmation
    end

4. Integration with Emerging Tech

Derivative 4.1: AI-Driven Dynamic QoS Optimization

  • Enabling Description: The "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) is augmented with an Artificial Intelligence (AI) module, specifically a deep reinforcement learning agent. This AI agent continuously monitors network conditions (e.g., bandwidth availability, interference levels, traffic load), current IP flow QoS requirements, and historical performance data. It dynamically adjusts the parameters of the reservation algorithm, such as the size of reserved slots, the frequency of reservations, and the prioritization scheme, in real-time. For "latency and jitter sensitive IP-flows" (Claims 1, 14, 38, 50), the AI can predict transient congestion or signal degradation and proactively re-schedule "future slots" (Claim 1) or adjust modulation and coding schemes to maintain the "isochronous manner" of delivery. The AI's decisions are based on maximizing an objective function combining end-user QoS metrics and network resource utilization.
  • Related Claims: Claims 1, 14, 26, 38, 50.
graph TD
    User_App[User Application (IP Flow)] --> QoS_Req[QoS Requirements];
    QoS_Req --> Flow_Analyzer[Flow Analyzer];
    Network_State[Network State (BER, Congestion)] --> AI_Engine[AI/ML Optimization Engine];
    Historical_Data[Historical Performance Data] --> AI_Engine;
    
    Flow_Analyzer --> ARA[Advanced Reservation Algorithm];
    AI_Engine -- Optimize Parameters --> ARA;
    
    ARA -- Reserve Future Slots --> MAC_Layer[MAC Layer (Wireless)];
    MAC_Layer -- Transmit Isochronous IP --> Wireless_Medium[Wireless Medium];
    
    Wireless_Medium --> CPE[Subscriber CPE];
    CPE --> User_App;
    
    MAC_Layer -- Feedback --> Network_State;

Derivative 4.2: IoT Sensor Network with Real-time Monitoring and Adaptive Reservation

  • Enabling Description: The "telecommunications system" (Claims 38, 50) comprises a wireless base station connected to a cloud platform, and a large number of heterogeneous Internet of Things (IoT) sensors (CPE stations). These sensors generate diverse "IP flows" (Claims 1, 14, 38, 50) including critical alert data (e.g., fire alarm), periodic environmental readings (temperature, humidity), and less time-sensitive firmware updates. Each IoT sensor is equipped with an embedded agent that negotiates its QoS requirements. The "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) continuously monitors the state of individual IoT sensors (e.g., battery level, data buffer status) and ambient radio frequency (RF) conditions. It adaptively reserves "succeeding slots in future transmission frames" (Claim 38) for each sensor's IP flow, ensuring that critical data maintains its "isochronous manner" of delivery (Claim 1), while background data is transmitted opportunistically. This is particularly relevant for Low-Power Wide-Area Networks (LPWANs).
  • Related Claims: Claims 1, 14, 26, 38, 50.
graph TD
    Cloud_Platform[Cloud Platform] -- Aggregates Data --> BS[Wireless Base Station];
    BS -- Controls --> ARA[Advanced Reservation Algorithm (BS)];
    
    IoT_Sensor_1[IoT Sensor 1 (CPE)] -- IP Flow (Critical) --> MAC_1[MAC Agent];
    IoT_Sensor_2[IoT Sensor 2 (CPE)] -- IP Flow (Periodic) --> MAC_2[MAC Agent];
    IoT_Sensor_N[IoT Sensor N (CPE)] -- IP Flow (Background) --> MAC_N[MAC Agent];
    
    MAC_1 -- QoS Request/Status --> ARA;
    MAC_2 -- QoS Request/Status --> ARA;
    MAC_N -- QoS Request/Status --> ARA;
    
    ARA -- Reserve Slots (Isochronous) --> Wireless_Link[LPWAN Wireless Link];
    Wireless_Link --> BS;
    
    ARA -- Adaptive Adjustments --> MAC_1;
    ARA -- Adaptive Adjustments --> MAC_2;
    ARA -- Adaptive Adjustments --> MAC_N;

Derivative 4.3: Blockchain for Verifiable QoS and SLA Enforcement

  • Enabling Description: To ensure transparency and immutability in "service level agreements (SLAs)" (as mentioned in the patent background) and the "optimizing end-user quality of service (QoS)" (Claim 38), a blockchain ledger is integrated into the "telecommunications system" (Claims 38, 50). Each "reservation of succeeding slots in one or more succeeding future transmission frames" (Claim 38) made by the "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) is recorded as a transaction on a distributed ledger. Upon successful transmission and reception of an "isochronous data packet" (Claim 38), a corresponding proof-of-delivery or successful slot utilization is also recorded. Smart contracts on the blockchain automatically verify QoS metrics (latency, jitter compliance) against the established SLAs. This allows for immutable auditing of network performance and automated billing or penalties based on verifiable QoS delivery, enhancing trust among network service providers and subscribers.
  • Related Claims: Claims 1, 14, 26, 38, 50.
sequenceDiagram
    participant Subscriber as Subscriber (CPE)
    participant BS as Wireless Base Station
    participant ARA as Advanced Reservation Algorithm
    participant Blockchain as Distributed Ledger (QoS Chain)
    participant Smart_Contract as SLA Smart Contract

    Subscriber->>BS: Initiate IP Flow (e.g., VoIP)
    BS->>ARA: Request Isochronous Reservation (QoS Parameters)
    ARA->>ARA: Determine Slot Allocation
    ARA->>Blockchain: Record "Slot Reservation Grant" (TxID_1)
    Blockchain->>BS: Confirmation of TxID_1
    BS->>Subscriber: Acknowledge Reservation

    loop Each Isochronous Packet Transmission
        BS->>BS: Packet Transmitted in Reserved Slot
        BS->>Blockchain: Record "Packet Tx/Rx Confirmation" (TxID_2)
        Blockchain->>Smart_Contract: Event: New TxID_2
        Smart_Contract->>Smart_Contract: Verify QoS against SLA (e.g., Latency < X ms, Jitter < Y ms)
        Smart_Contract->>Blockchain: Record "SLA Compliance Status" (TxID_3)
    end
    Blockchain->>Subscriber: (Optional) Notifies of SLA Compliance

5. The "Inverse" or Failure Mode

Derivative 5.1: Graceful Degradation of QoS under Congestion

  • Enabling Description: When the "wireless telecommunication network system" (Claims 1, 14, 38, 50) experiences severe congestion or high Bit Error Rate (BER) that prevents guaranteed "isochronous" delivery (Claim 1) for all "latency and jitter sensitive IP-flows" (Claims 1, 14, 38, 50), the "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) enters a graceful degradation mode. Instead of outright dropping packets or denying service, it dynamically renegotiates QoS parameters with applications or users. For example, it might reduce the video bitrate for video calls (e.g., from 720p to 480p), decrease the audio sampling rate for voice calls (e.g., from G.711 to G.729), or increase the acceptable jitter buffer size, thereby maintaining connectivity and a reduced, but still functional, "isochronous-like" experience for more users, rather than disconnecting high-priority users.
  • Related Claims: Claims 1, 14, 26, 38, 50.
stateDiagram
    [*] --> Normal_Operation
    Normal_Operation --> Congestion_Detected: High BER / Low Bandwidth
    Congestion_Detected --> Graceful_Degradation_Mode
    Graceful_Degradation_Mode --> Negotiate_QoS_Parameters: Re-evaluate IP Flow Needs
    Negotiate_QoS_Parameters --> Adjust_Reservation_Algorithm: Reduce Bitrate, Increase Jitter Buffer
    Adjust_Reservation_Algorithm --> Normal_Operation: Congestion Cleared / Adapted
    Graceful_Degradation_Mode --> Emergency_Mode: Critical System Failure
    Emergency_Mode --> Prioritize_Life_Safety: Suspend Non-Essential Flows
    
    state Normal_Operation {
        ARA_Full_QoS
    }
    state Graceful_Degradation_Mode {
        ARA_Adapted_QoS
    }

Derivative 5.2: Low-Power, Limited-Functionality Mode for Remote CPE

  • Enabling Description: The "subscriber customer premise equipment (CPE) stations" (Claims 38, 50) are designed to operate in remote locations with limited power. The "resource allocation means" (Claims 38, 50) and the "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) incorporate a low-power mode. When no "latency and jitter sensitive IP-flows" are active, or when battery levels fall below a threshold, the CPE and portions of the base station scheduler enter a sleep state. It periodically wakes up to check for scheduled "future transmission frames" (Claim 1) for minimal heartbeat or critical low-bandwidth IP flows. The "isochronous manner" (Claim 1) of packet delivery is then applied only during these brief, scheduled wake cycles or upon detection of a high-priority event, thereby significantly extending the operational life of the battery-powered CPE.
  • Related Claims: Claims 1, 14, 26, 38, 50.
stateDiagram
    [*] --> Active_Mode
    Active_Mode --> Low_Power_Mode: No Latency-Sensitive Flow OR Low Battery
    Low_Power_Mode --> Sleep_State
    Sleep_State --> Periodic_Wakeup: Scheduled Check
    Periodic_Wakeup --> Active_Mode: High-Priority Event Detected OR Scheduled Active Period
    Active_Mode --> Active_Mode: Isochronous IP Flow Processing
    
    state Active_Mode {
        QoS_Scheduler_Full
        Wireless_Transceiver_Full_Power
    }
    state Low_Power_Mode {
        QoS_Scheduler_Reduced
        Wireless_Transceiver_Sleep
    }

Derivative 5.3: Fail-Safe Isolation for Critical IP Flows

  • Enabling Description: In a "wireless telecommunication network system" (Claims 1, 14, 38, 50) handling mission-critical "latency and jitter sensitive IP-flows" (Claims 1, 14, 38, 50), the "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) includes a fail-safe isolation mechanism. In the event of detected failure (e.g., loss of primary channel, severe interference exceeding correction capabilities), the system automatically designates a dedicated, pre-allocated emergency channel (e.g., a narrow band, robustly modulated link) for specific, highest-priority IP flows. All other IP flows are immediately suspended or severely deprioritized. The "isochronous manner" (Claim 1) of delivery is maintained for these critical flows by switching to a more resilient, albeit lower-bandwidth, modulation and coding scheme, and utilizing aggressive Forward Error Correction (FEC) and retransmission policies within the pre-reserved emergency slots, ensuring essential communication persists even if general network functionality degrades.
  • Related Claims: Claims 1, 14, 26, 38, 50.
graph TD
    Primary_Network[Primary Wireless Network]
    Emergency_Channel[Dedicated Emergency Channel]
    IP_Flow_Critical[Critical IP Flow]
    IP_Flow_Normal[Normal IP Flow]
    ARA[Advanced Reservation Algorithm]
    Failure_Detector[Network Failure Detector]

    IP_Flow_Critical --> ARA
    IP_Flow_Normal --> ARA

    ARA -- Normal Scheduling --> Primary_Network
    Primary_Network -- Detected Failure --> Failure_Detector
    Failure_Detector -- Trigger --> ARA

    ARA -- Switch to Fail-Safe --> Emergency_Channel
    Emergency_Channel -- Robust Isochronous Tx --> IP_Flow_Critical

    ARA -- Suspend/Deprioritize --> IP_Flow_Normal

Combination Prior Art Scenarios with Open-Source Standards

These scenarios illustrate how the concepts of US Patent 6,628,629 could be combined with widely adopted open-source standards to demonstrate obviousness or lack of novelty for derivative inventions.

Combination 1: US 6,628,629 + IEEE 802.11e (Wi-Fi Multimedia - WMM)

  • Description: The "advanced reservation algorithm" and its application for providing "isochronous data packets" for "latency and jitter sensitive IP-flows" (Claims 1, 14, 26, 38, 50) within a wireless PtMP system are combined with the Quality of Service (QoS) mechanisms defined in the IEEE 802.11e standard (now integrated into 802.11-2007 and later Wi-Fi standards as Wi-Fi Multimedia, WMM). 802.11e introduces Traffic Categories (TCs) and Enhanced Distributed Channel Access (EDCA) to differentiate traffic and provide prioritized access to the wireless medium for real-time applications (e.g., voice, video). A system could explicitly leverage 802.11e's Transmission Opportunity (TXOP) mechanism to implement "future slot reservations." The "advanced reservation algorithm" would inform the duration and periodicity of TXOPs granted to stations for isochronous IP flows, effectively implementing the patent's core idea within the established Wi-Fi QoS framework. The 802.11e standard (e.g., as part of the Linux wireless drivers or open-source access point firmware) serves as an existing open-source implementation.
  • Relevance: Demonstrates the application of reservation-based QoS for latency-sensitive IP flows within a widely adopted, open-source wireless local area network (WLAN) standard. The "advanced reservation algorithm" could be seen as an enhancement or specific implementation of 802.11e's scheduling and prioritization capabilities for isochronous traffic.

Combination 2: US 6,628,629 + Message Queuing Telemetry Transport (MQTT) over an Open-Source LoRaWAN Stack

  • Description: The "telecommunications system" (Claims 38, 50) is a Low-Power Wide-Area Network (LPWAN) utilizing an open-source LoRaWAN stack (e.g., ChirpStack, The Things Network client). "Latency and jitter sensitive IP-flows" (Claims 1, 14, 38, 50) are represented by MQTT messages from IoT sensors, where certain topics (e.g., "emergency/alert") are critical and require guaranteed delivery within strict timing. The "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) is implemented at the LoRaWAN gateway (base station) to pre-allocate uplink and downlink transmission windows (e.g., Class B/C device slots) for MQTT messages with specific QoS levels. For critical MQTT flows, the algorithm reserves "succeeding slots in future transmission frames" (Claim 38) to ensure their "isochronous manner" of delivery, even over the typically sporadic LoRaWAN medium. Open-source MQTT brokers (e.g., Mosquitto) and client libraries provide the IP flow generation and consumption.
  • Relevance: Shows how the patent's concepts of reserving future slots for isochronous, latency-sensitive IP flows can be applied to an IoT context using popular open-source LPWAN and messaging protocols.

Combination 3: US 6,628,629 + Session Initiation Protocol (SIP) with RTP over FreeSWITCH (Open-Source VoIP)

  • Description: The "wireless telecommunication network system" (Claims 1, 14, 38, 50) utilizes an open-source Voice over IP (VoIP) platform like FreeSWITCH (acting as a host workstation/server managing IP flows). When a "latency and jitter sensitive IP-flow" (voice data conveyed via Real-time Transport Protocol, RTP) is initiated or negotiated via Session Initiation Protocol (SIP) signaling, the "advanced reservation algorithm" (Claims 1, 14, 26, 38, 50) at the wireless base station is dynamically invoked. The SIP session parameters (e.g., codec, bandwidth requirements) are extracted to inform the reservation algorithm. The algorithm then reserves "succeeding slots in one or more succeeding future transmission frames" (Claim 38) for the RTP stream in an "isochronous manner" (Claim 1), ensuring high-quality voice communication over the wireless link. The FreeSWITCH server, along with open-source SIP phones (e.g., Linphone, Asterisk-based endpoints) acts as the source and destination for these IP flows.
  • Relevance: Direct integration of the patent's core reservation concepts with widely used open-source VoIP signaling and media transport protocols, demonstrating obviousness for implementing QoS for voice-over-IP.

Generated 5/28/2026, 5:40:28 AM