Last Updated: May 11, 2026

Patent: 10,392,349


✉ Email this page to a colleague

« Back to Dashboard


Summary for Patent: 10,392,349
Title:Azepane derivatives and methods of treating hepatitis B infections
Abstract: Provided herein are compounds useful for the treatment of HBV infection in a subject in need thereof, pharmaceutical compositions thereof, and methods of inhibiting, suppressing, or preventing HBV infection in the subject.
Inventor(s): Hartman; George D. (Lansdale, PA), Kuduk; Scott (Harleysville, PA)
Assignee: NOVIRA THERAPEUTICS, INC. (Doylestown, PA)
Application Number:15/852,755
Patent Claims:see list of patent claims
Patent landscape, scope, and claims summary:

United States Patent 10,392,349: Claim Scope and HBV Patent Landscape Critical Analysis

What does US 10,392,349 actually claim (and how broad is it)?

US 10,392,349 claims a family of small-molecule compounds defined by a large “Formula I” Markush framework, plus downstream protection for compositions and HBV treatment methods.

Claim set at a glance

Claim Category Core protection
1–11 Compounds (Formula I and subset refinements) Huge Markush space around substituent variables (R4, R1, R2, R7, R8, R11, R12, m, n, x, y) and ring-closure options (benzimidazole option via two R2 + phenyl fusion; R7/R8 option to cyclize)
12 Pharmaceutical composition Compound of claim 1 (or salt) + pharmaceutically acceptable carrier
13–20 Methods of treating HBV Administer therapeutically effective amount of claim 1 compound; optional combination therapy with specified HBV classes (polymerase inhibitors, interferons, vaccines, etc.)

The breadth is driven by Markush variables, not a single scaffold

Claim 1’s structure is anchored by “Formula I” with the key flexibility concentrated in:

  • R4: H or C1-C3 alkyl
  • R1 (independently at each occurrence): OH, halo, CN, NO2, C1-C6 alkyl, O-alkyl, heteroalkyl, O-heteroalkyl, C3-C10 cycloalkyl, C3-C10 heterocycloalkyl, aryl/heteroaryl, and multiple “alkyl-aryl/alkyl-heteroaryl” attachment classes, with each aryl/alkyl/heteroalkyl group optionally substituted 1–5 times with halo/OH/CN/NO2
  • R2: OH, halo, CN, NO2, R6 or OR6, where R6 mirrors the breadth of R1’s substituent categories; and a special case:
    • “or two R2 groups and the phenyl ring to which they are attached join to form benzimidazole.”
  • Cy: a defined bicyclic/locked heterocycle fragment (rendered in the claim as a structural drawing)
  • R7 and R8: independent selection among alkyl/aryl/heteroaryl and alkyl-aryl/alkyl-heteroaryl, with optional substitutions; or R7 and R8 join to form a 3- to 10-membered ring
  • R11: OH/halo/CN/NO2 plus oxygenated and acyl/alkoxy groups (including acyloxy: “OC(O)CH3”), and alkyl/heteroalkyl/cyclo/heterocycle/aromatic options, each with optionally substituted 1–5 times with halo/OH/CN/NO2
  • R12: H or C1-C6 alkyl
  • m/n/x/y: discrete enumerations (m 0–4; n 1–4; x 0–5; y 0–4)

Net effect: claim 1 is not just “a compound.” It is a template that can cover many thousands of hypothetical variants, provided they fit the specific structural skeleton and variable positions.

How narrower claims manage scope (Claims 2–11)

Claims 2–3, 4, 7–11 progressively narrow subsets:

  • Claim 2: tighter ranges on substituent multiplicity (example: option lists limited to 1–3 substitutions instead of 1–5; and smaller ranges for m/n/x/y)
  • Claim 3: even more constrained substituent sets (replaces some aromatic freedom with narrower OH/halo/alkyl/cycloalkyl options) and reduces substitution counts
  • Claim 4: locks R4 to H
  • Claim 5: restricts R7/R8 to “C1-C6 alkyl, phenyl, pyridyl, benzyl, or pyridylmethyl”
  • Claim 6: restricts R7/R8 to C1-C6 alkyl that cyclize into a 3- to 7-membered ring
  • Claim 7: narrows R1 to halo only and x to 1–3
  • Claim 8: defines a Formula II embodiment with X1 = halo
  • Claims 9–11: restrict R2 and/or R11 oxygenation/alkyl substituent patterns and reduce substitution counts (for the optional halo/OH substitution intensity)

Critical read: The claim set uses layered subsets that preserve the core scaffold while trimming chemical degrees of freedom. That pattern is consistent with a strategy to maintain enforceability even if a particular breadth challenge succeeds, because narrower dependent claims stay within the same general structural domain.


What is the HBV therapeutic claim scope (and where are the legal hooks)?

Claim 13: direct method-of-use

Claim 13 claims: “treating an HBV infection” by administering a therapeutically effective amount of the claim 1 compound.

This is broad because it is not restricted by:

  • genotype
  • line of therapy (naive vs treatment-experienced)
  • disease stage (e.g., compensated vs decompensated cirrhosis)
  • endpoint (viral load, ALT, seroconversion)

Claim 14: combination-therapy hook

Claim 14 adds: the method can include at least one additional therapeutic agent selected from an enumerated list including:

  • HBV polymerase inhibitor
  • immunomodulatory agents
  • pegylated interferon
  • viral entry inhibitor
  • viral maturation inhibitor
  • “literature-described capsid assembly modulator”
  • reverse transcriptase inhibitor
  • cyclophilin/TNF inhibitor
  • TLR-agonist
  • HBV vaccine
  • combinations

This claim is structured to capture multi-drug regimens without requiring the competitor to copy a specific regimen. It is also structured to be compatible with common standard-of-care combinations and real-world prescribing patterns.

Claims 15–20: exemplified classes expand coverage

Claims 15–20 further specify categories:

  • Claim 15: reverse transcriptase inhibitors enumerated (includes NRTIs such as zidovudine, lamivudine, entecavir, tenofovir, etc.)
  • Claims 16–19: interferon options including interferon-alpha variants and pegylated forms; explicit inclusion of “PEGASYS”
  • Claim 20: method can include HBV vaccine, nucleoside HBV inhibitor, interferon, or combinations

Critical read: The method claims are designed to be resilient against “hard design-arounds.” A competitor may avoid direct compound claim coverage by selecting a non-covered analog, but if the competitor is still using a compound that reads on the scaffold, these dependent method claims support additional leverage for enforcement in HBV combination contexts.


Where is the claim vulnerable: overbreadth vs enablement vs written description?

Without the specification text and example compounds, a full legal validity assessment cannot be completed from claims alone. However, the claim architecture itself creates predictable risk points.

1) Markush magnitude vs enabling disclosure

Claim 1 includes:

  • multiple positions with independent variable choices (R1, R2, R7/R8, R11)
  • broad substitution allowances (1–5 optional substituents on diverse rings)
  • multiple ring-forming options (benzimidazole formation from R2 pairs; R7/R8 cyclization into 3–10 membered ring)

The more positions that are independently variable with wide substitution sets, the harder it is for the patentee to justify a single teaching that enables the entire scope across all variants. This is a classic friction point for:

  • enablement under 35 USC 112(a)
  • written description support

2) Functional claim alignment to HBV efficacy

The claims state therapeutic use for “HBV infection” but do not, on their face, specify that the compounds have defined potency, specific targets, or particular mechanism-of-action in HBV.

If the spec does not provide robust, correlated activity data across the broad chemical space, the broad “treating HBV” use may be challenged as lacking adequate support for the whole set.

3) Combining many chemical classes with “optionally substituted” language

Claims that permit “optionally substituted 1–5 times” across aryl/heteroaryl rings plus multiple halo/OH/CN/NO2 substituent types can face prosecution-time scrutiny and litigation scrutiny when competitors argue that the patentee effectively claims large chemical territory without commensurate examples.

4) Potential indefiniteness risk from drawing-based variables

Formula claims that rely on multiple variables defined by drawings (Cy, R groups, and joined-ring definitions) can be attacked if the claim language does not clearly define boundaries between embodiments. In practice, courts often construe these using the specification and prosecution history. Absent those, risk remains for interpretation in dispute.


Patent landscape: how US 10,392,349 likely sits in HBV chemistry

The claim set is HBV-focused by method-of-use (claims 13–20), but the compound-level coverage is generic and not limited to a named HBV target class (polymerase, capsid assembly, entry, etc.). The enumerated combination agents in claim 14 include categories aligned with multiple HBV mechanisms.

Implication for landscape mapping

Given the combination list includes polymerase inhibitors, interferons, viral entry/maturation inhibitors, capsid assembly modulators, cyclophilin/TNF inhibitors, and TLR agonists, US 10,392,349 likely belongs to a broad HBV small-molecule program that can be positioned across combination regimens even if its own mechanism is distinct.

In landscape terms, this positions the patent as:

  • a compound patent (primary estate) with
  • method-of-use coverage that reinforces adoption in HBV combination therapy

How competitors can respond (design-around strategy)

Because claim 1 uses a Markush scaffold, design-around opportunities typically come from:

  • selecting alternative substituents at one of the enumerated variable positions that fall outside the allowed lists or optional substitution constraints
  • avoiding the ring-closure options (benzimidazole formation or R7/R8 cyclization) if those closures are critical to coverage
  • using prodrug or salt forms not encompassed by “pharmaceutically acceptable salts” if a specific counterion or salt form is needed for a specific product

However, the dependent claims still sweep many of the same chemical freedoms, making “simple changes” less likely to avoid coverage unless the change targets a key variable definition.


Claim coverage vs typical HBV competitors: practical enforcement logic

1) If the competitor’s candidate compound reads on Formula I

Then:

  • claim 1 (or claims 2–11 depending on which variable restrictions match) is directly implicated for compound infringement, and
  • claim 12 covers the marketed formulation for administration, and
  • claims 13–20 can be used to tie infringement to HBV treatment regimens, including commonly used combinations (polymerase inhibitors, pegylated interferons, vaccines, etc.).

2) If the competitor uses the compound only in combination therapy

Even if formulation or compound manufacture is disputed, method claims can create exposure if there is evidence of administration to individuals with HBV using a therapeutically effective amount.

Claim 14 is particularly enforcement-friendly because it does not require a specific second agent; it requires only that the additional agent is selected from a listed class.


What to watch in prosecution history and claim construction (deal-critical items)

Even without the patent specification and file history, the following items are “construction pressure points” created by the claim language:

  1. Definition boundaries for each variable
    For example, “each R1 is independently… optionally substituted 1–5 times” means a competitor’s substituent selection will hinge on whether the group is considered “aryl/heteroaryl” vs “alkyl-(aryl)” and how substitution count is tallied.

  2. Ring closure conditions

    • “two R2 groups and the phenyl ring… join to form benzimidazole”
    • “R7 and R8 join to form a 3- to 10-membered ring”
      If a competitor’s compound uses a similar but non-identical ring topology, infringement hinges on whether it satisfies the join conditions exactly.
  3. O-alkyl vs C-linked alkyl distinctions
    Claims distinguish between alkyl, alkoxy (O-C1-C6 alkyl), and heteroalkoxy/heteroalkyl. These are often key to non-infringement design-arounds.

  4. R11 includes acyloxy (“OC(O)CH3”) This suggests the scaffold accommodates an acetylated oxygen substituent. If a competitor uses a different acyl group or a distinct prodrug strategy, they may argue outside the claimed oxy-acyl pattern.


Key Takeaways

  • US 10,392,349 is a broad Markush compound claim centered on Formula I with wide independent substituent variability across multiple positions (R1, R2, R7/R8, R11) and explicit ring-closure embodiments including benzimidazole and R7/R8 cyclization.
  • The patent extends coverage beyond compounds into formulation (claim 12) and HBV treatment methods (claims 13–20), with combination-therapy lists that are consistent with real-world HBV regimens.
  • The main legal risk for enforceability comes from classic Markush challenges: enablement/written description support for the breadth of substituted variants, and the correlation between chemical scope and HBV activity if the specification does not provide sufficiently representative examples.
  • For competitive strategy, design-arounds should focus on variable-definition boundaries (O- vs C-linkages, substitution-count limits, and exact ring-closure requirements) rather than on minor peripheral changes.

FAQs

  1. Is US 10,392,349 limited to a single HBV target (polymerase, capsid, entry)?
    No. The compound claims do not tie explicitly to a single target mechanism, while the method claims support HBV treatment generally and include combination classes spanning multiple mechanisms.

  2. Which claims provide the strongest enforcement leverage for combination therapy?
    Claim 14 plus claims 15–20. Claim 14’s enumerated “additional therapeutic agent” list enables linkage of administration to common HBV combination regimens without requiring a single named partner drug.

  3. What is the most common design-around path for Markush-heavy patents like claim 1?
    Breaking the claim’s variable definitions by changing linkage types (e.g., avoiding O-alkyl when C-linked alkyl is used), removing or altering ring-closure outcomes (benzimidazole or R7/R8 cyclization), or exceeding scope boundaries in optional substitution definitions.

  4. Do dependent claims narrow the patent enough to protect against a breadth attack?
    They reduce specific ranges (substitution counts and variable enumerations) and constrain subsets like R4 and R7/R8. They provide fallback positions if the broadest embodiment is narrowed in claim construction or invalidity arguments.

  5. Does the patent cover both compounds and salts?
    Yes. Claim 1 covers “the compound of Formula I or a pharmaceutically acceptable salt thereof,” and dependent method claims track the compound definition accordingly.


References

[1] United States Patent 10,392,349 (claims provided in user prompt).

More… ↓

⤷  Start Trial

Details for Patent 10,392,349

Applicant Tradename Biologic Ingredient Dosage Form BLA Approval Date Patent No. Expiredate
Pharmaand Gmbh PEGASYS peginterferon alfa-2a Injection 103964 October 16, 2002 ⤷  Start Trial 2037-12-22
Pharmaand Gmbh PEGASYS peginterferon alfa-2a Injection 103964 January 07, 2004 ⤷  Start Trial 2037-12-22
Pharmaand Gmbh PEGASYS peginterferon alfa-2a Injection 103964 September 29, 2011 ⤷  Start Trial 2037-12-22
>Applicant >Tradename >Biologic Ingredient >Dosage Form >BLA >Approval Date >Patent No. >Expiredate

Make Better Decisions: Try a trial or see plans & pricing

Drugs may be covered by multiple patents or regulatory protections. All trademarks and applicant names are the property of their respective owners or licensors. Although great care is taken in the proper and correct provision of this service, thinkBiotech LLC does not accept any responsibility for possible consequences of errors or omissions in the provided data. The data presented herein is for information purposes only. There is no warranty that the data contained herein is error free. We do not provide individual investment advice. This service is not registered with any financial regulatory agency. The information we publish is educational only and based on our opinions plus our models. By using DrugPatentWatch you acknowledge that we do not provide personalized recommendations or advice. thinkBiotech performs no independent verification of facts as provided by public sources nor are attempts made to provide legal or investing advice. Any reliance on data provided herein is done solely at the discretion of the user. Users of this service are advised to seek professional advice and independent confirmation before considering acting on any of the provided information. thinkBiotech LLC reserves the right to amend, extend or withdraw any part or all of the offered service without notice.