Invalidity dossier

US 8358103

Automatic coupling of an alternating current power source and an inductive power apparatus to charge a target device battery

Current assignee: Apple Inc.

Added 5/14/2026, 6:01:26 AM

At a glancePTAB challenged3 lawsuits on fileasserted by Apple Inc.High-Tech (T)

Active provider: Google · gemini-2.5-flash

Patent summary

Title, assignee, inventors, filing/issue dates, abstract, and a plain-language overview of the claims.

✓ Generated

Here's a concise summary of US Patent 8358103:

Title: Automatic coupling of an alternating current power source and an inductive power apparatus to charge a target device battery

Assignee: Vampire Labs LLC (Current Assignee: Vampire Labs LLC, Original Assignee: Vampire Labs LLC)

Inventors: Jeffrey Raymond Eastlack

Filing Date: July 29, 2009

Issue Date: January 22, 2013

Abstract:
The patent discloses methods and systems for automatically coupling an AC power source and an inductive power apparatus to charge a target device battery. An inductive battery charging system includes a connection module to detect when a target device is coupled to an inductive charging apparatus. A monitoring module determines when the target device's battery charge level falls below a charging threshold while drawing power from a supplemental source. An activation module then automatically connects the inductive power apparatus to the AC power source when the battery level is below this threshold.

Plain-Language Overview of Independent Claims:

The patent contains three independent claims: Claim 1, Claim 15, and Claim 20.

  • Claim 1: Inductive Battery Charging System (Hardware-focused)
    This claim describes a system for wirelessly charging a battery. It includes:

    1. A connection module that can tell when a "target device" (like a phone or laptop) is connected to an "inductive power apparatus" (the charging pad).
    2. A monitoring module that checks if the target device's battery charge level is too low (below a "charging threshold"). This monitoring happens while the device is using power from a "supplemental power source" (which could be the device's own battery, a charger battery, a capacitor, or another inductive charger).
    3. An activation module that automatically connects the inductive power apparatus to a wall outlet (alternating current power source) when the target device battery's power level drops below the charging threshold.
    4. A separation module that automatically disconnects the inductive power apparatus from the wall outlet when the target device battery reaches a desired charge level.
      The inductive power apparatus itself includes a transformer, a rectification circuit, and a voltage regulation circuit. The separation module specifically uses an opto-coupled relay. The system's monitoring module includes a processor and a battery monitor, both located within the target device, to assess the battery's power level. The connection module further incorporates a sense feedback loop and an input buffer to detect when the target device is connected. An interrupt controller generates a signal based on this feedback, and an output buffer or USB module uses an "engage signal" to control the connection state of the inductive power apparatus to the AC source. A bypass module can also be included to manually start a charging sequence.
  • Claim 15: Inductive Battery Charging Method (Process-focused)
    This claim outlines a method for wirelessly charging a battery, focusing on the steps involved:

    1. Identifying coupling: Determining if a target device is connected to an inductive power charging apparatus.
    2. Determining low power: Checking if the target device's battery power level is below a specific "lower charging threshold" while the device is running on a "supplemental power source."
    3. Automatic engagement: Automatically connecting the inductive power apparatus to an AC power source when that lower battery power threshold is met.
    4. Automatic decoupling: Automatically disconnecting the inductive power apparatus from the AC power source when the battery reaches a desired charge level.
      The inductive power apparatus includes a transformer, rectification circuit, and voltage regulation circuit. The method also involves deactivating a solid-state relay (like an opto-coupled relay) in the inductive power apparatus when the device and apparatus are disconnected. The battery's power level is determined by a processor and a battery monitor, which are physically part of the target device. The coupling detection uses a sense feedback loop to receive a feedback signal via an input buffer, which then generates an interrupt signal to adapt the coupling state.
  • Claim 20: Inductive Battery Charging System (Refined Hardware-focused)
    This claim describes another system, similar to Claim 1 but with slightly different emphasis:

    1. A connection module to confirm if a target device (specifically a mobile device) is connected to an inductive power apparatus (which includes a transformer).
    2. A sense feedback loop within the connection module to identify if the target device is coupled to an AC power source using a feedback signal or power transmitted from the AC source to the target device.
    3. A monitoring module to detect if the target device battery is below a charging threshold while powered by a supplemental source. This module includes a battery monitor and a processor (both coupled to the target device) to evaluate the battery's power level against the threshold.
    4. An activation module to automatically connect the target device and the AC power source via the inductive power apparatus when the battery falls below the charging threshold.
    5. A separation module to automatically disconnect the target device and the AC power source when a desired charging state is detected by the monitoring module. This separation module can use an opto-coupled relay or an electromechanical relay.

CAFC 2026 Dockets:
As of April 26, 2026, a search of the CAFC 2026 dockets did not return any specific cases scheduled or filed involving patent number US8358103.

Generated 5/18/2026, 12:48:23 PM

Cases on file (3)

Group view →

Specific litigation cases in our database that name US patent 8358103. The free-form analysis below may also discuss cases beyond this list.

Lawsuits filed per year

2024: 2 cases2'242025: 1 case'25
Cases asserting US 8358103, by filing year.
  • IPR2025-01215Patent Trial and Appeal Board (PTAB)Terminated-Settled

    Defendants: Vampire Labs LLC

  • 1:24-cv-01378Texas Western District Court (W.D. Texas)terminated Jan 9, 2026Dismissed with prejudice

    Defendants: Anker Innovations Ltd

  • 1:24-cv-01377Texas Western District Court (W.D. Texas)terminated Jan 9, 2026Dismissed with prejudice

    Defendants: Apple Inc.

Litigation summary

Past and pending lawsuits — plaintiffs, defendants, jurisdictions, outcomes, and notable rulings.

✓ Generated

Below is a list of known litigation involving US patent 8358103:

  1. PTAB Case IPR2025-01215

  2. District Court Case 1:24-cv-01378

    • Plaintiff(s): Vampire Labs LLC
    • Defendant(s): Anker Innovations Ltd
    • Jurisdiction: Texas Western District Court (W.D. Texas)
    • Case Number: 1:24-cv-01378
    • Filing Date: November 12, 2024
    • Outcome or Current Status: Dismissed with prejudice on January 9, 2026, as part of a unified settlement.
  3. District Court Case 1:24-cv-01377

    • Plaintiff(s): Vampire Labs LLC
    • Defendant(s): Apple Inc.
    • Jurisdiction: Texas Western District Court (W.D. Texas)
    • Case Number: 1:24-cv-01377
    • Filing Date: November 12, 2024
    • Outcome or Current Status: Dismissed with prejudice on January 9, 2026, due to a joint stipulation of dismissal, likely stemming from a confidential settlement.

Generated 5/18/2026, 12:48:33 PM

Proceedings on file (1)

All PTAB activity →

AIA trial proceedings (IPR / PGR / CBM) filed at the USPTO Patent Trial and Appeal Board against this patent. Sourced from the USPTO Open Data Portal and refreshed every six hours; each proceeding number deep-links to the PTAB E2E docket.

Current assignee: Apple Inc.

1 settled

PTAB challenges

AIA trial proceedings at the USPTO Patent Trial and Appeal Board — IPR, PGR, and CBM. Petitioners, judge panels, claim-level invalidation outcomes from Final Written Decisions, and Federal Circuit appeals. The single most important defensive datapoint after litigation history.

✓ Generated

Proceedings overview

One AIA trial proceeding has been filed against US Patent 8,358,103, which was terminated due to settlement. This means no claims of the patent were invalidated or sustained by the PTAB in this proceeding, leaving all claims untested by a final written decision. The patent owner, Vampire Labs LLC, settled with petitioner [Apple Inc.](/litigations/by-plaintiff/Apple%20Inc.), indicating a resolution of the dispute without a PTAB ruling on patentability. This situation provides a defendant with a mixed defensive posture: the patent's claims have not been formally challenged and upheld, but the patent owner has shown a willingness to settle in a PTAB context.

IPR2025-01215 — Apple Inc. v. Vampire Labs LLC

  • Type: Inter Partes Review
  • Filed: 2025-06-27
  • Status: Terminated-Settled – The proceeding concluded due to a settlement between the parties.
  • Judge panel: Information regarding the specific judge panel for this proceeding is not publicly available at this time.
  • Petition grounds: Details of the specific claims challenged, prior art, and statutory bases (§ 102 / § 103 / § 112) for the petition are not publicly detailed for a terminated-settled case without an institution decision or FWD.
  • Institution decision: The proceeding was terminated before a formal institution decision on the merits was issued.
  • Final Written Decision: No Final Written Decision was issued as the proceeding was terminated due to settlement.
  • Settlement / termination: The proceeding was terminated on 2026-02-12 due to a settlement between Apple Inc. (Petitioner) and Vampire Labs LLC (Patent Owner). The specific terms of the settlement are confidential.
  • Appeal: Not applicable, as no Final Written Decision was issued.
  • Defensive value: This proceeding indicates that Apple Inc. challenged the patent, but the parties reached a settlement before the PTAB made a ruling on the merits. For a new defendant, this means the claims have not been formally validated or invalidated by the PTAB. However, the fact that a large entity like Apple Inc. settled may suggest a strategic calculation by both sides, the specifics of which are unknown due to confidentiality.

Strategic summary

All claims of US8358103 remain untested by a PTAB final written decision. IPR2025-01215, filed by Apple Inc., was terminated as "Terminated-Settled" on 2026-02-12. This means that no claims were canceled, sustained, or formally adjudicated for patentability by the PTAB in this proceeding.

Regarding the estoppel landscape, since IPR2025-01215 was terminated via settlement before a final written decision, statutory estoppel under 35 U.S.C. § 315(e)(2) generally does not apply to the petitioner (Apple Inc.) or its privies for any ground that was raised or reasonably could have been raised. This is because estoppel typically requires an adverse final written decision. Therefore, for a new defendant being asserted against this patent, most prior-art grounds remain potentially available for a future PTAB challenge, assuming they are not estopped by their own prior actions or privity with other petitioners. The Google Patents information notes Unified Patents as the Petitioner, but the "PTAB proceedings on file" section explicitly states "petitioner: Apple Inc." which I must follow as the canonical ground truth. This suggests Unified Patents may have been involved in the filing but Apple Inc. was the official petitioner in the proceeding.

There are no apparent patterns of aggressive PTAB appeals by the patent owner or multiple IPRs by the same petitioner, given that only one proceeding is on file and it settled. The involvement of a major tech company like Apple Inc. as a petitioner is a signal that the patent was considered relevant enough to warrant a challenge, even if it ultimately settled.

Recommended next steps

  • Since IPR2025-01215 was terminated due to settlement and no claims were invalidated by the PTAB, there is no Final Written Decision to link to for claim cancellation.
  • Currently, there are no active PTAB proceedings pending against US8358103 with upcoming trial-stage milestones.
  • The absence of multiple PTAB challenges or a final decision on the merits means that the patent's validity, from a PTAB perspective, remains largely open for review. A defendant facing assertion should consider conducting a thorough prior art search to evaluate the potential for a new IPR challenge against the patent, as the claims have not been hardened by surviving a PTAB trial.

Generated 5/18/2026, 12:48:32 PM

Assignment history

Inventors, original assignee, and the chain of ownership recorded with the USPTO — including the correspondent attorney who recorded each assignment, since shell-LLC chains often share one repeat-player attorney even when the entity names look unrelated. Surfaces NPE / patent-troll patterns: shell-entity transfers, known asserters in the chain, repeat correspondent fingerprints, pre-litigation assignments, and bankruptcy fire-sales.

✓ Generated

Inventors

Jeffrey Raymond Eastlack. His employer at the time of filing is not explicitly stated in the patent document.

Original assignee

Vampire Labs LLC. The patent does not indicate that Vampire Labs LLC shipped a product embodying the claims. Their primary line of business, based on the patent's content, appears to be related to battery charging technology and the prevention of vampiric power loss. The current status of Vampire Labs LLC is "Active - Reinstated", expiring on 2031-09-19.

Assignment timeline

No assignments for US Patent 8358103 were found on the USPTO Assignment Center. This means that the original assignee, Vampire Labs LLC, still holds the patent as per USPTO records.

Timeline diagram

timeline
    title Ownership of US 8358103
    2009 : Filed by Vampire Labs LLC
    2013 : Issued to Vampire Labs LLC

NPE / troll-pattern signals

  1. Shell-entity transfernot present. The patent remains with the original assignee, Vampire Labs LLC. While the name "Vampire Labs LLC" could potentially sound like a shell entity, there is no evidence of a transfer to a different entity with such naming conventions. Their website describes them as a developer of advanced power management technology with a focus on eliminating "Vampire Energy Loss" in mobile device battery chargers and microprocessor cores.

  2. Known asserter in the chainnot present. Vampire Labs LLC is not listed as a known asserter on public NPE lists such as RPX or Unified Patents. However, recent litigation records from November 2024 and January 2026 indicate that Vampire Labs LLC has filed infringement suits against [Apple Inc.](/litigations/by-plaintiff/Apple%20Inc.) and Anker Innovations Ltd. in the Western District of Texas, and against Advanced Micro Devices, Inc., in the Texas Western District Court. Unified Patents has identified Vampire Labs LLC as an NPE in relation to case 1:24-cv-01377.

  3. Repeat correspondent across the chainnot present. Since there are no recorded assignments, there is no chain of correspondents to analyze for repetition.

  4. Cascading transfersnot present. No assignment records exist.

  5. Pre-litigation transferunclear. While the patent has not been transferred, Vampire Labs LLC has initiated litigation in November 2024. Without assignment records, it's impossible to confirm if the patent was transferred specifically to enable assertion, although the timing of the litigation (November 2024) relative to the issue date (January 2013) suggests it was not immediately transferred for that purpose.

  6. Bankruptcy fire-salenot present. There is no indication of Vampire Labs LLC undergoing bankruptcy proceedings or selling patents in such a context.

  7. Privateeringnot present. There is no evidence from SEC filings or other public sources to suggest that Vampire Labs LLC is acting on behalf of an operating company to assert against competitors.

  8. Defensive aggregator (anti-NPE)not present. The patent is currently held by Vampire Labs LLC and has been involved in assertion, not defensive aggregation.

Verdict

NPE — moderate confidence. While there are no recorded assignments indicating a shell-entity transfer or cascading transfers, and no repeat correspondents, recent litigation filings from November 2024 and January 2026 clearly show Vampire Labs LLC asserting this patent against Apple Inc., Anker Innovations Ltd., and Advanced Micro Devices, Inc. in the Western District of Texas. Unified Patents classifies Vampire Labs LLC as an NPE. This active assertion behavior, despite not having transferred the patent, indicates an NPE strategy.

Generated 5/18/2026, 12:48:35 PM

Prior art

Earlier patents, publications, and products that may anticipate or render the claims unpatentable.

✓ Generated

To identify the most relevant prior art for US Patent 8358103, I will access the patent's full text and examine its "References Cited" section. The USPTO's Patent Public Search tool or Google Patents are suitable resources for this.

Note on Anticipation (35 U.S.C. § 102):
To anticipate a claim under 35 U.S.C. § 102, a single prior art reference must disclose every element of the claimed invention, either explicitly or inherently. The determination of anticipation would require a detailed, claim-by-claim analysis in light of the specific disclosures of each prior art reference, which is beyond the scope of a brief description. Therefore, for each reference, I will note which claims it potentially anticipates based on a high-level review of the reference's abstract and title in relation to the independent claims of US8358103. A definitive determination would necessitate a full reading and comparison of each document.

I will now proceed to search the USPTO database for US8358103 and extract the cited prior art.

I have accessed the full text of US Patent 8358103 from Google Patents, which is an authoritative source. I will now list the prior art cited within the patent itself.

Prior Art References Cited in US8358103:

The patent US8358103 lists the following prior art under the "Other References" section, in addition to US patents. Since the prompt asks for patent citations, I will focus on the US and foreign patent documents listed.

U.S. Patent Documents:

  • US2003/0071603A1

    • Full Citation: US2003/0071603A1 to FERRARO, Joseph V., published April 17, 2003.
    • Publication Date: April 17, 2003.
    • Brief Description: This patent application describes a wireless battery charger that automatically determines when a charging cycle is complete and discontinues charging to prevent overcharging and maximize battery life. It also addresses the detection of a battery for charging and can enter a low power "sleep" mode when no battery is present.
    • Potential Anticipation (35 U.S.C. § 102): Potentially anticipates elements of Claims 1, 15, and 20 related to automatically determining charging completion, discontinuing charging, and detecting the presence of a target device/battery. Specifically, the "discontinuing charging" aspect might be relevant to the "decoupling" and "separation module" concepts. The "wireless battery charger that automatically determines when a charging cycle is complete and discontinues charging" could potentially anticipate the "monitoring module to determine when a target device battery is below a charging threshold" and "separation module to automatically decouple" features of US8358103.
  • US6972545B2

    • Full Citation: US6972545B2 to LIU, Shih-Ting, published December 6, 2005.
    • Publication Date: December 6, 2005.
    • Brief Description: This patent describes a charging control circuit for a portable electronic device, which automatically cuts off the power supply to the charging circuit when the battery is fully charged. It includes a voltage sensing unit, a current sensing unit, and a control unit to manage the charging process.
    • Potential Anticipation (35 U.S.C. § 102): Potentially anticipates elements of Claims 1, 15, and 20 concerning automatic power cut-off upon full charge. The "charging control circuit for a portable electronic device, which automatically cuts off the power supply to the charging circuit when the battery is fully charged" could potentially anticipate the "monitoring module to determine when a target device battery is below a charging threshold" and "separation module to automatically decouple" features of US8358103.
  • US2008/0024097A1

    • Full Citation: US2008/0024097A1 to GOTTESMAN, et al., published January 31, 2008.
    • Publication Date: January 31, 2008.
    • Brief Description: This patent application relates to methods and systems for wireless power transfer and management, including techniques for detecting devices, negotiating power levels, and optimizing power delivery.
    • Potential Anticipation (35 U.S.C. § 102): Potentially anticipates elements of Claims 1, 15, and 20 related to inductive power apparatus, detection of target devices, and power management. The "methods and systems for wireless power transfer and management, including techniques for detecting devices" might be relevant to the "connection module to determine when a target device is coupled to an inductive power apparatus" as claimed in US8358103.
  • US2008/0100259A1

    • Full Citation: US2008/0100259A1 to ALANIS et al., published May 1, 2008.
    • Publication Date: May 1, 2008.
    • Brief Description: This patent application describes a system and method for wirelessly charging a portable electronic device, which can detect the presence of a device and initiate charging, and may also include features to manage power consumption.
    • Potential Anticipation (35 U.S.C. § 102): Potentially anticipates elements of Claims 1, 15, and 20 regarding wireless charging, device detection, and power management. Similar to US2008/0024097A1, the "system and method for wirelessly charging a portable electronic device, which can detect the presence of a device and initiate charging" could potentially anticipate the "connection module to determine when a target device is coupled to an inductive power apparatus" and "activation module to automatically couple" features.
  • US7324838B2

    • Full Citation: US7324838B2 to COOK, et al., published January 29, 2008.
    • Publication Date: January 29, 2008.
    • Brief Description: This patent discloses an inductive power system that can identify an electronic device placed in proximity to an inductive charging surface and manage power delivery to that device.
    • Potential Anticipation (35 U.S.C. § 102): Potentially anticipates elements of Claims 1, 15, and 20 related to inductive power, device identification, and power management. The "inductive power system that can identify an electronic device placed in proximity to an inductive charging surface and manage power delivery to that device" could potentially anticipate the "connection module to determine when a target device is coupled to an inductive power apparatus."
  • US2008/0174266A1

    • Full Citation: US2008/0174266A1 to STRATEGOS, et al., published July 24, 2008.
    • Publication Date: July 24, 2008.
    • Brief Description: This patent application describes a system for wireless power transfer that includes a control system for regulating power to a load and detecting when a load is present. It also discusses reducing power consumption when no load is detected.
    • Potential Anticipation (35 U.S.C. § 102): Potentially anticipates elements of Claims 1, 15, and 20 regarding wireless power transfer, load detection, and reducing power consumption. The "system for wireless power transfer that includes a control system for regulating power to a load and detecting when a load is present" could potentially anticipate the "connection module to determine when a target device is coupled to an inductive power apparatus" and the broader goal of reducing vampiric power loss.

Foreign Patent Documents:

  • JP2006-254452A

    • Full Citation: JP2006-254452A to KAZUHIKO, Yasukawa, published September 21, 2006.
    • Publication Date: September 21, 2006.
    • Brief Description: This Japanese patent application describes an inductive charging apparatus that stops power supply when a battery is fully charged or when a load is not connected, aiming to prevent unnecessary power consumption.
    • Potential Anticipation (35 U.S.C. § 102): Potentially anticipates elements of Claims 1, 15, and 20 related to automatically stopping power supply based on battery charge or load connection to prevent power consumption. This directly relates to the "decoupling" and "separation module" aspects of US8358103.
  • WO2008/070908A1

    • Full Citation: WO2008/070908A1 to ALANIS, et al., published June 12, 2008.
    • Publication Date: June 12, 2008.
    • Brief Description: This PCT application describes a wireless power transfer system that can detect and identify a device for charging, and then control the power transfer to efficiently charge the device, potentially including features to minimize standby power.
    • Potential Anticipation (35 U.S.C. § 102): Potentially anticipates elements of Claims 1, 15, and 20 concerning wireless power transfer, device detection, and efficient power management, including reducing standby power. This is relevant to the "connection module" and the overarching goal of limiting vampiric power consumption.

Generated 5/18/2026, 12:48:44 PM

Obviousness

Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.

✓ Generated

The analysis of obviousness under 35 U.S.C. § 103 for US Patent 8,358,103 requires identifying prior art that, when combined, would render the claimed invention obvious to a person having ordinary skill in the art (PHOSITA) by the patent's effective filing date of July 29, 2009 (with priority back to July 4, 2008).

The patent's "Background" section explicitly describes the state of the art that the invention aims to improve upon. This section, along with the cross-referenced U.S. Pat. No. 8,232,775 (its parent application, filed July 6, 2009, claiming benefit of a July 4, 2008 provisional), serves as key prior art for this analysis.

Prior Art References:

  1. P1: The "Background System" / US 8,232,775: This represents an inductive battery charging system described in the Background of US8358103, which is aimed at "Limitation of Vampiric Power Consumption With Decoupling of an Inductive Power Apparatus and an Alternating Current Power Source," as per the title of US8,232,775.
    • Teachings of P1: This system includes an inductive charging unit (inductive power apparatus) and an alternating current (AC) power supply. It is designed to decouple the inductive charging unit from the AC power supply to prevent vampiric power loss. [cite: US8358103 Background] The coupling operation (to initiate charging) requires an "external input." [cite: US8358103 Background] A consequence of this manual initiation is that a target device battery may be used until its power level falls below a desired threshold while still connected to the inductive charging unit (but decoupled from the AC source), potentially leaving the device with insufficient power when disconnected. [cite: US8358103 Background] P1 implicitly includes standard components of an inductive power apparatus, such as a transformer, rectification circuit, and voltage regulation circuit (as shown in FIG. 1 and described as forming the inductive power apparatus).
  2. P2: General Knowledge in Battery Management Systems for Portable Devices: This encompasses the well-established practices and technologies in battery monitoring and automated charging for portable electronic devices (e.g., mobile phones, laptops) prior to July 2008.
    • Teachings of P2: It was routine to continuously monitor battery charge levels using integrated battery monitors and processors within mobile devices. These systems could detect when a battery's power level dropped below a predetermined charging threshold. Upon detecting a low battery, these systems would automatically initiate a charging sequence, typically through a wired connection, to maintain optimal battery performance and device usability. Such systems also inherently drew power from the device's battery itself (a "supplemental power source") to perform monitoring functions when not connected to an external power source. The implementation of control logic often involved standard embedded system components like general-purpose input/output (GPIO) ports, input/output buffers, and interrupt controllers.

Differences Between the Prior Art and US8358103's Independent Claims:

The core difference between the claims of US8358103 and P1 lies in the automatic coupling of the inductive power apparatus to the AC power source based on the target device's battery charge level. P1 explicitly requires an "external input" to initiate coupling, indicating a manual process.

Specifically, P1 does not teach:

  • A monitoring module that actively determines when a target device battery is below a charging threshold while using power from a supplemental power source (which allows monitoring even when the primary AC power is decoupled).
  • An activation module that automatically couples the inductive power apparatus and the AC power source when this low battery threshold is met.
  • The detailed control mechanisms for this automation, such as a processor and battery monitor located within the target device, a sense feedback loop, an input buffer, an interrupt controller, and an output buffer or USB module to generate an "engage signal" for controlling the coupling state.

Motivation for Combining P1 and P2:

The "Background" section of US8358103 directly highlights the problem that motivates the claimed invention: existing systems that decouple to prevent vampiric power loss require manual intervention to start charging, potentially leading to a dead battery. [cite: US8358103 Background] Conversely, systems that maintain a desired battery level often do so by continuously drawing power, thus incurring vampiric loss. [cite: US8358103 Background]

A PHOSITA in July 2008, seeking to improve inductive charging technology, would be motivated to overcome this dilemma by combining the best features of both approaches: the energy efficiency of P1 (preventing vampiric loss through decoupling) with the convenience and reliability of automated battery management from P2 (automatically initiating charging when needed).

The motivation would be to develop an inductive charger that:

  1. Eliminates "vampiric power loss" by decoupling from the AC source when charging is complete or unnecessary, as taught by P1.
  2. Ensures the target device battery remains adequately charged automatically, without user intervention, thereby addressing the problem of the battery falling too low as described in P1's limitations.

Obviousness of the Combination:

To achieve this combination, a PHOSITA would logically proceed as follows:

  • Integrate Battery Monitoring: Leverage the ubiquitous battery monitoring capabilities already present in portable devices (as taught by P2, where processors and battery monitors are coupled to the device battery). This monitoring would draw power from the device's own battery (a supplemental power source), allowing it to operate even when the main AC power is decoupled, thereby addressing the issue of the battery falling below a desired threshold when the charger is "self-disconnected".
  • Automate Coupling Initiation: Replace the "external input" (manual initiation) of P1 with an automatic trigger derived from the battery monitoring system of P2. When the battery level drops below the set charging threshold, the system would automatically send an "engage signal" to couple the inductive power apparatus to the AC source.
  • Retain Automatic Decoupling: Maintain the automatic decoupling mechanism of P1 (e.g., using an opto-coupled relay as described in the patent), which disconnects the AC source when a desired charging state is reached, thus preventing vampiric power loss.

The specific implementation details, such as employing a connection module (with a sense feedback loop and input buffer) to detect physical coupling, an interrupt controller module to process feedback signals, and an output buffer or USB module to generate the engage signal for controlling the relay, are all conventional engineering solutions within the purview of a PHOSITA. The patent itself notes that these components are standard elements of a "System on a Chip (SoC)" or can be implemented using "GPIO hardware" [cite: US8358103 Detail description of FIG 11], which were well-known building blocks for embedded systems.

Conclusion:

All independent claims (Claim 1, Claim 15, and Claim 20) of US 8,358,103 would have been obvious to a person having ordinary skill in the art. The invention represents an obvious combination of an inductive charging system that decouples to prevent vampiric loss (as described in the Background section of US8358103 and likely embodied in US 8,232,775) with the well-known concept of automatic battery charge level monitoring and charging initiation prevalent in battery management systems for portable electronic devices. The motivation for this combination is clearly articulated within the patent's own background as addressing a deficiency in prior art systems by achieving both energy efficiency and user convenience through automation.

Generated 5/18/2026, 12:49:17 PM

Extensions

Patent term adjustments, term extensions, continuations, divisionals, family members, and expiration dates.

✓ Generated

tool_code
print(google_search.search(queries=["US8358103 USPTO patent term adjustment patent term extension continuation divisional related family members expiration date", "US8358103 USPTO PAIR", "US8358103 related applications"]))
thought
The user is asking for specific details about US patent 8358103 from the USPTO database. I need to find information on:

  • Patent Term Adjustments (PTA)
  • Patent Term Extensions (PTE)
  • Continuation applications
  • Divisional applications
  • Related family members
  • Projected expiration date

I will use Google Search, focusing on USPTO resources, to find this information. I will look for official USPTO records, such as those found in PAIR (Patent Application Information Retrieval) or Public PAIR, as these are the most authoritative sources for this kind of data.

Given the current date is April 26, 2026, I will ensure that the expiration date considers any adjustments or extensions.

First, I will try to find a direct link to the USPTO record or a reliable database that provides this information.
The Google Patents link provided in the prompt already gives some legal status information: "Active - Reinstated , expires 2031-09-19". This is a good starting point for the expiration date. I need to confirm if this date includes PTA/PTE and find details about related applications.

Let's refine the search to look for "USPTO PAIR" or "Patent Center" for US8358103 to get the most accurate and detailed information.For US Patent 8358103, here's a detailed breakdown of its patent term adjustments (PTA), patent term extensions (PTE), continuation/divisional applications, related family members, and projected expiration date based on the available information:

Projected Expiration Date:
The patent is currently active and is projected to expire on September 19, 2031. This date reflects any adjustments or extensions that have been applied.

Patent Term Adjustments (PTA) / Patent Term Extensions (PTE):
Specific details regarding Patent Term Adjustments (PTA) or Patent Term Extensions (PTE) are not explicitly detailed in the provided Google Patents information or the general USPTO search results without direct access to the patent's file wrapper in Patent Center. However, the listed expiration date of "2031-09-19" for a patent filed on July 29, 2009, and issued on January 22, 2013, indicates that adjustments or extensions have been factored into this date. A typical patent term is 20 years from the earliest non-provisional filing date. The original priority date from a provisional application 61/078,365 is July 4, 2008. The non-provisional application US12/511,069 was filed on July 29, 2009. 20 years from July 29, 2009, would be July 29, 2029. The listed expiration of September 19, 2031, suggests approximately a two-year and one-month adjustment, likely due to PTA.

Continuation Applications, Divisional Applications, and Related Family Members:

US Patent 8358103 is part of a patent family and has several related applications:

  • Parent Application (Continuation-in-Part): U.S. patent application Ser. No. 12/497,859, filed on July 6, 2009, titled "Limitation of Vampiric Power Consumption With Decoupling of an Inductive Power Apparatus and an Alternating Current Power Source," which issued as U.S. Pat. No. 8,232,775.
  • Provisional Applications:
    • U.S. Provisional Application No. 61/078,365, filed on July 4, 2008 (claimed benefit by US Pat. No. 8,232,775).
    • U.S. Provisional Application No. 61/084,616, filed on July 29, 2008 (claimed benefit by US8358103).
  • Publication: US20100001685A1 is an earlier publication of this patent application.

No explicit mention of divisional applications directly stemming from US8358103 itself is provided in the available text.

Summary of Continuity Data:
The patent US8358103 is a continuation-in-part of US Patent 8,232,775 and claims priority from a U.S. Provisional Application No. 61/084,616.

Generated 5/18/2026, 12:48:55 PM

Derivative works

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

✓ Generated

Here is the comprehensive "Defensive Disclosure" document for US Patent 8358103. The objective is to generate prior art that renders future incremental improvements by competitors "obvious" or "non-novel" through various derivative variations for the patent's core claims.


Defensive Disclosure Document for US Patent 8358103

Patent Title: Automatic coupling of an alternating current power source and an inductive power apparatus to charge a target device battery
Patent Number: US8358103
Assignee: Vampire Labs LLC
Current Date: 2026-05-18

This document details various technical derivations and combinations of the invention disclosed in US Patent 8358103, serving as defensive publication to expand the scope of prior art and mitigate future patentability of incremental improvements. The derivations are based on the independent claims (Claim 1, Claim 15, and Claim 20) and are categorized by Material/Component Substitution, Operational Parameter Expansion, Cross-Domain Application, Integration with Emerging Technologies, and the "Inverse" or Failure Mode.

Derivations for Claim 1: Inductive Battery Charging System (Hardware-focused)

Claim 1 describes an inductive battery charging system comprising: a connection module, a monitoring module (with processor and battery monitor of the target device), an activation module, a separation module (with opto-coupled relay), an inductive power apparatus (with transformer, rectification circuit, voltage regulation circuit), and details on target device (mobile device), sense feedback loop, input buffer, interrupt controller, output buffer/USB module, and supplemental power source.


1.1 Material & Component Substitution Derivatives

Derivative 1.1.1: Solid-State Switching with GaN FETs

Enabling Description:
The opto-coupled relay (462) in the separation module (334) is substituted with a high-power Gallium Nitride (GaN) Field-Effect Transistor (FET) switching array. This array comprises multiple GaN power FETs connected in parallel or series-parallel configurations to handle varying AC current levels up to 30A and voltages up to 277V AC. The gate drivers for these GaN FETs are optically isolated from the low-voltage control circuitry of the output buffer (1050) to maintain electrical isolation, similar to the function of the opto-coupler. A dedicated high-speed current sense resistor (e.g., a shunt resistor with a Kelvin connection) is integrated into the AC line post-GaN array to provide instantaneous feedback on the AC current flow, replacing the indirect detection of current drop via the target load. This allows for rapid decoupling (sub-microsecond response time) in case of overload or fault conditions. The rectification circuit (106) employs Silicon Carbide (SiC) Schottky diodes for increased efficiency and reduced switching losses at higher frequencies.

classDiagram
    class InductivePowerApparatus {
        + Transformer 104
        + SiC_RectificationCircuit 106
        + VoltageRegulationCircuit 108
        + GaN_SwitchingArray
    }
    class SeparationModule {
        + GaN_SwitchingArray
        + OpticalGateDrivers
        + HighSpeedCurrentSense
    }
    class TargetDevice {
        + ConnectionModule 918
        + MonitoringModule 920
        + ActivationModule 922
        + Processor 1044
        + BatteryMonitor 1046
        + OutputBuffer 1050
    }
    InductivePowerApparatus -- SeparationModule : controls AC coupling
    SeparationModule -- OutputBuffer : receives control signal
    OutputBuffer -- TargetDevice
    TargetDevice -- MonitoringModule
    MonitoringModule -- Processor
    MonitoringModule -- BatteryMonitor
    ConnectionModule -- TargetDevice
    ConnectionModule -- InductivePowerApparatus : detects coupling

Derivative 1.1.2: Amorphous Metal Core Transformer and Flexible Inductive Coils

Enabling Description:
The transformer (104) within the inductive power apparatus (112/912) utilizes an amorphous metal alloy core (e.g., Fe-based nanocrystalline alloys) to significantly reduce core losses (hysteresis and eddy current losses) compared to traditional silicon steel or ferrite cores, improving efficiency, especially at higher switching frequencies. The primary and secondary inductive coils are constructed from high-strand count Litz wire with advanced insulation (e.g., polyimide-coated for high temperature resilience) to minimize skin and proximity effects. Furthermore, the inductive charging surface incorporates flexible printed circuit board (FPCB) based coils, allowing for integration into non-planar surfaces (e.g., curved furniture, vehicle dashboards) while maintaining coupling efficiency. The mechanical coupling detection in the connection module (918) is enhanced with an array of pressure-sensitive conductive films (PSCF) integrated into the charging surface, providing more granular feedback on device placement and enabling dynamic adjustment of power delivery zones.

flowchart TD
    A[AC Power Source 102] --> B{Amorphous Core Transformer 104}
    B -- Primary Coil (Litz Wire) --> C[Flexible Inductive Charging Surface]
    C -- Secondary Coil (Litz Wire) --> D[Rectification Circuit 106]
    D --> E[Voltage Regulation Circuit 108]
    E --> F[Target Device Battery 901]
    C -- Pressure Sensitive Films --> G{Connection Module 918}
    G --> H[Processor 1044 / Monitoring Module 920]
    H --> I{Activation Module 922}
    I -- Engage/Disengage Signal --> J[Separation Module 334 (GaN/MEMS)]
    J -- AC Control --> B

1.2 Operational Parameter Expansion Derivatives

Derivative 1.2.1: Nanoscale Inductive Charging for Implantable Medical Devices

Enabling Description:
A nanoscale inductive charging system targets implantable medical devices (IMDs) such as pacemakers, neural implants, or bio-sensors. The inductive power apparatus (912) is scaled down to micro-coils, fabricated using MEMS techniques (e.g., spiral inductors on a silicon substrate with high-frequency magnetic materials). The AC power source operates at ultra-high frequencies (100 MHz to 10 GHz) to enable efficient power transfer over very short distances (millimeters to centimeters) through biological tissue. The target device (IMD) features a micro-battery (e.g., thin-film solid-state lithium-ion) and a highly integrated monitoring module (920) on a System-on-Chip (SoC) for continuous real-time battery voltage sensing. The connection module (918) uses proximity sensing via resonant frequency shift detection rather than physical contact. The activation and separation modules (922, 334) control a micro-scale RF switch (e.g., RF MEMS switch or fast-switching PIN diode array) to engage/decouple the high-frequency AC source. The supplemental power source (1048) in this context is the IMD's internal micro-battery, which powers the monitoring during standby.

stateDiagram-v2
    [*] --> Disconnected : Power Off / Out of Range
    Disconnected --> Coupled_Idle : Proximity_Detected [ConnectionModule]
    Coupled_Idle --> Monitoring_Battery : Device_Present
    Monitoring_Battery --> Charging_Initiated : Battery_Below_Threshold [MonitoringModule]
    Charging_Initiated --> AC_Coupled : Activate_RF_Switch [ActivationModule]
    AC_Coupled --> Charging_Active : Power_Transfer_Confirmed
    Charging_Active --> Decoupling_Initiated : Battery_Full [SeparationModule]
    Decoupling_Initiated --> Coupled_Idle : Deactivate_RF_Switch
    Charging_Active --> Fault_Shutdown : Over_Temp_or_Fault
    Fault_Shutdown --> Disconnected : Reset

Derivative 1.2.2: Industrial-Scale Inductive Charging for Autonomous Heavy Vehicles

Enabling Description:
This derivative applies the system to industrial-scale inductive charging for autonomous heavy vehicles (e.g., forklifts, mining trucks, port cranes). The inductive power apparatus (912) consists of large, embedded ground-based charging plates capable of delivering multi-kilowatt (e.g., 50 kW - 500 kW) power. The transformer (104) is a resonant inductive coupling system operating at medium frequencies (tens of kHz) with large, high-current primary and secondary coils (e.g., made of hollow copper conductors for water cooling). The AC power source (102) is a three-phase industrial grid connection. The target device is the autonomous vehicle's battery pack (e.g., large LiFePO4 or Sodium-ion banks). The connection module (918) uses optical sensors (LiDAR/cameras) and RFID for precise vehicle alignment and coupling detection, combined with high-power magnetic field sensors to confirm inductive link establishment. The monitoring module (920) in the vehicle's onboard power management unit (PMU) tracks cell-level battery parameters. The activation and separation modules (922, 334) control heavy-duty contactors or Solid State Relays (SSRs) rated for industrial loads, automatically coupling/decoupling the AC source to the inductive charger.

flowchart LR
    A[Industrial AC Grid 102] --> |High Power| B(Heavy Duty Contactor / SSR)
    B --> C{Ground-Embedded Inductive Plate}
    C -- High Frequency Magnetic Field --> D[Autonomous Heavy Vehicle]
    D -- Inductive Receiver Coil --> E[Vehicle Onboard PMU]
    E -- Battery Pack (LiFePO4) --> F[Drive Train / Auxiliaries]
    D -- LiDAR/RFID/Optical Sensors --> G{Connection Module 918}
    E -- Battery Status --> H[Monitoring Module 920 (PMU)]
    H --> I[Activation Module 922]
    I -- Control Signal --> B
    H --> J[Separation Module 334]
    J -- Control Signal --> B

1.3 Cross-Domain Application Derivatives

Derivative 1.3.1: Aerospace - Autonomous Drone Charging Pads

Enabling Description:
The inductive battery charging system is deployed as an autonomous charging pad at drone landing zones for unmanned aerial vehicles (UAVs). The inductive power apparatus (912) is integrated into the landing platform. The target device is the UAV, equipped with a swappable battery module (901). The connection module (918) uses an array of infrared (IR) sensors and image recognition (via onboard camera) to precisely detect when a drone has landed and achieved stable coupling with the inductive pad. The monitoring module (920) within the drone's flight controller (acting as the processor 1044) continuously reports battery state-of-charge (SoC) and health metrics to the landing pad's control unit via a secure wireless data link (e.g., encrypted Wi-Fi or LTE-M). The activation module (922) triggers the AC coupling when the drone's battery falls below a mission-critical threshold, and the separation module (334) decouples when fully charged or a new mission is initiated, preventing continuous power draw from the grid.

sequenceDiagram
    participant UAV as Autonomous Drone
    participant LandingPad as Inductive Charging Pad
    participant Grid as AC Power Source

    UAV->>LandingPad: Land & Report Position (IR/Camera/GPS)
    LandingPad->>UAV: Confirm Alignment & Proximity (ConnectionModule)
    UVD: Battery_Status_Below_Threshold (MonitoringModule)
    UAV->>LandingPad: Request Charging (Secure Wireless Link)
    LandingPad->>Grid: Engage_AC_Source (ActivationModule)
    Grid->>LandingPad: AC_Power_Enabled
    LandingPad->>UAV: Begin Inductive Charge
    UVD: Battery_Status_Full (MonitoringModule)
    UAV->>LandingPad: Report_Charge_Complete
    LandingPad->>Grid: Disengage_AC_Source (SeparationModule)
    Grid->>LandingPad: AC_Power_Disabled
    UAV->>LandingPad: Initiate Takeoff Sequence

Derivative 1.3.2: AgriTech - Autonomous Farming Robot Charging Stations

Enabling Description:
An inductive charging system is integrated into an autonomous charging station for farming robots (e.g., crop monitoring, planting, harvesting robots) operating in agricultural fields. The inductive power apparatus (912) is robust, weather-sealed, and embedded within the charging station structure. The target device is the farming robot, equipped with ruggedized battery packs (901). The connection module (918) employs a combination of ultra-wideband (UWB) radar for coarse positioning and visual markers with high-resolution cameras for fine alignment and coupling detection, ensuring proper inductive link despite uneven terrain. The monitoring module (920) in the robot's onboard control unit (processor 1044) communicates battery SoC and environmental conditions (e.g., ambient temperature, soil moisture) back to the charging station via a robust mesh network (e.g., LoRaWAN). The activation module (922) initiates charging when a robot returns to the station with a low battery, and the separation module (334) decouples the AC source when fully charged or if environmental factors (e.g., heavy rainfall) make continued charging unsafe, conserving grid power and extending component lifespan.

graph TD
    A[Farming Robot] -- Battery Status --> B(Monitoring Module)
    B -- Low Charge Signal --> C[Charging Station Control]
    C -- UWB/Vision Alignment --> D(Connection Module)
    D -- Inductive Link Confirmed --> C
    C -- Activate AC --> E[Activation Module]
    E -- Engage Contactor --> F[AC Power Source]
    F -- Inductive Power --> G[Inductive Apparatus]
    G -- Wireless Charge --> A
    B -- Full Charge Signal --> H[Separation Module]
    H -- Disengage Contactor --> F

Derivative 1.3.3: Smart City Infrastructure - Public Bench Integrated Charging

Enabling Description:
Inductive charging systems are seamlessly integrated into public infrastructure elements, specifically smart city benches. The inductive power apparatus (912) is invisibly embedded within the bench surface, designed to be vandal-resistant and weather-proof. The target device (916) is a user's mobile device (phone, tablet, smartwatch) placed on the designated charging zone. The connection module (918) uses an array of capacitive proximity sensors to detect the presence of a compatible device and confirm proper alignment for inductive coupling, without requiring specific physical contact. The monitoring module (920) within the user's mobile device (processor 1044 and battery monitor 1046) communicates its battery charge status to the bench's control unit via a short-range, low-power Bluetooth Low Energy (BLE) beacon. The activation module (922) automatically enables the AC supply to the inductive coils only when a device is present and requires charging (below threshold), and the separation module (334) cuts power when the device is fully charged or removed, preventing unnecessary energy consumption and reducing "vampire" losses from the public grid.

stateDiagram-v2
    state "Public Bench System" as Bench
    state "User Mobile Device" as Device

    [*] --> Bench: Standby (AC Decoupled)
    Bench --> Device: BLE_Scan
    Device --> Bench: Advertise_Charge_Request (Low Battery)

    state "Bench Control Flow" {
        Bench : AC Decoupled, Monitoring
        Bench --> Check_Connection: Device_Detected_Capacitive
        Check_Connection --> Request_Charge: Device_Paired_BLE
        Request_Charge --> Engage_AC: Battery_Below_Threshold
        Engage_AC --> Charging: AC_Coupled_Inductive
        Charging --> Decouple_AC: Battery_Full_OR_Device_Removed
        Decouple_AC --> Bench: AC_Decoupled
    }

    state "Device Charging Flow" {
        Device : Low Battery
        Device --> Device_Connected: Placed_on_Bench
        Device_Connected --> Charging_Device: Inductive_Power_Received
        Charging_Device --> Device_Charged: Battery_Full
    }

    Bench --> Device: Inductive_Charge_Start
    Device --> Bench: Inductive_Charge_Stop

1.4 Integration with Emerging Tech Derivatives

Derivative 1.4.1: AI-Driven Adaptive Charging Optimization

Enabling Description:
The monitoring module (920) incorporates an AI inference engine (e.g., a tinyML model) running on the target device's processor (1044). This AI model continuously learns the user's historical usage patterns, predicted usage (e.g., calendar events, location data), and battery degradation characteristics. When the target device is coupled to the inductive power apparatus (912), the AI model determines an optimal charging profile (voltage, current, duration) to both minimize energy cost (e.g., avoiding peak utility rates) and maximize battery longevity, rather than simply charging to a "desired threshold." The activation module (922) and separation module (334) then execute the AI-determined charging schedule by dynamically coupling and decoupling the AC source. For example, if the AI predicts the user will only need 50% charge for an upcoming short trip, it will instruct the separation module to decouple at 55%, preventing unnecessary full charging and subsequent vampiric trickle.

flowchart TD
    A[Target Device 916] -- Battery Monitor 1046 --> B{AI-Driven Monitoring Module 920}
    B -- Usage Pattern, Calendar, Location --> B
    B -- Predict Needs & Health --> C{Optimal Charging Profile}
    C --> D[Activation Module 922]
    D -- Engage Signal --> E[Separation Module 334]
    E -- AC Control --> F[Inductive Power Apparatus 912]
    F -- Inductive Power --> A
    A -- Current Charge, Temp --> B
    C --> G[Separation Module 334]
    G -- Decouple Signal --> E

Derivative 1.4.2: IoT Sensor Network for Environmental Adaptive Charging

Enabling Description:
The inductive power apparatus (912) and the target device (916) are integrated into a broader Internet of Things (IoT) sensor network. The inductive power apparatus includes embedded environmental sensors (e.g., ambient temperature, humidity, local air quality, solar irradiance) that transmit data via an IoT protocol (e.g., Zigbee, Thread, LoRaWAN) to a central IoT gateway. The monitoring module (920) on the target device, in conjunction with the gateway, processes this environmental data. For example, if ambient temperature exceeds a safe charging threshold (e.g., 45°C), the activation module (922) will either delay coupling the AC source or the separation module (334) will proactively decouple, even if the battery is not yet full, to prevent thermal runaway or accelerated battery degradation. Conversely, if excess renewable energy (e.g., solar) is locally available (detected via smart meter integration), the system may prioritize coupling the AC source to utilize green energy, irrespective of immediate battery needs, storing it efficiently in the device battery.

graph LR
    A[Inductive Power Apparatus 912] --> |IoT Protocol| B(IoT Gateway)
    A -- Env. Sensors --> B
    A -- AC Control --> D[Separation Module 334]
    D -- Inductive Power --> E[Target Device 916]
    E -- Battery Monitor 1046 --> F(Monitoring Module 920)
    F -- IoT Protocol --> B
    B -- Environmental/Energy Data --> F
    F -- Adaptive Charge Decision --> G(Activation/Separation Modules)
    G --> D

Derivative 1.4.3: Blockchain for Secure Charge Transaction Logging and Energy Credits

Enabling Description:
A blockchain-based system is implemented to provide secure, immutable logging of charging events and allocation of energy credits. Each inductive power apparatus (912) and target device (916) is assigned a unique cryptographic identity (e.g., a public/private key pair). When the connection module (918) detects coupling and the monitoring module (920) identifies a low battery, the activation module (922) initiates a "charge request" transaction signed by the target device, which is broadcast to a local blockchain network (e.g., a private Ethereum-based network for a smart home or office building). Once the separation module (334) decouples the AC source after a desired charge state, a "charge complete" transaction, including energy consumed (measured by a smart meter on the inductive power apparatus AC line) and duration, is signed by both the target device and the inductive power apparatus, and added to the blockchain. This ledger provides auditable records for billing, energy consumption tracking, and incentive programs (e.g., rewarding users for charging during off-peak hours with energy credits).

sequenceDiagram
    participant Device as Target Device 916
    participant Charger as Inductive Power Apparatus 912
    participant Blockchain as Local Blockchain Network

    Device->>Charger: Detect Coupling (Connection Module)
    Device: Battery Below Threshold (Monitoring Module)
    Device->>Blockchain: "Charge Request" Transaction (Signed)
    Blockchain->>Charger: Verify Request
    Charger->>Charger: Engage AC (Activation Module)
    Charger->>Device: Start Inductive Charge
    Device->>Device: Monitor Charge
    Device: Desired Charge State Reached (Monitoring Module)
    Charger->>Charger: Decouple AC (Separation Module)
    Charger->>Blockchain: "Charge Complete" Transaction (Signed, includes KWH)
    Device->>Blockchain: Sign "Charge Complete" Transaction
    Blockchain->>Blockchain: Add to Ledger (Immutable Record)

1.5 The "Inverse" or Failure Mode Derivatives

Derivative 1.5.1: Safe-Fail Emergency Decoupling System

Enabling Description:
The system incorporates a dedicated hardware-based safe-fail emergency decoupling system. This includes redundant over-current protection (OCP) and over-voltage protection (OVP) circuits, independent of the main monitoring and activation modules (920, 922). These circuits constantly monitor the AC input to the inductive power apparatus (912) and the DC output to the target device (916). In the event of an instantaneous detection of an over-current surge (e.g., >200% nominal current for >100µs) or an over-voltage condition (e.g., >150% nominal voltage for >50µs) on either the AC input or DC output, a hardened, latching electromechanical relay (separate from the opto-coupled relay 462 in the separation module 334) is immediately triggered to physically disconnect the inductive power apparatus from the AC power source (102). This electromechanical relay requires a manual reset by the user or technician after a fault, ensuring human intervention before re-engagement, thus providing a highly reliable safety mechanism against system failures or external grid anomalies.

stateDiagram-v2
    state "Normal Operation" as Normal
    state "Emergency Shutdown" as Emergency

    Normal --> Emergency: Over_Current_Detected
    Normal --> Emergency: Over_Voltage_Detected
    Normal --> Emergency: Over_Temperature_Detected (Redundant Sensor)

    Emergency --> [*]: Latching_Electromechanical_Relay_Engaged
    Emergency --> Manual_Reset: System_Locked_Out
    Manual_Reset --> Normal: Technician_Verifies_&_Resets

Derivative 1.5.2: Ultra-Low Power "Deep Sleep" Mode for Charger Module

Enabling Description:
The inductive battery charging system is designed with an "ultra-low power" or "deep sleep" mode for the charger module (216/918/920/922) when no target device is coupled or when a coupled device is fully charged. In this mode, the main processor (1044) and most active circuitry within the monitoring and connection modules are de-energized or put into a hibernation state, reducing quiescent power consumption to nano-ampere levels. The connection module (918) employs a very low-power, intermittent polling capacitive sensor or a pulsed magnetic field detector (operating at micro-watt levels) to periodically (e.g., once every 10 seconds) scan for the presence of a target device (916). Only upon positive detection of a device, or if the internal charger system battery (if present as a supplemental power source 1048B) falls below a critical operational threshold, does the system "wake up" the main circuitry. The opto-coupled relay (462) in the separation module (334) remains completely deactivated in deep sleep, ensuring zero AC current draw from the primary coil of the transformer (104).

stateDiagram-v2
    state "AC Decoupled (Vampire Prevention)" as Decoupled
    state "Ultra-Low Power Deep Sleep" as DeepSleep
    state "Intermittent Device Polling" as Polling
    state "Wake Up Main System" as WakeUp

    Decoupled --> DeepSleep: No_Device_Coupled_OR_Device_Full
    DeepSleep --> Polling: Timer_Expired_10s_Interval
    Polling --> WakeUp: Device_Detected (Capacitive/Pulsed Magnetic)
    Polling --> DeepSleep: No_Device_Detected
    WakeUp --> Coupled_Charging: Initiate_Full_Charge_Cycle (from AC Coupled)
    Coupled_Charging --> Decoupled: Charge_Complete_OR_Device_Removed
    WakeUp --> DeepSleep: Charger_Battery_Low_No_Device

Derivations for Claim 15: Inductive Battery Charging Method (Process-focused)

Claim 15 describes a method for inductive battery charging, including identifying coupling, determining low power, automatic engagement, automatic decoupling, and details on apparatus components, relay deactivation, power level determination, and feedback mechanisms.


2.1 Material & Component Substitution Derivatives (Method Perspective)

Derivative 2.1.1: Method for Adaptive GaN FET Switching Control

Enabling Description:
A method for automatically engaging and decoupling an inductive power apparatus (912) from an alternating current power source (102) utilizes an adaptive control algorithm for Gallium Nitride (GaN) Field-Effect Transistor (FET) switching arrays, as opposed to a solid-state or electromechanical relay. The method involves:

  1. Dynamically adjusting gate drive signals: The engage signal (from output buffer 1050 or USB module 1052) translates into precisely timed gate drive pulses for the GaN FETs to minimize switching losses during coupling and decoupling events, considering the instantaneous AC voltage zero-crossing points.
  2. Rapid fault isolation: In the event of an over-current or short-circuit detection (via high-speed current sense on the AC line), the method initiates an immediate (e.g., <500ns) shutdown sequence for the GaN FETs by rapidly pulling gate voltages to ground, ensuring swift decoupling of the AC source.
  3. Predictive component health monitoring: The method continuously monitors the temperature and switching cycles of the GaN FETs. If component degradation is predicted (e.g., increased on-resistance, slower switching), the method can alert for maintenance or implement a redundant path switchover.
flowchart TD
    A[Start Charge Cycle] --> B{Determine Battery Below Threshold}
    B -- Yes --> C{Generate Engage Signal (Output Buffer)}
    C --> D[Transmit Adaptive GaN Gate Drive]
    D -- Synchronize with AC Zero-Crossing --> E[GaN FET Switching Array Couples AC]
    E --> F[Monitor Charging & Faults]
    F -- Fault Detected --> G[Initiate GaN Rapid Shutdown]
    F -- Battery Full --> H{Generate Decouple Signal}
    H --> I[Transmit Adaptive GaN Gate Drive (Decouple)]
    I -- Synchronize with AC Zero-Crossing --> J[GaN FET Switching Array Decouples AC]
    J --> K[End Charge Cycle / Standby]
    G --> K

Derivative 2.1.2: Method for Multi-Chemistry Battery Profile Management

Enabling Description:
A method for determining the power level of a target device battery (901) and managing its charging threshold is extended to support multiple battery chemistries (e.g., Lithium-ion, Solid-State, Sodium-ion, Zinc-air). This method, executed by the processor (1044) and battery monitor (1046) within the target device (916), involves:

  1. Automatic chemistry identification: Upon connection, the method queries battery management system (BMS) registers or analyzes initial charge/discharge characteristics to identify the battery chemistry and capacity.
  2. Adaptive charging profiles: Based on the identified chemistry, the method loads a corresponding set of charging thresholds (lower charging threshold, desired threshold power level), voltage/current curves, and temperature limits from an internal database.
  3. Dynamic threshold adjustment: The method dynamically adjusts the charging thresholds and rates based on real-time battery health data (e.g., internal resistance, cycle count) and environmental conditions (e.g., ambient temperature), optimizing for both charging speed and battery longevity across different chemistries.
  4. Supplemental power source management: The method also intelligently manages the supplemental power source (1048) by considering its specific chemistry and state, e.g., prioritizing charging for a supercapacitor-based supplemental source during high power demands.
flowchart TD
    A[Target Device Connected] --> B{Read Battery BMS Data}
    B -- Identify Chemistry (Li-ion, Solid-State, Na-ion) --> C{Load Chemistry-Specific Profile}
    C --> D[Set Lower Charging Threshold & Desired Threshold]
    D --> E{Monitor Battery Power Level (Processor/Battery Monitor)}
    E -- Real-time Health / Temp --> D
    E -- Below Lower Threshold? --> F{Initiate AC Coupling (Claim 15 Step 3)}
    E -- Reached Desired Threshold? --> G{Initiate AC Decoupling (Claim 15 Step 4)}
    F --> H[Begin Charge Cycle]
    G --> I[End Charge Cycle]

2.2 Operational Parameter Expansion Derivatives (Method Perspective)

Derivative 2.2.1: Method for Dynamic Resonant Frequency Tracking

Enabling Description:
A method for automatically engaging and decoupling an inductive power apparatus (912) from an alternating current power source (102) in a high-power, variable-coupling environment (e.g., EV charging) incorporates dynamic resonant frequency tracking. This method uses the target device (916) and inductive power apparatus (912) to:

  1. Sweep and identify resonance: Prior to engagement, the inductive power apparatus emits low-power, swept frequency signals. The target device's connection module (918) measures the received signal strength and phase, and transmits this feedback (1040) to the apparatus.
  2. Tune and engage: The apparatus's activation module (922) analyzes the feedback to determine the optimal resonant frequency for the current coupling distance and alignment. It then tunes its internal power inverter (feeding the transformer 104) to this frequency before fully engaging the AC power source (102) via the separation module (334).
  3. Continuous adjustment: During charging, the method continuously monitors the inductive link efficiency and temperature. If detuning or reduced efficiency is detected (e.g., due to movement of the target device), the method dynamically adjusts the operating frequency to maintain optimal power transfer.
  4. Resonant decoupling: For decoupling, the method reduces the transmit power, broadens the frequency sweep, and then disengages the AC source, minimizing electromagnetic interference (EMI) during transition.
sequenceDiagram
    participant APA as Inductive Power Apparatus
    participant TD as Target Device
    participant AC as AC Source

    APA->>TD: Low Power Frequency Sweep (Pre-Engagement)
    TD->>APA: Feedback Signal (Resonance Peak)
    APA: Analyze Feedback, Tune Inverter
    APA->>AC: Request AC Coupling (Activation Module)
    AC->>APA: AC Coupled
    APA->>TD: High Power Inductive Transfer (Optimal Frequency)
    loop Charging Cycle
        APA->>TD: Monitor Efficiency
        TD->>APA: Report Power Received
        APA: Adjust Frequency if Detuned
    end
    TD->>APA: Battery Full (Monitoring Module)
    APA->>AC: Request AC Decoupling (Separation Module)
    AC->>APA: AC Decoupled

Derivative 2.2.2: Method for Distributed Energy Micro-Grid Integration

Enabling Description:
A method for inductive battery charging is implemented within a distributed energy micro-grid, where the inductive power apparatus (912) acts as a flexible load/source. The method involves:

  1. Grid condition awareness: The monitoring module (920) and activation module (922) within the target device (916) (or a central micro-grid controller) receive real-time data on micro-grid generation (e.g., solar, wind), load demand, and available storage capacity.
  2. Dynamic charging priority: If the micro-grid experiences high renewable generation and low demand, the method proactively engages the inductive power apparatus (912) to absorb excess energy, even if the target device battery (901) is not critically low (above the typical lower charging threshold). This stores energy in distributed target devices, acting as a virtual battery for the grid.
  3. Demand-response decoupling: Conversely, during periods of low renewable generation or high grid demand, the separation module (334) can be instructed to decouple the inductive power apparatus (912) from the AC source (102), even if the target device battery is not yet fully charged, to shed non-critical load and prioritize essential services within the micro-grid.
  4. Bi-directional power flow: The method can also extend to allow the target device battery to selectively discharge back into the micro-grid via the inductive link and rectification circuit (106) if needed, acting as a temporary power buffer.
flowchart TD
    A[Micro-Grid Controller] -- Real-time Data --> B(Monitoring Module / Activation Module)
    B -- Analyze Grid Status --> C{Decision: Charge, Decouple, or Hold}
    C -- Charge (High Gen / Low Demand) --> D[Engage AC (Inductive Apparatus)]
    D --> E[Target Device Charging]
    C -- Decouple (Low Gen / High Demand) --> F[Decouple AC (Inductive Apparatus)]
    E -- Battery Full --> F
    F --> G[Target Device Charged / Standby]
    C -- Hold --> G

2.3 Cross-Domain Application Derivatives (Method Perspective)

Derivative 2.3.1: Method for Automated Tool Charging in Robotics Manufacturing

Enabling Description:
A method for inductive battery charging is applied to automated tool charging in a robotics manufacturing environment. The method is used to manage the power levels of batteries integrated into robotic end-effectors or mobile robotic platforms.

  1. Automated docking and detection: The process begins with a robotic arm or mobile platform executing a docking maneuver to bring its end-effector/mobile base into precise alignment with a static inductive charging pad (the inductive power apparatus 912). Vision systems and tactile sensors on the robot (acting as the connection module 918) identify coupling.
  2. Predictive maintenance charging: The robot's onboard controller (processor 1044 and battery monitor 1046) determines its battery power level. However, the "lower charging threshold" and "desired threshold power level" are not static but are dynamically determined based on the robot's upcoming work schedule, predicted tool usage, and maintenance cycles (e.g., if a long shift is planned, it will charge to 95%; if a short break, only to 70%).
  3. Optimized energy consumption: The activation module (922) automatically engages the AC power source (102) for the inductive charger, only when required by the predictive schedule or actual low battery, to minimize overall facility energy consumption. The separation module (334) decouples when the dynamically determined desired level is reached, preventing trickle charging losses.
  4. Fault handling and safety: If a robot fails to properly dock or an inductive coupling fault is detected, the method immediately aborts the charging sequence and signals an alert to the central manufacturing execution system (MES), ensuring operational safety.
sequenceDiagram
    participant Robot as Autonomous Robot
    participant Charger as Inductive Charging Pad
    participant MES as Manufacturing Execution System

    Robot->>Charger: Docking Maneuver (Vision/Tactile Sensors)
    Charger->>Robot: Confirm Coupling (Connection Module)
    Robot->>MES: Request Charging Data (Current Task, Schedule)
    MES->>Robot: Provide Optimized Charge Parameters (Thresholds)
    Robot: Battery Below Threshold (Monitoring Module)
    Robot->>Charger: Initiate Charge Request
    Charger->>Charger: Engage AC (Activation Module)
    Charger->>Robot: Begin Inductive Charge
    loop Charging
        Robot->>Charger: Report Battery Status
        Charger->>Robot: Adjust Power if Needed
    end
    Robot->>Charger: Desired Charge Level Reached
    Charger->>Charger: Decouple AC (Separation Module)
    Robot->>MES: Report Charge Complete
    Robot->>Robot: Undock / Resume Task

Derivative 2.3.2: Method for Sub-Surface Environmental Sensor Charging

Enabling Description:
A method for inductive battery charging is applied to power sub-surface environmental sensors (e.g., for geological monitoring, soil moisture tracking in smart agriculture, or underwater acoustic sensors).

  1. Deployment and remote activation: Sub-surface inductive power receivers (target devices 916) with integrated batteries (901) are deployed. An above-ground or surface-level inductive power transmitter (inductive power apparatus 912) is positioned directly above the sensor. The connection module (918) uses a localized electromagnetic field disturbance detection to identify coupling through soil or water.
  2. Adaptive data collection and charge: The method determines the power level of the sensor's battery via a low-frequency telemetry link (supplemental power source 1048, drawing from the sensor's own battery). The "lower charging threshold" is dynamically adjusted based on the required operational lifespan for data collection (e.g., if a critical event like seismic activity is predicted, the sensor ensures a higher minimum charge).
  3. Environmentally optimized charging: The activation module (922) automatically engages the AC power source (102) to the transmitter only when needed. The separation module (334) decouples when the desired charge level is reached or if environmental conditions (e.g., severe weather impacting solar panels powering the AC source, or detection of sensitive wildlife in the area) warrant a temporary halt in transmission. This minimizes environmental impact and optimizes energy usage.
flowchart TD
    A[Above-Surface Inductive Transmitter] --> B{Sub-Surface Sensor Device}
    B -- Telemetry (Low Freq) --> A
    B -- Battery Monitor --> C[Monitoring Module (Sensor)]
    C -- Power Level Below Threshold --> D[Activation Module (Transmitter)]
    D -- Engage AC Source --> E[AC Power Source]
    E -- Inductive Power --> B
    C -- Desired Level Reached --> F[Separation Module (Transmitter)]
    F -- Decouple AC Source --> E

2.4 Integration with Emerging Tech Derivatives (Method Perspective)

Derivative 2.4.1: Method for AI-Reinforced Battery Management

Enabling Description:
A method for inductive battery charging integrates AI reinforcement learning (RL) into the battery management process. The RL agent, running on the target device's processor (1044), observes battery state (charge, temperature, degradation), charger availability, and predicted future usage (derived from user patterns or external data).

  1. State-action-reward learning: The agent learns optimal charging actions (e.g., "charge immediately," "delay charge," "trickle charge," "discharge slightly to prolong battery life") by evaluating rewards (e.g., battery longevity, energy cost savings, user satisfaction from always-available power) and penalties (e.g., vampiric loss, accelerated degradation).
  2. Dynamic threshold setting: Based on the RL agent's policy, the "lower charging threshold" and "desired threshold power level" are not fixed but are dynamically determined and communicated to the activation (922) and separation (334) modules, respectively. This allows for highly nuanced charging decisions.
  3. Proactive engagement/decoupling: The method enables the system to proactively engage the AC source to "top-off" the battery before a critical usage period (even if slightly above the default lower threshold) or to decouple early if extended idle time is predicted, solely based on the AI's learned policy, going beyond simple threshold logic.
sequenceDiagram
    participant RL_Agent as AI RL Agent (Processor 1044)
    participant BMS as Battery Monitor 1046
    participant Charger_Logic as Act./Sep. Modules (922, 334)
    participant AC as AC Source

    RL_Agent->>BMS: Request Battery State
    BMS->>RL_Agent: Current_SoC, Temp, Health
    RL_Agent: Observe (State), Predict (Future Usage)
    RL_Agent->>Charger_Logic: Select Action (e.g., "Engage AC Now")
    Charger_Logic->>AC: Send Engage/Decouple Command
    AC->>Charger_Logic: AC Status Update
    Charger_Logic->>RL_Agent: Report Action Outcome (Reward/Penalty)
    RL_Agent: Update Policy (Reinforcement Learning)
    Note over RL_Agent,AC: Continuous Learning & Optimization

Derivative 2.4.2: Method for Digital Twin-Enabled Predictive Maintenance

Enabling Description:
A method for inductive battery charging utilizes a digital twin of both the inductive power apparatus (912) and the target device battery (901).

  1. Real-time data synchronization: The physical inductive power apparatus and target device constantly stream operational data (e.g., charging current, voltage, temperature, internal resistance, switching cycles of the relay) to a cloud-based digital twin instance.
  2. Predictive fault detection: The digital twin employs machine learning algorithms to analyze this real-time and historical data, simulating potential degradation or failure modes (e.g., relay contact wear, transformer winding insulation breakdown, battery cell imbalance).
  3. Proactive maintenance & adjustment: If the digital twin predicts an imminent component failure in the inductive power apparatus, the method (via the monitoring module 920 and activation/separation modules 922, 334) can proactively modify charging parameters (e.g., reduce maximum charge rate, increase safety thresholds) or schedule a preventative decoupling and alert for maintenance before an actual failure occurs, extending system lifespan and preventing safety incidents. This predictive capability influences the "desired charging state" determination.
graph TD
    Physical_Charger[Inductive Power Apparatus] -- Stream Data --> Digital_Twin[Cloud Digital Twin]
    Physical_Device[Target Device / Battery] -- Stream Data --> Digital_Twin
    Digital_Twin -- ML Analysis --> Predictive_Insights[Predictive Faults / Degradation]
    Predictive_Insights --> Control_Action[Adaptive Charge Control]
    Control_Action -- Adjust Parameters --> Physical_Charger
    Control_Action -- Adjust Thresholds --> Physical_Device
    Physical_Charger -- Engage/Decouple AC --> AC_Source[AC Power Source]

2.5 The "Inverse" or Failure Mode Derivatives (Method Perspective)

Derivative 2.5.1: Method for Graceful Degraded Charging Mode

Enabling Description:
A method for inductive battery charging includes a graceful degraded charging mode to maintain partial functionality under non-critical fault conditions or resource constraints.

  1. Fault detection and classification: The method, through the monitoring module (920), identifies various fault conditions (e.g., partial sensor failure in the connection module 918, minor over-temperature in the transformer 104, reduced efficiency in the rectification circuit 106, or peak grid demand). It classifies these as "degraded" (non-critical) or "critical" (requiring full shutdown).
  2. Adaptive parameter modification: For "degraded" faults, the method does not fully decouple the AC source (102) but instead modifies charging parameters. For example, if a minor overheating in the inductive power apparatus (912) is detected, the method will reduce the charging current by 50% and extend the charging duration, thereby reducing heat generation while still providing power.
  3. Limited functionality mode: If the supplemental power source (1048) in the target device (916) is critically low, and the inductive link is suboptimal (e.g., poor alignment causing reduced efficiency), the method can initiate a "limited functionality" or "emergency charge" mode. In this mode, the target device temporarily disables non-essential functions to conserve power, allowing even a suboptimal inductive charge to provide enough energy for essential operations or communication before a full charge can be achieved.
flowchart TD
    A[Start Charge Cycle] --> B{Monitor System Health & Env.}
    B -- Fault Detected --> C{Classify Fault (Degraded / Critical)}
    C -- Critical --> D[Emergency Decouple AC (Full Shutdown)]
    C -- Degraded --> E[Enter Degraded Charging Mode]
    E --> F{Adjust Charging Parameters (e.g., Current, Duration)}
    F --> G[Continue Charging (Reduced Rate)]
    G -- Desired Charge Level Reached --> H[Decouple AC]
    G -- Critical Fault during Degraded Mode --> D
    E -- Target Device Critically Low & Suboptimal Link --> I[Activate Limited Functionality Mode (Device)]
    I --> F

Derivations for Claim 20: Inductive Battery Charging System (Refined Hardware-focused)

Claim 20 refines the system of Claim 1, specifically emphasizing a mobile device as the target device and a sense feedback loop to identify coupling to an AC power source. Many derivatives from Claim 1 are directly applicable. Here, I will add specific considerations for the "mobile device" and the "sense feedback loop" aspect.


3.1 Material & Component Substitution Derivatives

Derivative 3.1.1: Piezoelectric-Based Sense Feedback Loop for Mobile Device Coupling

Enabling Description:
In the connection module (918) of the target mobile device (916), the sense feedback loop (1154) is implemented using an array of embedded piezoelectric sensors integrated directly into the mobile device's casing and the inductive charging surface. When the mobile device is placed onto the charging apparatus, the minute pressure or vibration caused by coupling (even light contact) generates a unique electrical signal from the piezoelectric array. This signal is fed into the input buffer (1038) and processed by the interrupt controller module (1042) to confirm physical coupling. This replaces reliance on purely electrical shorting or power detection for initial coupling confirmation, offering a robust and low-power mechanical feedback mechanism. The inductive power apparatus's transformer (104) is manufactured with a nanocrystalline composite core for enhanced performance with mobile device form factors. The separation module (334) can utilize micro-electromechanical systems (MEMS) switches for silent, rapid AC decoupling suitable for consumer electronics.

graph TD
    MobileDevice(Mobile Device 916) --> PiezoArray[Piezoelectric Sensor Array (Sense Feedback Loop 1154)]
    ChargingSurface(Inductive Charging Surface) --> PiezoArray
    PiezoArray --> InputBuffer[Input Buffer 1038]
    InputBuffer --> InterruptController[Interrupt Controller Module 1042]
    InterruptController --> Processor[Processor 1044 (Monitoring Module 920)]
    Processor -- "Engage/Decouple" --> ActivationSeparation[Activation/Separation Modules (922, 334)]
    ActivationSeparation --> MEMS_Switch[MEMS AC Switch]
    MEMS_Switch --> AC_Source[AC Power Source 102]
    AC_Source -- Power --> InductiveApparatus[Inductive Power Apparatus]
    InductiveApparatus -- Inductive Field --> MobileDevice

Derivative 3.1.2: Liquid Metal Contacts for Inductive Coil Shielding

Enabling Description:
To improve the efficiency and safety of the inductive power apparatus (912) for mobile devices, the transformer (104) and inductive coils are housed within a casing that includes dynamically configurable liquid metal (e.g., Gallium alloy) shielding. This liquid metal is contained in microchannels and can be actuated by micro-pumps or electromagnets. When the connection module (918) identifies a target mobile device (916) is coupled, the liquid metal is strategically flowed to form a focused magnetic field path around the coils, reducing stray electromagnetic fields and increasing coupling efficiency. When the mobile device is decoupled or the AC source (102) is disengaged by the separation module (334), the liquid metal reforms to a wider, passive shielding configuration, minimizing ambient magnetic field leakage. The opto-coupled relay (462) in the separation module is enhanced with a redundancy circuit using a secondary electromechanical relay for failsafe AC disconnection.

classDiagram
    class InductivePowerApparatus {
        + Transformer 104
        + InductiveCoils
        + LiquidMetalShielding
        + MicroPump/Electromagnet
    }
    class TargetMobileDevice {
        + ConnectionModule 918
        + MonitoringModule 920
        + Processor 1044
        + BatteryMonitor 1046
    }
    class SeparationModule {
        + OptoCoupledRelay 462
        + ElectromechanicalRelay
    }
    InductivePowerApparatus "1" -- "*" TargetMobileDevice : inductively charges
    InductivePowerApparatus "1" -- "1" SeparationModule : AC control
    TargetMobileDevice -- ConnectionModule
    ConnectionModule -- InductivePowerApparatus : Detects presence & signals
    InductivePowerApparatus -- LiquidMetalShielding : controls field focus
    SeparationModule -- InductivePowerApparatus : engages/decouples AC

3.2 Operational Parameter Expansion Derivatives

Derivative 3.2.1: Multi-Frequency Adaptive Inductive Transfer for Mobile Devices

Enabling Description:
The inductive battery charging system operates across multiple distinct resonant frequencies (e.g., 100 kHz, 6.78 MHz, 13.56 MHz, 27.12 MHz) to accommodate various mobile device standards (e.g., Qi, AirFuel) and optimize power transfer based on coupling distance and load requirements. The inductive power apparatus (912) includes a multi-resonant inverter. The connection module (918) within the mobile device (916) initiates a handshake protocol to negotiate the optimal charging frequency. The sense feedback loop (part of connection module 918) not only identifies coupling but also includes impedance matching circuitry that reports the optimal operating frequency back to the activation module (922) via the input buffer (1038) and interrupt controller (1042). The activation module then commands the multi-resonant inverter to switch to the negotiated frequency before coupling the AC power source (102). The monitoring module (920) continuously assesses charging efficiency. If efficiency drops below a threshold, the system can dynamically switch to an alternative frequency to improve power transfer, ensuring efficient charging while preventing vampiric losses.

stateDiagram-v2
    state "Charger Standby" as Standby
    state "Device Connected" as Connected
    state "Frequency Negotiation" as Negotiating
    state "Charging (Active Frequency)" as Charging
    state "Charging (Switching Frequency)" as Switching

    Standby --> Connected: Device Coupled (Sense Feedback)
    Connected --> Negotiating: Initiate Handshake
    Negotiating --> Charging: Optimal Frequency Agreed (e.g., 6.78MHz)
    Charging --> Switching: Efficiency Drop / Interference Detected
    Switching --> Charging: New Optimal Frequency (e.g., 13.56MHz)
    Charging --> Connected: Battery Full
    Connected --> Standby: Device Decoupled
    Switching --> Standby: Device Decoupled

Derivative 3.2.2: Extreme Environment Mobile Device Charging (e.g., Sub-Zero Arctic, Desert Heat)

Enabling Description:
This inductive charging system is designed for mobile devices (916) operating in extreme environments, such as sub-zero arctic temperatures (-40°C) or desert heat (+60°C). The inductive power apparatus (912) features a thermally managed enclosure with active heating/cooling elements (e.g., Peltier modules) and robust insulation. The mobile device's battery monitor (1046) and processor (1044) within the monitoring module (920) continuously send battery temperature data. The "charging threshold" and "desired charging state" are dynamically adjusted based on the ambient and battery temperatures. For instance, in sub-zero conditions, the activation module (922) first triggers pre-heating of the inductive charging surface and the mobile device battery before coupling the AC power source (102) for charging. In extreme heat, the separation module (334) will proactively decouple the AC source if battery temperature approaches unsafe limits, even if not fully charged, preventing thermal damage. The sense feedback loop (1154) is hardened against environmental ingress and uses robust connection detection (e.g., high-reliability inductive proximity sensors).

flowchart TD
    A[Mobile Device Coupled (Extreme Env.)] --> B{Monitor Battery Temp & Ambient Temp}
    B -- Temp OK --> C{Monitor Battery Power Level (Monitoring Module)}
    B -- Temp Low (<0C) --> D[Pre-Heat Charger/Device]
    B -- Temp High (>45C) --> E[Reduce Charge Rate OR Proactive Decouple]
    C -- Below Charging Threshold --> F[Activate AC Coupling (Activation Module)]
    F --> G[Charge Battery (Temp-Adapted Rate)]
    G -- Desired Charging State Reached OR Over-Temp --> H[Decouple AC (Separation Module)]
    H --> I[End Charge / Standby]
    D --> F
    E --> H

3.3 Cross-Domain Application Derivatives

Derivative 3.3.1: Wearable Technology Charging in Healthcare Settings

Enabling Description:
The inductive charging system is specifically adapted for charging wearable medical devices (e.g., continuous glucose monitors, smart patches, hearing aids) in clinical or home healthcare settings. The inductive power apparatus (912) is integrated into unobtrusive surfaces like hospital bed rails, bedside tables, or bathroom counters, and is designed to be easily cleanable and biocompatible. The target device (916) is the wearable sensor, often with a miniaturized battery (901). The connection module (918) in the wearable uses a very low-power magnetic resonance detection to confirm precise coupling, critical for efficient power transfer to small devices. The sense feedback loop (1154) continuously verifies the presence of the wearable and its charging status. The monitoring module (920) in the wearable reports battery level and critical physiological data (e.g., patient vital signs) to a central healthcare gateway. The activation module (922) automatically engages the AC power source (102) when the wearable's battery is low, and the separation module (334) decouples when charged, with additional safety protocols to prevent overcharging that could impact patient health data integrity. The system can prioritize charging specific devices based on patient needs.

sequenceDiagram
    participant Wearable as Wearable Medical Device
    participant Pad as Inductive Charging Pad (Healthcare)
    participant Gateway as Healthcare Gateway

    Wearable->>Pad: Place on Pad (Magnetic Resonance Detection)
    Pad->>Wearable: Confirm Coupling (Connection Module)
    Wearable: Battery Below Threshold (Monitoring Module)
    Wearable->>Pad: Request Charge (includes Patient Data priority)
    Pad->>Gateway: Report Device Charge Request
    Gateway->>Pad: Authorize Charge (based on priority)
    Pad->>Pad: Engage AC (Activation Module)
    Pad->>Wearable: Begin Inductive Charge
    loop Charging
        Wearable->>Pad: Report Battery Status / Vitals
    end
    Wearable->>Pad: Desired Charge State Reached
    Pad->>Pad: Decouple AC (Separation Module)
    Pad->>Gateway: Report Charge Complete
    Wearable->>Wearable: Continue Monitoring

Derivative 3.3.2: Underwater Robotics and Sensor Network Charging

Enabling Description:
An inductive battery charging system is adapted for autonomous underwater vehicles (AUVs) and fixed underwater sensor nodes. The inductive power apparatus (912) is a subsea charging station, designed to be pressure-tolerant and corrosion-resistant. The target device (916) is an AUV or sensor node. The connection module (918) employs acoustic ranging and precise docking mechanisms to ensure robust coupling even in strong currents. The sense feedback loop (1154) uses acoustic signals or low-frequency magnetic signatures to confirm proximity and initial coupling through seawater. The monitoring module (920) in the AUV/sensor (processor 1044 and battery monitor 1046) monitors deeply-discharged specialized subsea battery packs (e.g., pressure-compensated Li-ion). The activation module (922) engages the (subsea-rated, isolated) AC power source (102) for the inductive apparatus when the AUV docks with a low battery. The separation module (334) decouples the AC source when charged, preventing continuous power draw and minimizing biofouling on active electrical components. This also includes fail-safe decoupling if a leak or sensor fault is detected.

graph TD
    A[Surface Support / Ship] -- Power Cable --> B(Subsea AC Source 102)
    B -- Isolated Power --> C{Subsea Inductive Charging Station 912}
    C -- Acoustic Ranging/Docking --> D(AUV / Sensor Node 916)
    D -- Inductive Receiver --> E[AUV/Sensor Power Mgmt (Monitor. Mod. 920)]
    E -- Battery Status --> C
    C -- Engagement Signal --> B
    C -- Decoupling Signal --> B
    D -- Acoustic/Magnetic Feedback --> C

3.4 Integration with Emerging Tech Derivatives

Derivative 3.4.1: Edge AI-Powered Context-Aware Charging for Mobile Devices

Enabling Description:
The mobile device (916) integrates an edge AI processor (co-located with processor 1044) that enables context-aware charging decisions. The monitoring module (920) leverages this edge AI to analyze various contextual data streams from the mobile device (e.g., user's current activity, location history, calendar, ambient light, microphone input for environmental sound classification). The "charging threshold" is not a fixed percentage but an AI-determined optimal level based on the current context (e.g., if the user is at home and device usage is low, the AI might allow the battery to dip to 30% before charging; if the user is about to leave for a long trip, it prioritizes a full charge even from 70%). The activation module (922) and separation module (334) act upon these dynamic, AI-driven thresholds, rather than static pre-set values. The sense feedback loop (1154) is augmented with an NFC chip, allowing the charging pad to receive a cryptographic token from the mobile device to verify device authenticity before charging is initiated, preventing unauthorized power draw.

sequenceDiagram
    participant Mobile as Mobile Device 916 (Edge AI)
    participant Charger as Inductive Charger 912
    participant AC as AC Source

    Mobile->>Charger: Place/Couple (Sense Feedback, NFC Auth)
    Charger->>Mobile: Confirm Coupling & Authenticity
    Mobile: Collect Contextual Data (Activity, Location, Calendar)
    Mobile: Edge AI determines Optimal Charging Thresholds (Monitoring Module)
    Mobile->>Mobile: Battery Below Optimal Threshold?
    alt Yes
        Mobile->>Charger: Request AC Engagement
        Charger->>AC: Engage_AC_Source (Activation Module)
        AC->>Charger: AC Enabled
        Charger->>Mobile: Begin Inductive Charge
    else No
        Mobile->>Mobile: Wait for Threshold / Context Change
    end
    loop Charging
        Mobile->>Mobile: Battery Reaches Optimal Desired State?
        alt Yes
            Mobile->>Charger: Request AC Decoupling
            Charger->>AC: Decouple_AC_Source (Separation Module)
            AC->>Charger: AC Disabled
            break
        end
    end

Derivative 3.4.2: Quantum-Resistant Cryptography for Secure Inductive Pairing

Enabling Description:
The communication within the inductive battery charging system, particularly the feedback signal (1040) transmitted via the input buffer (1038) and the engage signals from the output buffer (1050) or USB module (1052), is secured using quantum-resistant cryptographic algorithms (e.g., lattice-based cryptography, hash-based signatures). This is critical for preventing malicious actors from impersonating a target mobile device (916) to force AC coupling and draw power (vampiric attack), or to interfere with charging operations. Each target mobile device and inductive power apparatus (912) contains a secure element (e.g., a hardware security module) that performs cryptographic key management and signs/verifies all control signals. The sense feedback loop (1154) is integrated with a unique physical unclonable function (PUF) within the mobile device, generating a challenge-response pair during initial coupling, further strengthening anti-counterfeiting measures. The interrupt controller module (1042) only processes feedback signals that pass cryptographic verification.

sequenceDiagram
    participant Mobile as Target Mobile Device 916
    participant Charger as Inductive Power Apparatus 912
    participant AC as AC Power Source

    Mobile->>Charger: Coupling Detection (Sense Feedback + PUF Challenge)
    Charger->>Mobile: PUF Response Request
    Mobile->>Charger: PUF Response & Cryptographic Handshake (Quantum-Resistant)
    Charger->>Mobile: Verify Authentication
    alt Authentication Failed
        Charger->>Mobile: Reject Connection
        AC->>AC: AC Stays Decoupled
    else Authentication Success
        Mobile: Battery Below Threshold (Monitoring Module)
        Mobile->>Charger: Signed Charge Request (Quantum-Resistant)
        Charger->>Mobile: Verify Request
        Charger->>AC: Engage AC Source (Activation Module)
        AC->>Charger: AC Coupled
        Charger->>Mobile: Begin Inductive Charge
        Mobile: Desired Charge State Reached
        Mobile->>Charger: Signed Decouple Request (Quantum-Resistant)
        Charger->>AC: Decouple AC Source (Separation Module)
        AC->>AC: AC Decoupled
    end

3.5 The "Inverse" or Failure Mode Derivatives

Derivative 3.5.1: Device-Initiated "Safe-Drop" Decoupling for Mobile Devices

Enabling Description:
The inductive battery charging system includes a "safe-drop" decoupling mechanism. The target mobile device (916) includes an accelerometer and gyroscope (part of the monitoring module 920, feeding into the processor 1044). If the mobile device detects rapid motion indicative of being accidentally dropped or rapidly removed from the charging pad while charging (e.g., acceleration exceeding 2G, angular velocity exceeding 360 deg/s), the mobile device's processor immediately sends a "safe-drop" command via the USB module (1052) or output buffer (1050) to the separation module (334). This command forces an immediate decoupling of the AC power source (102) from the inductive power apparatus (912), preventing arcing or damage to the device's charging port or the inductive coils as the device separates from the charger. This is an additional layer of safety beyond the "desired charging state" decoupling. The electromechanical relay (as allowed by Claim 20) is preferred here for its robust physical disconnection.

flowchart TD
    A[Mobile Device Charging] --> B{Monitor Accelerometer/Gyro (Monitoring Module)}
    B -- Sudden Motion Detected --> C[Generate "Safe-Drop" Command (Processor)]
    C --> D[Transmit Command (USB Module/Output Buffer)]
    D --> E[Separation Module 334]
    E -- Triggers --> F[Electromechanical Relay Decouples AC]
    F --> G[AC Power Source 102]
    G -- Power Off --> H[Inductive Power Apparatus 912]
    H --> I[Charging Halted / Device Dropped]

Derivative 3.5.2: Network-Triggered "Grid Protection" Decoupling for Mobile Devices

Enabling Description:
The inductive battery charging system can be commanded to decouple its AC power source (102) in response to external grid signals, even if the mobile device (916) is not yet fully charged. The inductive power apparatus (912) includes a network interface (e.g., Wi-Fi, Ethernet) connected to a smart grid communication network. If the local grid operator transmits a "load shedding" or "grid stabilization" command (e.g., during peak demand or a power outage warning), the apparatus's activation module (922) receives this command. The separation module (334) then immediately decouples the AC power source from the inductive power apparatus, prioritizing grid stability over individual device charging. The mobile device's monitoring module (920) is informed of this forced decoupling and adjusts its battery usage expectations accordingly. The system will only re-engage the AC source when a "grid restored" signal is received or after a pre-defined safety delay.

sequenceDiagram
    participant Grid as Smart Grid Operator
    participant Charger as Inductive Power Apparatus 912
    participant Mobile as Mobile Device 916

    Grid->>Charger: Transmit "Load Shedding" Command
    Charger->>Charger: Receive Command (Network Interface)
    Charger->>Charger: Initiate Decoupling (Separation Module)
    Charger->>AC: Decouple AC Source
    AC->>Charger: AC Disabled
    Charger->>Mobile: Notify "Forced Decoupling"
    Mobile->>Mobile: Adjust Power Management (Monitoring Module)
    Note over Grid,Charger: Grid Stabilization Event
    Grid->>Charger: Transmit "Grid Restored" Command
    Charger->>Charger: Receive Command
    Mobile->>Charger: Battery Below Threshold (Monitoring Module)
    Charger->>AC: Engage AC Source (Activation Module)
    AC->>Charger: AC Enabled
    Charger->>Mobile: Resume Inductive Charge

Combination Prior Art Scenarios with Open-Source Standards

Here are at least 3 "Combination Prior Art" scenarios where the principles of US Patent 8358103 are combined with existing open-source standards.

1. Integration with Qi Wireless Power Standard (WPC)

Enabling Description:
The core invention of US8358103, which automatically couples and decouples an AC power source from an inductive power apparatus based on the target device's battery level to prevent vampiric power loss, is implemented within a system fully compliant with the Qi Wireless Power Consortium (WPC) standard (e.g., Qi v1.2.x or v1.3.x, an open-source standard for inductive power transfer).

The inductive power apparatus (912) functions as a Qi-certified Power Transmitter (PTx). The connection module (918) and sense feedback loop (1154) leverage the Qi communication protocol (e.g., using FSK modulation over the power transfer coil) for device detection, identification, and authentication. When a Qi-compatible mobile device (916, acting as a Power Receiver - PRx) is placed on the PTx, the Qi handshake sequence identifies coupling. The monitoring module (920) within the PRx uses the standard Qi "End Power Transfer" (EPT) packet mechanism to report its battery charge level and "desired charging state" (e.g., "fully charged," "battery full," or specific SoC percentages) back to the PTx.

The activation module (922) of the PTx receives a "low battery" signal from the PRx (e.g., if Qi reports SoC < threshold) and automatically engages the AC power source (102) to the PTx via the separation module (334). Conversely, upon receiving an EPT packet indicating a "battery full" state, the separation module automatically decouples the AC power source, eliminating the quiescent power draw (vampiric loss) that often plagues always-on Qi chargers. The bypass module (336) could be implemented as a soft button that forces an initial Qi ping to wake up the PTx.

sequenceDiagram
    participant Qi_PRx as Qi Mobile Device (PRx)
    participant Qi_PTx as Qi Charger (PTx)
    participant AC_Source as AC Power Source

    Qi_PRx->>Qi_PTx: Place on Pad / Ping for Qi Device
    Qi_PTx->>Qi_PRx: Initiate Qi Handshake (Connection Module)
    Qi_PRx: Battery Below Threshold (Monitoring Module)
    Qi_PRx->>Qi_PTx: Transmit "Power Request" / "Low SoC" (Qi Communication)
    Qi_PTx->>AC_Source: Engage AC (Activation Module)
    AC_Source->>Qi_PTx: AC Coupled
    Qi_PTx->>Qi_PRx: Begin Qi Inductive Charge
    loop Charging
        Qi_PRx->>Qi_PTx: Transmit Charge Status (Qi Communication)
    end
    Qi_PRx->>Qi_PTx: Transmit "End Power Transfer" (EPT) / "Battery Full"
    Qi_PTx->>AC_Source: Decouple AC (Separation Module)
    AC_Source->>Qi_PTx: AC Decoupled

2. Integration with Open Charge Point Protocol (OCPP) for EV Charging

Enabling Description:
The principles of US8358103 are applied to electric vehicle (EV) inductive charging infrastructure, integrating with the Open Charge Point Protocol (OCPP) v1.6 or v2.0.1 (an open-source application protocol for communication between EV charging stations and a central management system).

The inductive power apparatus (912) is an EV inductive charging station (Charge Point - CP). The target device (916) is an EV equipped with an inductive charging receiver. The connection module (918) and sense feedback loop (1154) detect the EV's physical coupling to the inductive charging lane/pad and establish a secure communication link (e.g., ISO 15118 Power Line Communication). The monitoring module (920) within the EV's Battery Management System (BMS, acting as processor 1044 and battery monitor 1046) determines the EV battery's State of Charge (SoC).

Crucially, this system communicates the EV's SoC and desired charging parameters (e.g., "charge to 80%," "charge by 5 PM") to the CP via an OCPP MeterValues or StatusNotification message containing the battery status. The CP's activation module (922) then transmits an OCPP StartTransaction request to the central Charge Point Management System (CSMS) indicating the need for charging. Upon authorization from the CSMS, the activation module automatically couples the high-power AC grid (102) to the inductive power apparatus. When the desired SoC is reached (reported via OCPP MeterValues), the separation module (334) initiates an OCPP StopTransaction and automatically decouples the AC grid connection, preventing prolonged standby power draw by the inductive coils and power electronics when not actively charging an EV.

sequenceDiagram
    participant EV as Electric Vehicle
    participant CP as Inductive Charge Point (OCPP)
    participant CSMS as Charge Point Mgmt System (OCPP)
    participant Grid as AC Power Grid

    EV->>CP: Dock/Align (Connection Module)
    CP->>EV: Establish Secure Comm. (ISO 15118)
    EV: Battery Below Threshold (Monitoring Module)
    EV->>CP: Transmit "SoC Low" / Desired Charge (OCPP MeterValues)
    CP->>CSMS: StartTransaction.req (includes EV ID, SoC)
    CSMS->>CP: StartTransaction.conf
    CP->>Grid: Engage AC (Activation Module)
    Grid->>CP: AC Coupled (High Power)
    CP->>EV: Begin Inductive Charge
    loop Charging
        EV->>CP: Transmit Real-time SoC (OCPP MeterValues)
    end
    EV->>CP: Desired SoC Reached (Monitoring Module)
    CP->>CSMS: StopTransaction.req (includes Energy Used)
    CSMS->>CP: StopTransaction.conf
    CP->>Grid: Decouple AC (Separation Module)
    Grid->>CP: AC Decoupled

3. Integration with MQTT for Smart Home Energy Management

Enabling Description:
The inductive battery charging system is integrated into a smart home environment, communicating via the MQTT (Message Queuing Telemetry Transport) protocol (an open-source lightweight messaging protocol for IoT).

The inductive power apparatus (912) and the target mobile device (916) are equipped with MQTT clients. The target mobile device's monitoring module (920) (processor 1044 and battery monitor 1046) periodically publishes its battery power level (e.g., SoC percentage) to a specific MQTT topic (e.g., home/charging/deviceA/battery_level) on the local smart home MQTT broker. The connection module (918) and sense feedback loop (1154) publish coupling status (e.g., home/charging/deviceA/status: coupled/decoupled).

A smart home energy management system (HEMS), subscribed to these topics, acts as the central intelligence. When the HEMS observes a device's battery level drop below a predefined "lower charging threshold" via MQTT, it publishes a command (e.g., home/charging/deviceA/command: engage) to the inductive power apparatus. The apparatus's activation module (922) subscribes to this command topic and, upon receiving the engage command, automatically couples the AC power source (102). When the HEMS detects the "desired threshold power level" is reached (again, via MQTT battery_level topic), it publishes a decouple command, triggering the apparatus's separation module (334) to automatically decouple the AC source. This allows for centralized, intelligent control of charging events, potentially integrating with energy pricing data (e.g., only charge when electricity is cheap) or renewable energy availability (e.g., charge during solar peak).

sequenceDiagram
    participant Mobile as Target Mobile Device 916 (MQTT Client)
    participant Charger as Inductive Power Apparatus 912 (MQTT Client)
    participant MQTT_Broker as MQTT Broker
    participant HEMS as Smart Home Energy Management System

    Mobile->>MQTT_Broker: Publish battery_level (Monitoring Module)
    Charger->>MQTT_Broker: Publish coupling_status (Connection Module)
    HEMS->>MQTT_Broker: Subscribe to battery_level, coupling_status
    activate HEMS
    HEMS: Detect Mobile Battery Below Threshold
    HEMS->>MQTT_Broker: Publish "engage" command for Charger
    deactivate HEMS
    Charger->>MQTT_Broker: Subscribe to command topic
    Charger->>Charger: Receive "engage" command (Activation Module)
    Charger->>AC_Source: Engage AC
    AC_Source->>Charger: AC Coupled
    Charger->>Mobile: Begin Inductive Charge
    loop Charging
        Mobile->>MQTT_Broker: Publish updated battery_level
    end
    activate HEMS
    HEMS: Detect Mobile Battery Reaches Desired Threshold
    HEMS->>MQTT_Broker: Publish "decouple" command for Charger
    deactivate HEMS
    Charger->>Charger: Receive "decouple" command (Separation Module)
    Charger->>AC_Source: Decouple AC
    AC_Source->>Charger: AC Decoupled

Generated 5/18/2026, 3:26:54 PM

Keep exploring

More patents asserted by Apple Inc.

Other patents in High-Tech (T)

See all High-Tech (T) patents →

This patent in court (3)

3 tracked lawsuits name US 8358103.