Patent 9320041

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

The USPTO search results confirm the existence of "Patent Public Search" tools. I can use these to find the patent information. I need to go to Patent Public Search and enter "9320041" into the patent number search field. The search results from the initial Google Patents link provided in the prompt already contained specific details (publication number, application number, priority date, filing date, legal status, adjusted expiration, assignee, inventor, related applications) [cite: patent]. Therefore, for the purpose of this analysis, the Google Patents information is sufficient and already authoritative. No contradictions were found with a general search for "USPTO patent 9320041". I will proceed with generating the defensive disclosure based on the provided patent text.

Defensive Disclosure for US Patent 9,320,041

This document outlines derivative variations of the technologies described in US Patent 9,320,041, aiming to proactively establish prior art that could render future incremental improvements by competitors obvious or non-novel. The focus is on expanding the claims' scope through various technical axes.

Derivative Variations for Claim 1 (Method for Activating Carrier Aggregation)

Claim 1 describes a method for activating carrier aggregation (CA) by determining SCC availability, required resources (L_add), available PCC resources (L_avail), their ratio (β = L_add / L_avail), and activating CA if an activation condition related to this ratio is satisfied.

1.1 Material & Component Substitution: Reconfigurable Intelligent Surface (RIS) Based Carrier Management

Enabling Description:
Instead of a traditional base station (eNB) with fixed antenna arrays, the method is implemented within a distributed radio access network (DRAN) where the "base station" functionality is partially offloaded to intelligent network controllers coordinating multiple Reconfigurable Intelligent Surfaces (RISs). Each RIS comprises an array of passive or semi-passive metasurface elements, each element capable of independently adjusting its phase shift, amplitude, or polarization to dynamically steer and shape wireless signals. The "determining whether any secondary component carrier is available" involves active probing or passive sensing by RIS panels, which can adapt their reflective properties to enhance signal propagation for potential SCCs. The "first communication device" (UE) utilizes advanced multi-antenna (e.g., Massive MIMO or holographic beamforming) transceivers capable of coordinating with RISs. The "first value" (L_add) is determined by the UE's application-layer data queue depth, reported via enhanced buffer status reports (eBSRs) that include quality of service (QoS) requirements. The "second value" (L_avail) is calculated by the RIS controller based on real-time channel state information (CSI) obtained through pilots and sounding reference signals (SRSs) from the UE and adjacent cells, specifically evaluating the residual capacity of the PCC as perceived through the RIS-manipulated channel. The ratio β is computed at the RIS controller or a centralized orchestrator, which then directs specific RIS elements to enable/enhance an SCC for the UE if α·β > C_activate, where α reflects RIS-mediated SCC availability and C_activate is dynamically adjusted based on RIS power consumption profiles.

graph TD
    A[UE with eBSR] --> B{RIS Controller/Orchestrator};
    B --> C{Determine SCC Availability (α)};
    B --> D{Determine L_add (from eBSR)};
    B --> E{Determine L_avail (from RIS CSI)};
    C & D & E --> F{Calculate Ratio β = L_add / L_avail};
    F --> G{Evaluate Activation Condition α·β > C_activate?};
    G -- Yes --> H[Activate/Enhance SCC via RIS Control];
    H --> I[UE Transmits on PCC + RIS-enhanced SCC];
    G -- No --> J[Maintain PCC-only or Defer];

1.2 Operational Parameter Expansion: Ultra-Wideband (UWB) and Millimeter-Wave (mmWave) Integration with Adaptive Beamforming

Enabling Description:
This variation applies the method to communication devices operating across ultra-wideband (UWB) spectrum (3.1 GHz to 10.6 GHz) for short-range, high-precision localization and data transfer, and millimeter-wave (mmWave) spectrum (24 GHz to 100 GHz) for high-bandwidth data links. The "first component carrier" (PCC) is dynamically assigned from either the UWB or mmWave band based on immediate link quality and latency requirements. SCCs are drawn from the other band or additional narrower mmWave channels. "Determining SCC availability" involves continuous beam sweeping and channel sounding in both UWB and mmWave bands using phased array antennas at the communication device and base station, establishing potential line-of-sight (LOS) or non-LOS paths. L_add (first value) is derived from instantaneous data burst sizes in a time-critical industrial control loop, while L_avail (second value) on the PCC is assessed by monitoring effective isotropic radiated power (EIRP) margins and instantaneous spectral efficiency across the highly directional mmWave beams or UWB pulses. The ratio β is evaluated, and if the activation condition (α·β > C_activate) is met, the system activates an SCC by switching the UE's transceiver to a different frequency band (e.g., from UWB PCC to mmWave PCC with UWB SCC, or vice-versa) or adding a new mmWave component carrier using spatial multiplexing with adaptive beamforming steering. This requires sub-millisecond switching times and dynamic beamforming algorithm adjustments.

stateDiagram-v2
    state "PCC_UWB_ACTIVE" as UWB_A
    state "PCC_MMWAVE_ACTIVE" as MMW_A
    state "CA_UWB_MMWAVE_ACTIVE" as CA_UM_A
    state "CA_MMWAVE_UWB_ACTIVE" as CA_MU_A

    [*] --> UWB_A : Initial State
    [*] --> MMW_A : Initial State

    UWB_A --> CA_UM_A : α·β > C_activate (mmWave SCC available)
    MMW_A --> CA_MU_A : α·β > C_activate (UWB SCC available)

    CA_UM_A --> CA_UM_A : L_add/L_avail updates, CA active
    CA_MU_A --> CA_MU_A : L_add/L_avail updates, CA active

    CA_UM_A --> UWB_A : α·β < C_release (mmWave SCC no longer needed)
    CA_MU_A --> MMW_A : α·β < C_release (UWB SCC no longer needed)

    MMW_A --> UWB_A : PCC re-selection (e.g., severe mmWave blockage)
    UWB_A --> MMW_A : PCC re-selection (e.g., high-throughput demand)

1.3 Cross-Domain Application 1: Autonomous Vehicle (AV) Sensor Data Offloading

Enabling Description:
In an autonomous vehicle (AV) communication network, the "first communication device" is an AV that continuously generates high-volume sensor data (LiDAR, camera, radar) requiring offloading to a roadside unit (RSU) or centralized processing unit. The "first component carrier" (PCC) is a dedicated V2X (Vehicle-to-Everything) channel (e.g., IEEE 802.11p or 5G NR-V2X sidelink). "Determining SCC availability" involves the RSU assessing adjacent cellular or Wi-Fi access points that can serve as secondary component carriers (SCCs) for the AV, considering their current load and backhaul capacity. The "first value" (L_add) represents the accumulated sensor data buffer depth within the AV, indicative of pending data offload. The "second value" (L_avail) is the remaining available bandwidth on the V2X PCC, considering existing safety-critical message traffic. The ratio β and activation condition α·β > C_activate trigger the RSU to activate CA, enabling the AV to utilize an additional cellular or Wi-Fi SCC for bulk sensor data offloading, reducing latency for critical processing.

graph LR
    A[Autonomous Vehicle] -- High Sensor Data Rate --> B(AV Data Buffer);
    B --> C{Determine L_add (Buffer Depth)};
    A -- V2X PCC Link --> D{RSU / eNB};
    D -- Assess PCC Capacity --> E{Determine L_avail (PCC)};
    D -- Scan Adjacent APs --> F{Determine SCC Availability (α)};
    C & E & F --> G{Calculate β = L_add / L_avail};
    G --> H{Check Activation Condition α·β > C_activate?};
    H -- Yes --> I[Activate Cellular/Wi-Fi SCC for AV];
    H -- No --> J[Continue V2X PCC only];

1.4 Cross-Domain Application 2: Remote Surgery and Tele-Rehabilitation Systems

Enabling Description:
In remote surgery and tele-rehabilitation systems, the "first communication device" is a robotic surgical arm or a haptic feedback device at a remote location, controlled by a surgeon or therapist. The "first component carrier" (PCC) is a primary low-latency, high-reliability connection (e.g., dedicated fiber optic link or ultra-reliable low-latency communication (URLLC) over 5G). "Determining SCC availability" involves a network controller assessing alternative high-bandwidth wireless (e.g., mmWave, satellite) or wired (e.g., secondary fiber, DSL) connections that can serve as SCCs. The "first value" (L_add) is determined by the instantaneous data rate of high-definition video feeds, haptic sensor data, and control commands required for surgical precision or real-time rehabilitation. The "second value" (L_avail) is the current unused capacity on the primary URLLC PCC. The ratio β is computed, and if α·β > C_activate (e.g., indicating potential latency spikes or data backlog on PCC), the system activates CA, establishing a redundant or supplementary SCC to ensure uninterrupted, high-fidelity data flow, crucial for patient safety and operational integrity.

sequenceDiagram
    participant Robot_Device as Remote Surgical/Rehab Device
    participant Network_Ctrl as Network Controller (Base Station/Central Office)
    participant Surgeon_Console as Surgeon/Therapist Console (PCC endpoint)

    Surgeon_Console -->> Network_Ctrl: Transmit Control Commands/Video (PCC Traffic)
    Robot_Device -->> Network_Ctrl: Transmit Haptic Feedback/Video (PCC Traffic)

    activate Network_Ctrl
    Network_Ctrl->>Network_Ctrl: Determine L_add (Robot/Console buffer depth)
    Network_Ctrl->>Network_Ctrl: Determine L_avail (PCC capacity)
    Network_Ctrl->>Network_Ctrl: Determine SCC Availability (α)
    Network_Ctrl->>Network_Ctrl: Calculate Ratio β = L_add / L_avail
    Network_Ctrl->>Network_Ctrl: Check Activation Condition (α·β > C_activate)
    alt Activation Condition Met
        Network_Ctrl->>Network_Ctrl: Identify 2nd Component Carrier
        Network_Ctrl-->>Robot_Device: Activate SCC
        Network_Ctrl-->>Surgeon_Console: Activate SCC
        Robot_Device-->>Network_Ctrl: Transmit on PCC + SCC
        Surgeon_Console-->>Network_Ctrl: Transmit on PCC + SCC
    else Activation Condition Not Met
        Network_Ctrl->>Robot_Device: Continue PCC-only
        Network_Ctrl->>Surgeon_Console: Continue PCC-only
    end
    deactivate Network_Ctrl

1.5 Cross-Domain Application 3: High-Resolution Earth Observation Satellite Downlink

Enabling Description:
For high-resolution Earth observation satellites, the "first communication device" is a Low Earth Orbit (LEO) or Medium Earth Orbit (MEO) satellite, and the "first component carrier" (PCC) is a primary S-band or X-band downlink channel to a ground station. "Determining SCC availability" involves the ground station network coordinating with adjacent ground stations or inter-satellite optical links that can serve as SCCs. The "first value" (L_add) is the accumulated buffer of raw high-resolution imagery and scientific data on the satellite, awaiting downlink. The "second value" (L_avail) is the current available capacity on the primary X-band downlink, considering weather conditions and interference. The ratio β is computed, and if α·β > C_activate (indicating a backlog of data due to limited contact time or poor primary link conditions), the ground station network activates CA. This involves instructing the satellite to simultaneously transmit on an additional Ka-band or optical SCC to another ground station or relay satellite, maximizing data throughput during short communication windows.

graph TD
    A[LEO/MEO Satellite] -- High-Res Data Generation --> B(Satellite Data Buffer);
    B --> C{Determine L_add (Buffer Depth)};
    A -- Primary X-band Downlink (PCC) --> D{Ground Station 1};
    D -- Assess PCC Link Quality --> E{Determine L_avail (PCC)};
    D -- Coordinate with Network --> F{Determine SCC Availability (α) (e.g., GS2, Optical Link)};
    C & E & F --> G{Calculate β = L_add / L_avail};
    G --> H{Check Activation Condition α·β > C_activate?};
    H -- Yes --> I[Activate Ka-band/Optical SCC to GS2/Relay];
    I --> J[Satellite Transmits on PCC + SCCs];
    H -- No --> K[Continue X-band PCC only];

1.6 Integration with Emerging Tech 1: AI-Driven Predictive CA Optimization

Enabling Description:
The method for activating carrier aggregation is enhanced by an AI-driven predictive optimization module integrated into the base station's scheduler. The "determining" steps (SCC availability, L_add, L_avail, ratio) feed into a Machine Learning (ML) model, specifically a Recurrent Neural Network (RNN) or Transformer-based model, that learns historical traffic patterns, user mobility, QoS requirements, and environmental factors (e.g., weather impacting mmWave links). This ML model dynamically predicts future transmission needs and SCC availability, adjusting the activation threshold value (C_activate) and potentially the ratio calculation. Instead of a static C_activate, the AI model outputs a probabilistic activation score. If this score exceeds a learned confidence threshold, and α·β satisfies a predicted condition, CA is activated. The system uses reinforcement learning (RL) to continuously refine the ML model, where "rewards" are assigned for successful CA activations that minimize latency and maximize throughput while penalizing unnecessary activations or late activations. The RL agent observes the outcome of previous CA decisions and adjusts its policy for threshold setting and SCC selection.

graph TD
    A[UE Traffic/Buffer Info (L_add)] --> B{Base Station Scheduler};
    C[PCC Resource Avail (L_avail)] --> B;
    D[SCC Availability (α)] --> B;
    B --> E[Real-time Feature Extractor];
    E --> F(AI/ML Predictive Model);
    F -- Predict future L_add, L_avail, SCC availability --> G{Dynamic C_activate Adjustment};
    G --> H{Calculate β = L_add / L_avail};
    H & G --> I{Check Activation Condition α·β > Dynamic_C_activate?};
    I -- Yes --> J[Activate SCCs];
    I -- No --> K[Maintain PCC-only];
    J --> L[Network Performance Metrics (Reward Signal)];
    K --> L;
    L --> F;

1.7 Integration with Emerging Tech 2: IoT Sensor-Triggered Edge-Coordinated CA

Enabling Description:
In a dense IoT deployment, the "first communication device" is a high-volume data-generating IoT gateway aggregating data from numerous sensors (e.g., smart city infrastructure). The "base station" functionality is distributed among multiple edge computing nodes (ECNs) that form a local compute and communication cluster. "Determining SCC availability" involves the ECNs receiving real-time telemetry from neighboring ECNs via a low-latency backhaul, indicating the load and available capacity of their managed component carriers. The "first value" (L_add) is derived from aggregated buffer states of all connected IoT sensors within the gateway, reflecting collective data backlog. The "second value" (L_avail) is the available radio resource blocks (RBs) on the IoT gateway's primary component carrier to its serving ECN. The unique aspect is that specific "critical event" triggers from IoT sensors (e.g., fire alarm, infrastructure fault detection) bypass the standard buffer-depth L_add calculation and immediately elevate the perceived L_add to a maximum, forcing an urgent CA activation. The ratio β is still computed but in critical scenarios, C_activate is dynamically lowered to near zero. Activation decisions are orchestrated by an edge orchestrator, which ensures only one SCC is activated at a time, minimizing interference within the dense IoT cluster.

graph TD
    A[IoT Sensors] -- Data --> B(IoT Gateway);
    B -- Aggregated Buffer State --> C{Edge Computing Node (ECN) 1};
    C -- Local PCC Allocation --> D{Determine L_avail (PCC)};
    E[Neighbor ECNs] -- Telemetry --> F{Edge Orchestrator};
    F --> G{Determine SCC Availability (α)};
    C -- IoT Critical Event Trigger --> H[Override L_add to Max];
    C -- Normal L_add --> I{Determine L_add (Buffer Depth)};
    H & I --> J(L_add);
    J & D & G --> K{Calculate β = L_add / L_avail};
    K --> L{Check Activation Condition α·β > C_activate?};
    L -- Yes --> M[Activate SCC via Edge Orchestrator];
    M --> N[IoT Gateway Transmits on PCC + SCC];
    L -- No --> O[Continue PCC only];

1.8 Integration with Emerging Tech 3: Blockchain-Validated Dynamic Spectrum Access for CA

Enabling Description:
This method integrates blockchain technology for transparent and auditable dynamic spectrum access (DSA) in activating carrier aggregation. The "first communication device" (UE) requests spectrum resources. The "base station" acts as a blockchain node. "Determining SCC availability" involves querying a decentralized ledger (blockchain) that records current spectrum usage rights and availability for potential SCCs, rather than relying solely on local measurements. Each spectrum block or component carrier is tokenized as a non-fungible token (NFT) or a fungible token representing usage rights. The "first value" (L_add) is reported by the UE and signed by its private key, and validated on-chain to prevent fraudulent requests. The "second value" (L_avail) is determined by the base station, which commits its PCC resource allocation decisions to the blockchain for transparency. The ratio β is computed, and the activation condition (α·β > C_activate) triggers a smart contract execution on the blockchain. This smart contract automatically proposes and validates the allocation of a tokenized SCC to the UE, ensuring that the allocation adheres to predefined rules (e.g., no double-spending of spectrum, priority for emergency services, fair market pricing for spectrum). Once validated by the network's consensus mechanism (e.g., Proof of Stake by other base stations), the SCC is activated.

sequenceDiagram
    participant UE
    participant Base_Station as Base Station (Blockchain Node)
    participant Blockchain
    participant Smart_Contract as Spectrum Allocation Smart Contract

    UE->>Base_Station: Data Request / Signed L_add
    Base_Station->>Base_Station: Determine L_avail (PCC)
    Base_Station->>Blockchain: Query SCC Availability/Spectrum Tokens (α)
    Blockchain-->>Base_Station: Return Available Tokenized SCCs
    Base_Station->>Base_Station: Calculate β = L_add / L_avail
    Base_Station->>Smart_Contract: Trigger Activation Condition (α·β > C_activate)
    Smart_Contract->>Blockchain: Propose SCC Allocation Transaction
    Blockchain->>Blockchain: Validate Transaction (Consensus)
    Blockchain-->>Smart_Contract: Transaction Confirmed
    Smart_Contract-->>Base_Station: Grant SCC Access
    Base_Station->>UE: Activate SCC
    UE->>Base_Station: Transmit on PCC + SCC (Validated)

1.9 The "Inverse" / Failure Mode: Energy-Harvesting Device CA with Minimum Power Activation

Enabling Description:
This derivative describes a system optimized for extreme low-power, energy-harvesting "first communication devices" (e.g., environmental sensors, agricultural monitors) where CA activation is minimized to conserve harvested energy. The "first component carrier" (PCC) is a narrow-band low-power wide-area (LPWA) channel (e.g., NB-IoT, LoRa). "Determining SCC availability" factors in the instantaneous energy level of the energy harvesting device. A potential SCC is typically another LPWA channel or a short-range unlicensed band, activated only under specific conditions. The "first value" (L_add) is the accumulated critical sensor data, but its weight in the ratio is dynamically scaled down if the device's harvested energy buffer is below a critical threshold. The "second value" (L_avail) is the maximum possible transmit power budget on the PCC given current harvested energy. The activation condition (α·β > C_activate) is heavily biased towards energy availability: C_activate itself is dynamically adjusted upwards with decreasing available energy. CA is only activated if both high data need and sufficient harvested energy exist, enabling a brief burst on an SCC (e.g., a slightly wider band LPWA channel or a brief Wi-Fi burst) before immediately releasing it, minimizing power drain. If energy levels are critical, CA activation is suppressed entirely, regardless of L_add, prioritizing basic PCC functionality.

stateDiagram-v2
    state "PCC_LPWA_Idle" as PCC_Idle
    state "PCC_LPWA_Active" as PCC_Active
    state "CA_LPWA_Burst" as CA_Burst
    state "Energy_Critical" as E_Crit

    [*] --> PCC_Idle

    PCC_Idle --> PCC_Active : Data Available
    PCC_Active --> PCC_Idle : Data Transmitted / Timeout

    PCC_Active --> CA_Burst : α·β > C_activate_mod AND Energy > Min_CA_Energy
    CA_Burst --> PCC_Active : Data Burst Complete / Energy < Min_CA_Energy

    PCC_Idle --> E_Crit : Energy < Critical_Threshold
    PCC_Active --> E_Crit : Energy < Critical_Threshold
    CA_Burst --> E_Crit : Energy < Critical_Threshold

    E_Crit --> PCC_Idle : Energy Recovered
    E_Crit --> E_Crit : CA Blocked / Minimum Functionality

Derivative Variations for Claim 8 (Method for Releasing Carrier Aggregation)

Claim 8 describes a method for releasing CA by determining required resources (L_add), available PCC resources (L_avail), their ratio (β), and releasing CA if a release condition related to this ratio is satisfied.

2.1 Material & Component Substitution: Optical Wireless Communication (OWC) in Data Centers

Enabling Description:
In a high-density data center environment, the "first communication device" is a server rack or network switch utilizing optical wireless communication (OWC, also known as Free-Space Optical or FSO) for inter-rack or intra-data center connectivity. The "first component carrier" (PCC) is a primary OWC link using a specific laser wavelength (e.g., 850 nm VCSEL arrays). The "second component carrier" (SCC) is a secondary OWC link using a different wavelength (e.g., 1550 nm DFB lasers) or a modulated infrared light-emitting diode (LED) link. "Determining a first value" (L_add) involves monitoring the egress data queue depth of the server rack. "Determining a second value" (L_avail) on the PCC involves real-time monitoring of the primary OWC link's signal-to-noise ratio (SNR), beam alignment precision, and error rate, which directly impacts its effective throughput. The ratio β is computed. If the release condition (α·β < C_release) is met, indicating sufficient primary OWC capacity or the SCC becoming unstable (α=0, e.g., due to temporary beam misalignment or dust particles affecting the secondary link), the CA is released. This involves deactivating the secondary OWC laser/LED and re-routing all traffic to the primary OWC link, conserving power and reducing optical interference.

graph TD
    A[Server Rack/Network Switch] -- Egress Data Queue --> B{Determine L_add};
    C[Primary OWC Link (PCC)] -- Link Metrics (SNR, BER) --> D{Determine L_avail (PCC)};
    E[Secondary OWC Link (SCC)] -- Link Status/Quality --> F{Determine SCC Availability (α)};
    B & D & F --> G{Calculate β = L_add / L_avail};
    G --> H{Check Release Condition α·β < C_release?};
    H -- Yes --> I[Deactivate Secondary OWC Link (Release CA)];
    I --> J[Traffic on Primary OWC Link Only];
    H -- No --> K[Continue PCC + SCC OWC Links];

2.2 Operational Parameter Expansion: Extreme Temperature and Radiation Environments (e.g., Nuclear Facilities, Deep Space)

Enabling Description:
This method is adapted for communication devices operating in extreme environments, such as nuclear reactor facilities or deep space probes, where wireless links are subject to high temperatures (e.g., 200°C+), radiation, and electromagnetic interference (EMI). The "first communication device" is a robotic inspection unit or a sensor node within these environments. The "first component carrier" (PCC) is a robust, low-bandwidth, frequency-hopping spread spectrum (FHSS) link designed for resilience. The "second component carrier" (SCC) is a higher-bandwidth, but more sensitive, direct-sequence spread spectrum (DSSS) or OFDM link. "Determining a first value" (L_add) involves monitoring the telemetry and diagnostic data buffer of the robotic unit. "Determining a second value" (L_avail) on the PCC factors in real-time degradation of antenna performance due to radiation damage, noise floor increases from temperature, and error rates, which directly diminish usable PCC capacity. The ratio β is computed. If the release condition (α·β < C_release) is met, or if the SCC's link quality drops below a radiation-induced error threshold (α=0 for SCC), CA is released. This prioritizes the ultra-reliable FHSS PCC link, even if slower, to ensure critical data transmission under hazardous conditions, and deactivates the more fragile SCC to prevent further energy waste or generation of erroneous data.

stateDiagram-v2
    state "CA_Active_Extreme_Env" as CA_AE
    state "PCC_Only_Resilient" as PCC_R

    [*] --> CA_AE : Initial CA Active
    CA_AE --> CA_AE : L_add/L_avail updates, CA active

    CA_AE --> PCC_R : α·β < C_release OR SCC_Link_Degraded_by_Env
    PCC_R --> PCC_R : PCC only, monitoring env. conditions

    PCC_R --> CA_AE : α·β > C_activate AND SCC_Link_Stable_for_Env

2.3 Cross-Domain Application 1: Smart Agriculture Sensor Networks

Enabling Description:
In smart agriculture, the "first communication device" is a field sensor hub collecting data (soil moisture, temperature, nutrient levels) from numerous distributed sensors across a large farm. The "first component carrier" (PCC) is a long-range, low-power LoRaWAN or NB-IoT link to a central gateway. The "second component carrier" (SCC) is a local Wi-Fi HaLow or Zigbee link, used for higher-bandwidth data bursts (e.g., detailed imagery from a drone landing near the hub, or firmware updates). "Determining a first value" (L_add) is the accumulated sensor data buffer at the hub. "Determining a second value" (L_avail) on the LoRaWAN/NB-IoT PCC accounts for varying environmental factors like crop density, weather interference, and gateway load. The ratio β is computed. If the release condition (α·β < C_release) is met (e.g., all high-bandwidth drone data transmitted, only routine sensor data remains) or the SCC becomes unreachable (α=0, e.g., drone flies away or local Wi-Fi AP powers down), CA is released. The hub then reverts to transmitting solely via the energy-efficient LoRaWAN/NB-IoT PCC, conserving power for extended field deployment.

graph LR
    A[Field Sensor Hub] -- Accumulated Data --> B(Data Buffer L_add);
    C[LoRaWAN/NB-IoT PCC] -- Link Quality/Avail --> D{Determine L_avail (PCC)};
    E[Wi-Fi HaLow/Zigbee SCC] -- Status/Reachability --> F{Determine SCC Avail (α)};
    B & D & F --> G{Calculate β = L_add / L_avail};
    G --> H{Check Release Condition α·β < C_release?};
    H -- Yes --> I[Deactivate SCC (Release CA)];
    I --> J[Hub Transmits on LoRaWAN/NB-IoT PCC only];
    H -- No --> K[Continue PCC + SCC];

2.4 Cross-Domain Application 2: Maritime IoT and Offshore Platform Communications

Enabling Description:
For maritime IoT and offshore platforms, the "first communication device" is a buoy or an offshore sensor array transmitting environmental data (ocean currents, weather, seismic activity). The "first component carrier" (PCC) is a reliable but low-bandwidth satellite link (e.g., Iridium, Inmarsat C) for critical data. The "second component carrier" (SCC) is a higher-bandwidth, but line-of-sight dependent, microwave or Free-Space Optical (FSO) link to a nearby vessel or platform. "Determining a first value" (L_add) is the aggregated buffer of sensor data and diagnostic information on the buoy/array. "Determining a second value" (L_avail) on the satellite PCC considers signal attenuation due to weather, antenna alignment, and satellite constellation availability. The ratio β is computed. If the release condition (α·β < C_release) is met (e.g., high-volume data burst completed, vessel moved out of range for SCC (α=0), or adverse weather affecting the SCC), CA is released. The device then reverts to solely using the robust satellite PCC for essential, low-rate data, preserving energy and ensuring critical data delivery irrespective of local conditions.

sequenceDiagram
    participant Buoy_Sensor_Array as Buoy/Offshore Sensor Array
    participant Off_Platform as Offshore Platform/Vessel (Base Station)
    participant Satellite_Gateway as Satellite Gateway (PCC Endpoint)

    Buoy_Sensor_Array ->> Off_Platform: High-bandwidth data burst (SCC + PCC traffic)
    Buoy_Sensor_Array ->> Satellite_Gateway: Critical data (PCC traffic)

    activate Off_Platform
    Off_Platform->>Off_Platform: Determine L_add (Buoy buffer)
    Off_Platform->>Off_Platform: Determine L_avail (PCC Satellite Link)
    Off_Platform->>Off_Platform: Determine SCC Availability (α) (Microwave/FSO link)
    Off_Platform->>Off_Platform: Calculate Ratio β = L_add / L_avail
    Off_Platform->>Off_Platform: Check Release Condition (α·β < C_release)
    alt Release Condition Met
        Off_Platform-->>Buoy_Sensor_Array: Release SCC
        Buoy_Sensor_Array->>Satellite_Gateway: Transmit on Satellite PCC only
    else Release Condition Not Met
        Off_Platform->>Buoy_Sensor_Array: Continue PCC + SCC
    end
    deactivate Off_Platform

2.5 Cross-Domain Application 3: Smart City Infrastructure Monitoring (e.g., Traffic, Environmental)

Enabling Description:
In smart city infrastructure, the "first communication device" is a pole-mounted multi-sensor unit gathering real-time traffic flow, air quality, and noise pollution data. The "first component carrier" (PCC) is a city-wide LoRaWAN or NB-IoT network for continuous, low-bandwidth data streams. The "second component carrier" (SCC) is a local Wi-Fi or CBRS (Citizens Broadband Radio Service) access point for high-definition video analytics or urgent event alerts. "Determining a first value" (L_add) is the data buffer of the multi-sensor unit, indicating pending data transmission for analysis. "Determining a second value" (L_avail) on the PCC accounts for network congestion and current signal quality in the urban environment. The ratio β is computed. If the release condition (α·β < C_release) is met (e.g., a traffic incident video burst has completed, air quality anomaly resolved, or local Wi-Fi AP experiences backhaul congestion making it unavailable (α=0)), CA is released. The multi-sensor unit then reverts to the energy-efficient LoRaWAN/NB-IoT PCC for routine monitoring, reducing power consumption and freeing up local high-bandwidth resources.

graph TD
    A[Multi-Sensor Unit] -- Data Accumulation --> B(Data Buffer L_add);
    C[LoRaWAN/NB-IoT PCC] -- Network Status/Avail --> D{Determine L_avail (PCC)};
    E[Local Wi-Fi/CBRS SCC] -- Link Quality/Load --> F{Determine SCC Avail (α)};
    B & D & F --> G{Calculate β = L_add / L_avail};
    G --> H{Check Release Condition α·β < C_release?};
    H -- Yes --> I[Deactivate SCC (Release CA)];
    I --> J[Sensor Unit Transmits on PCC only];
    H -- No --> K[Continue PCC + SCC];

2.6 Integration with Emerging Tech 1: AI-Based Adaptive CA Release Policy

Enabling Description:
The method for releasing carrier aggregation is enhanced by an AI-based adaptive policy engine. A Deep Reinforcement Learning (DRL) agent operates at the base station or a centralized network orchestrator. This DRL agent observes network state (L_add, L_avail, α, interference levels, QoS metrics, energy consumption of UEs and BS), and learns optimal C_release values. Instead of a static C_release, the DRL agent dynamically adjusts the release threshold based on real-time network conditions and predicted future traffic. The DRL agent's "reward" function is designed to optimize a multi-objective goal, such as minimizing signaling overhead, maximizing overall system throughput, and balancing energy consumption across component carriers, while maintaining minimum QoS. When the traditional α·β < C_release condition is met, the DRL agent's policy is consulted. If the DRL agent determines that releasing the SCC would violate a long-term network objective (e.g., lead to future congestion spikes, or is part of a planned resource reshuffling), it can override the immediate release, keeping the SCC active for a short grace period, or trigger an alternative resource reallocation.

graph TD
    A[Network State (L_add, L_avail, α, QoS, Interference)] --> B(DRL Agent - Release Policy);
    B -- Dynamic C_release --> C{Base Station / Orchestrator};
    C --> D{Calculate β = L_add / L_avail};
    D & C --> E{Check Traditional Release Condition α·β < Dynamic_C_release?};
    E -- Yes --> F{DRL Agent Policy Check};
    F -- Override Release (No) --> G[Continue PCC + SCC];
    F -- Allow Release (Yes) --> H[Release SCC];
    H --> I[Network Performance Metrics (Reward Signal)];
    I --> B;
    E -- No --> G;

2.7 Integration with Emerging Tech 2: Distributed Ledger Technology (DLT) for Auditable CA Release

Enabling Description:
This variation integrates a Distributed Ledger Technology (DLT) (e.g., a consortium blockchain or a permissioned distributed ledger) to provide an auditable and transparent record of carrier aggregation release decisions, particularly for critical infrastructure or public safety networks where accountability is paramount. When the base station determines that the release condition (α·β < C_release) is satisfied for a "first communication device" (e.g., a critical infrastructure sensor), it doesn't immediately release CA. Instead, it generates a "Release Proposal" transaction containing L_add, L_avail, β, α, C_release, and a timestamp. This proposal is submitted to the DLT. A smart contract on the DLT, pre-programmed with the network's release policies, verifies the proposal against immutable rules and historical network state recorded on the ledger. If the smart contract validates the release (e.g., confirms no outstanding critical data, no SLA violation), it issues a "Release Approval" event. Only upon receipt of this DLT-approved event does the base station then proceed to physically release the SCC. All such proposals, validations, and approvals are immutably recorded, allowing for post-event auditing and dispute resolution.

sequenceDiagram
    participant Base_Station
    participant DLT_Smart_Contract as DLT Smart Contract (Release Policy)
    participant DLT_Network as DLT Network (Consensus)

    Base_Station->>Base_Station: Determine L_add, L_avail, α, β
    Base_Station->>Base_Station: Check Release Condition (α·β < C_release)
    alt Release Condition Met
        Base_Station->>DLT_Smart_Contract: Submit Release Proposal (Transaction)
        DLT_Smart_Contract->>DLT_Smart_Contract: Validate Proposal against rules/ledger
        DLT_Smart_Contract-->>DLT_Network: Request Consensus
        DLT_Network->>DLT_Network: Achieve Consensus
        DLT_Network-->>DLT_Smart_Contract: Consensus Reached
        DLT_Smart_Contract-->>Base_Station: Issue Release Approval (Event)
        Base_Station->>Base_Station: Release SCC
    else Release Condition Not Met
        Base_Station->>Base_Station: Continue PCC + SCC
    end

2.8 The "Inverse" / Failure Mode: Graceful Degradation of CA for Mission-Critical Links

Enabling Description:
This derivative implements a graceful degradation mode for carrier aggregation release, designed for mission-critical "first communication devices" (e.g., emergency responder radios, military drones) where abrupt CA release could be detrimental. When the base station determines the release condition (α·β < C_release) is met, instead of immediate release, it initiates a "graceful degradation" sequence. First, the SCC is transitioned into a "standby" mode, where its power is significantly reduced, but it remains available for rapid re-activation if L_add suddenly increases again. During this standby, only minimal control signaling is maintained. Second, the system prioritizes specific traffic types (e.g., voice, command & control) to remain on the PCC with guaranteed QoS, while best-effort traffic is buffered or dropped. The actual physical release of the SCC occurs only after a configurable "degradation timer" expires, or if the PCC alone proves absolutely sufficient for a prolonged period, or if a higher-priority task requires the SCC resources. This prevents sudden drops in aggregated bandwidth for critical applications and allows for a smooth transition back to PCC-only operation.

stateDiagram-v2
    state "CA_Fully_Active" as CA_Active
    state "SCC_Standby_Degraded" as SCC_Standby
    state "PCC_Only_Critical_Mode" as PCC_Only

    [*] --> CA_Active : Initial CA active

    CA_Active --> SCC_Standby : α·β < C_release AND Mission_Critical_Traffic
    SCC_Standby --> PCC_Only : Degradation_Timer_Expires OR PCC_Self_Sufficient_Long_Term
    SCC_Standby --> CA_Active : L_add_Increases_Rapidly OR New_Critical_Traffic

    PCC_Only --> CA_Active : α·β > C_activate AND Mission_Critical_Traffic_Increase

    CA_Active --> PCC_Only : α·β < C_release AND Not_Mission_Critical

Combination Prior Art Scenarios

Here are three combination prior art scenarios where the core principles of US Patent 9,320,041 can be combined with existing open-source standards to make future variations obvious.

  1. US9320041 + 3GPP LTE-Advanced Standard (Release 10 onwards):

    • Description: The fundamental mechanisms of carrier aggregation, including the definition of PCC and SCCs, and the signaling messages (e.g., RRCConnectionReconfiguration for CA activation/deactivation, MAC CEs for buffer status reports (BSRs)) are extensively defined in 3GPP Technical Specifications (e.g., 3GPP TS 36.331 for RRC, 3GPP TS 36.321 for MAC). US9320041's concept of using buffer depth or BSRs (explicitly mentioned in the patent) as triggers for dynamic CA activation/release, and the sequential activation/release of SCCs, would be obvious when combined with the detailed operational procedures and message structures already laid out in 3GPP Release 10 and subsequent releases. A PHOSITA would readily understand how to implement the patent's logic within the existing signaling framework to dynamically manage component carriers based on traffic load, as an optimization to the standard CA procedures.
    • Relevance: The patent itself operates within the LTE-Advanced context, making direct integration with 3GPP specifications an obvious step for any implementer. The 3GPP specifications represent a pervasive open-source standard in the cellular industry.

  2. US9320041 + Linux Kernel Network Stack (e.g., for eNB/gNB implementation):

    • Description: Modern base stations (eNBs/gNBs) are often implemented on general-purpose hardware running Linux-based operating systems. The Linux kernel's network stack provides extensive functionalities for managing network interfaces, queuing disciplines (QoS), packet buffering, and scheduling. Combining US9320041's methodology (determining L_add from buffer queues, L_avail from interface statistics, calculating ratios, and applying thresholds) with the modular and extensible nature of the Linux network stack would be obvious to a software engineer or network architect. The dynamic activation/release of SCCs could be implemented as software-defined network (SDN) functions leveraging Linux's traffic control (tc) utilities and netlink sockets to reconfigure network interfaces (representing component carriers) and their associated scheduling parameters.
    • Relevance: Linux is a dominant open-source operating system in networking equipment. Demonstrating how US9320041's concepts can be implemented using standard Linux networking tools reinforces the obviousness of such implementations.

  3. US9320041 + Open RAN (O-RAN) Architecture and Interfaces:

    • Description: The O-RAN Alliance specifies open and disaggregated radio access network (RAN) architectures, including interfaces (e.g., O-CU-CP, O-DU, O-RU) and intelligent controllers (RICs - Near-RT RIC and Non-RT RIC). US9320041's methods for dynamic CA management (determining traffic state, resource availability, ratios, and thresholds) could be implemented as an xApp (for Near-RT RIC, handling sub-second decisions) or an rApp (for Non-RT RIC, for policy and optimization over longer timeframes) within the O-RAN framework. The O-RAN interfaces (e.g., E2 interface for Near-RT RIC control, A1 interface for Non-RT RIC policies) provide standardized mechanisms for the RIC to collect necessary data (e.g., buffer status, resource usage) from O-DUs and O-RUs, and to issue commands for activating/deactivating component carriers. It would be obvious to develop an O-RAN xApp/rApp that applies US9320041's logic for optimizing CA.
    • Relevance: O-RAN is an emerging open-source standard promoting interoperability and programmability in RANs. Integrating patented concepts into this open architecture highlights their implementation within a widely adopted, flexible framework.

Generated 6/4/2026, 3:58:32 AM