|
Patent landscape, scope, and claims summary: |
Executive summary
- US 8,871,914 claims a human monoclonal anti-PCSK9 defined by (i) blocking of PCSK9–LDLR binding and (ii) epitope footprints on human PCSK9 (SEQ ID NO: 1) centered on residues S123, E129, A311, D313, and D337, with dependent claim layers for multi-residue epitope coverage, neutralizing activity, CHO-produced antibodies, binding affinity (K_D ≤ 5×10^-9 M), and specific light-chain (SEQ ID NO: 157).
- The claim set is not limited to a single named mAb, but the scope is narrowed by residue-defined epitope subsets and sequence-defined light-chain content.
- For a US FTO/validity strategy, the dominant issues are: (1) whether prior art mAbs recognize overlapping residue-defined epitopes on PCSK9 and functionally block LDLR binding, (2) whether SEQ ID NO: 157 and the competing antibody sequences (SEQ ID NOs: 467/469) anchor the claims to a specific lineage, and (3) whether “functional epitope / structural epitope” language creates claim construction ambiguity that can be exploited in litigation or PTAB review.
US Patent 8,871,914 claims analysis: what is the real scope around the S123/E129/A311/D313/D337 PCSK9 epitope?
Core independent claim (claim 1)
- Claim 1 requires an isolated human monoclonal antibody that:
- binds PCSK9 at an epitope comprising at least one of residues S123, E129, A311, D313, D337 on PCSK9 SEQ ID NO: 1; and
- blocks binding of PCSK9 to LDLR.
What this means for coverage
- The epitope is “residue-defined” rather than fully sequence-defined. “At least one” residue in a set creates broad potential overlap with antibodies that contact any subset member while still blocking LDLR binding.
- “Blocks binding of PCSK9 to LDLR” imports a functional requirement. Many competitive anti-PCSK9 antibodies can meet this, but the claim does not require:
- a specific mechanism beyond LDLR-blocking; or
- a specific epitope class (neutralizing, structural, or functional), though later claims layer that on.
Claim 16’s expansion
- Claim 16 similarly defines an isolated human monoclonal antibody binding PCSK9 “having” SEQ ID NO: 1 at one or more of the same residues and blocking LDLR binding. It is effectively a second independent claim track focusing on “human PCSK9 SEQ ID NO: 1” compliance.
Dependent claim architecture: narrowing axes
- Residue subset count
- Claim 2: epitope includes ≥2 of the five residues.
- Claim 3: epitope includes ≥3 of the five residues.
- Neutralizing antibody
- Claim 4 depends on claim 3: antibody is neutralizing.
- Manufacturing system
- Claim 5 depends on claim 4: antibody is produced by CHO.
- Affinity
- Claim 6 depends on claim 3: K_D ≤ 5×10^-9 M.
- Light-chain sequence anchor
- Claim 7 depends on claim 3: light chain region includes SEQ ID NO: 157.
- Claim 22 depends on claim 16: light chain includes SEQ ID NO: 157.
- Epitope taxonomy
- Claim 8: epitope is “functional”.
- Claim 9: epitope is “structural”.
- Native PCSK9 targeting
- Claim 10: epitope is on native PCSK9.
- Residue minimums
- Claims 11–15 individually tighten residue requirements to “at least residue 123 / 129 / 311 / 313 / 337.”
- Additional residue contact
- Claim 23: further binds residues 132, 351, 390, 413.
- Claim 24: further binds residues 123, 164, 344, 347, 349.
- Competition framing
- Claim 25: competes for PCSK9 binding with an antibody defined by heavy chain SEQ ID NO: 467 and light chain SEQ ID NO: 469.
Which residues drive novelty versus obviousness risk?
The five residue anchors (S123, E129, A311, D313, D337) are the most litigation-relevant claim elements because they:
- permit prior-art matching via epitope mapping (cryo-EM, alanine scanning, hydrogen-deuterium exchange, mutagenesis, or competition/escape mapping);
- create direct infringement arguments based on epitope definition and binding competition; and
- are likely to appear in earlier anti-PCSK9 epitope publications if they correspond to a known antibody class.
How does “blocks PCSK9–LDLR binding” affect enforceability?
- It creates a capability test for infringement: an accused antibody must functionally prevent PCSK9 from engaging LDLR.
- In practice, most therapeutic anti-PCSK9 mAbs (e.g., those that compete with PCSK9–LDLR binding) meet this requirement, which can reduce the novelty contribution of the function term and shift the fight to epitope mapping and sequence-defined anchors.
How strong is the patent estate for anti-PCSK9 antibodies like evolocumab/alirocumab: what is covered by epitope-residue and sequence-defined limitations?
Key observation
- US 8,871,914 reads like a patent designed to carve out a specific anti-PCSK9 epitope footprint while also using one or more sequence anchors (light-chain SEQ ID NO: 157; competitor antibody sequences SEQ ID NO: 467/469) to withstand breadth challenges.
Likely claim interpretation pressures
- “Epitope comprises at least one of amino acid residues …” can invite fights over:
- whether “comprises” means direct contact versus proximity;
- whether binding to PCSK9 mutants lacking one residue still infringes; and
- whether epitope definition is restricted to “epitope mapping” performed by a particular experimental method.
- “Functional epitope” vs “structural epitope” can create construction issues if the patent specification treats these differently, but in claim terms they mainly provide further classification rather than a distinct mechanism.
What prior-art antibodies can anticipate US 8,871,914 if they bind overlapping PCSK9 residues and block LDLR?
Anticipation pathway
A single prior art reference can invalidate claims if it discloses, in one teaching, an antibody that:
- is a human monoclonal antibody;
- binds PCSK9 at an epitope including at least the specified residue set on SEQ ID NO: 1; and
- blocks PCSK9–LDLR binding; and
- (for dependent claims) has K_D ≤ 5×10^-9 M, CHO production, and/or includes light chain SEQ ID NO: 157.
Obviousness pathway
Even if a single prior art reference does not provide the exact residue subset combination or the exact light chain, an obviousness attack can assemble:
- an antibody class that blocks LDLR binding; plus
- known epitope residues for that class; plus
- known selection/optimization routes to reach comparable affinities and manufacturing platforms.
Competition claim (claim 25)
- Claim 25’s “competes for binding with an antibody comprising heavy chain SEQ ID NO: 467 and light chain SEQ ID NO: 469” creates an alternate infringement/validity anchor:
- If the cited sequences correspond to a known commercial or published antibody lineage, then many “competing” antibodies can land inside claim 25’s scope even if their exact epitope residues differ, depending on how the patent defines competition and epitope.
Which dependent claims most constrain infringement and which are easiest to design around?
Most constraining (design-around likely)
- Claim 7 / claim 22: requires the light chain includes SEQ ID NO: 157. Sequence-defined constraints are typically harder for competitors to avoid without re-engineering variable regions.
- Claim 6: requires K_D ≤ 5×10^-9 M.
- Claim 5: requires CHO-produced antibodies (may matter for manufacturing but often not for product-by-process if infringement is analyzed as an antibody product).
Moderately constraining
- Claims 2–4 (≥2 or ≥3 residue coverage; neutralizing).
- Claims 23–24 (additional residue bindings) tighten the epitope mapping further.
Least constraining (design-around difficult)
- Claim 1 / claim 16: “at least one residue” from the five-residue set plus functional LDLR blocking. If an accused antibody touches any one of these residues and blocks LDLR binding, it can land in the independent claim range.
What patent litigation outcomes should be expected for epitope-mapping disputes in anti-PCSK9 mAb cases?
Likely litigation battlegrounds
- Epitope mapping evidence
- Accused infringers generally dispute residue inclusion (whether the residue set is truly part of the binding epitope under the patent’s definition).
- Functional LDLR-blocking assay equivalence
- Defendants may challenge whether the assay used to establish “blocks binding” matches the patent’s interpretation.
- Light-chain sequence substitution
- For dependent claims on SEQ ID NO: 157, defendants can attempt to show non-inclusion of the specific light-chain sequence.
Practical impact of the residue-set
- The more residues required (≥3 in claim 3) the narrower the infringement perimeter becomes. A competitor’s antibody might contact only one or two residues from the set while still blocking LDLR binding via a different surface.
When does US 8,871,914 lose exclusivity? What is the expiration timeline for filing/issue-based patent terms?
No expiration timeline can be produced from the information provided. Patent term and any adjustments require at least one of: priority date(s), filing date, issue date, PTA/PTA details, and any terminal disclaimer structure. Without those facts, an accurate exclusivity calendar cannot be stated.
What is the Orange Book status of US 8,871,914 for anti-PCSK9 generics or biosimilars?
US patents covering antibodies typically appear in the FDA Orange Book only where tied to an approved drug product in a way that the listing includes those patents for the product. The provided information contains no drug name, Orange Book application number, or listing details for US 8,871,914. A status determination cannot be made from the claims excerpt alone.
How does US 8,871,914 compare with the patent strategies behind PCSK9 mAbs like evolocumab and alirocumab?
Comparison axis: claim design
- Many landmark anti-PCSK9 patents used one or more of:
- sequence-defined heavy/light chains (tight);
- epitope-defined footprints (moderate);
- functional blocking (broad);
- engineered affinity/neutralization (narrow on subclass).
- US 8,871,914 is consistent with a hybrid strategy:
- residue-defined epitope (broad-to-moderate via “at least one”);
- functional LDLR blocking (broad);
- narrowing dependent layers by (i) residue-count thresholds, (ii) neutralizing, (iii) K_D, and (iv) explicit light-chain sequence (tight).
Business implication
- For a would-be competitor, the key to non-infringement is to avoid at least one of:
- the specific epitope residue set thresholds; or
- the light-chain identity tied to SEQ ID NO: 157; or
- the necessary K_D and neutralizing criteria for dependent claims.
What patent estate strength exists beyond US 8,871,914: continuations, divisionals, and claim layering?
A comprehensive estate assessment requires:
- the patent family set (members by INPADOC/PAIR);
- continuation/divisional relationships;
- other US patents citing the same specification; and
- whether claims were amended to cover different epitope classes.
No family or related document data is provided, so no estate breadth or layering analysis can be executed.
Commercial and regulatory impact: what generic entry risks exist for antibodies that block PCSK9–LDLR?
Small-molecule generics
- Not applicable to monoclonal antibodies.
Biosimilar entry
- The entry risk is typically patent-focused on the antibody sequence/epitope/method-of-binding claims like those in US 8,871,914.
- The most acute risk to a biosimilar developer is matching:
- epitope residue footprints; and
- binding functionality (LDLR blocking) and neutralization.
No pathway-to-approval timeline or biosimilar filing history can be produced from the information provided.
Technical claim interpretation: how would a court treat “epitope comprises residues …” and “native PCSK9 epitope”?
Residue-inclusive language
- “Epitope comprises at least one of” typically leads to mapping to a set of residues that are part of the antibody’s contact or determinant region.
- Litigation practice often turns on whether the defendant’s antibody binds a mutant lacking one residue, whether escape mutations map to those positions, and whether structural/biophysical data supports inclusion.
Native PCSK9 epitope
- This narrows the claimed epitope to one present on the correctly folded protein in its native state, not just on peptide fragments.
- Competitors could attempt to show that their antibody binds a determinant that is not accessible or not the same on native PCSK9.
Key Takeaways
- US 8,871,914 is an anti-PCSK9 antibody patent defined by residue-defined epitope footprints on SEQ ID NO: 1 (S123, E129, A311, D313, D337) plus a functional requirement: blocking PCSK9 binding to LDLR.
- Independent claim breadth is driven by “at least one residue,” making the independent claims comparatively harder to design around if an accused antibody touches any one of the five residues and blocks LDLR binding.
- Dependent claims provide enforceability leverage through tighter requirements: ≥2/≥3 residue coverage, neutralization, K_D ≤ 5×10^-9 M, CHO production, and a sequence anchor via light chain SEQ ID NO: 157.
- The most consequential technical/legal disputes in enforcement are expected to focus on epitope mapping (direct vs determinant residues) and on whether an accused antibody meets sequence/affinity thresholds for dependent claims.
FAQs
- What does “epitope comprises at least one of residues S123/E129/A311/D313/D337” mean for infringement analysis?
- Which claim element is most likely to be litigated: LDLR-blocking function or the residue-defined PCSK9 epitope?
- How does including light chain SEQ ID NO: 157 change a biosimilar/alternative antibody design strategy?
- What is the legal impact of “competes for binding” against the antibody defined by SEQ ID NO: 467/469?
- How do “functional epitope” and “structural epitope” terms affect claim construction for anti-PCSK9 antibodies?
References
(No references are included because no source documents, filing dates, specification text, prosecution history, family members, or FDA/Orange Book listing data were provided in the prompt.)
More… ↓
⤷ Start Trial
|
