Patent 11,965,040 (US) claims C5-binding polypeptide compositions: what the scope covers and how the claim set maps to complement inhibition, lipid conjugates, and manufacturable peptide variants
Executive summary: US patent 11,965,040 claims a pharmaceutical composition containing a C5-binding polypeptide defined by a narrow sequence scaffold (R1–Tyr–Xaa0–Glu–Tyr–R2) plus defined optional bridging moieties, defined sub-sequences in R1 and R2, and selectable lysine lipid conjugation plus terminal modifications (N-terminal acetyl, C-terminal amidation). The practical scope is limited to specific amino-acid substitutions (including multiple aza/N-methyl tryptophan-like analogs at Xaa0), and it tightly constrains where the sequence can vary through claim-embedded formulae. The patent landscape risk is driven by whether competing complement C5 inhibitors (peptide, peptidomimetic, antibody, or small-molecule) overlap this exact scaffold and its conjugation/terminal features.
What does US Patent 11,965,040 claim for C5-binding polypeptide compositions?
Straight answer: The claims cover a composition comprising a polypeptide that binds complement component C5, where the polypeptide must contain the motif:
with:
- Xaa0 limited to: Trp, azaTrp, N-methyl Trp, 1-methyl Trp, 3-aminomethyl Phe
- R1 and R2 each are constrained by further dependent-claim formulae for additional fallback coverage.
Claim 1 is the independent “gate” (composition + scaffold + binding function)
Claim 1 requires three elements in combination:
- Pharmaceutical composition (means formulation into a carrier/excipient)
- A C5-binding polypeptide
- The polypeptide’s sequence architecture: R1–Tyr–Xaa0–Glu–Tyr–R2
In claim construction terms, the independent claim is a hybrid of:
- Structure/function: “binds complement component C5” is functional but tied to the defined sequence
- Sequence restriction: the motif and allowed Xaa0 residues constrain the set of covered polypeptides
Xaa0 is a critical narrowing “switch”
The explicit Xaa0 list is unusually specific, and it matters for both infringement and invalidity:
- Trp (standard tryptophan)
- azaTrp (tryptophan analog with a nitrogen substitution)
- N-methyl Trp
- 1-methyl Trp
- 3-aminomethyl Phe (a phenylalanine side-chain functionalized variant)
Because Xaa0 is enumerated, design-around is more feasible than if it were broader (for example “aromatic substituted” or “Trp analogs”).
R1 and R2 are defined as “comprising a polypeptide”
In claim 1, R1 comprises a polypeptide and R2 comprises a polypeptide without further constraint beyond “comprising.” That means claim 1 may capture:
- R1 and R2 as multi-residue segments, as long as the overall polypeptide has the required motif and binds C5.
- The dependent claims then pull R1/R2 into explicit micro-grammars (below).
How broad is claim 1 versus the dependent claim coverage (claims 2–12)?
Straight answer: Claim 1 is broad on the “composition” and general scaffold, while claims 2–10 and 11–12 add narrow structural constraints that create layered fallback positions.
Dependent Claim 2: bridging moiety between two amino acids
Claim 2 adds:
- “polypeptide comprises a bridging moiety between two amino acids”
This is a common tactic in peptide patents:
- It preserves coverage for cyclized or conformationally constrained peptides, where an internal bridge stabilizes the bioactive shape.
- It also becomes a key infringement lever: a competitor peptide that lacks the bridging chemistry falls outside claim 2, but could still attempt to sit inside claim 1 if it still binds C5 and retains the motif.
Dependent Claims 3–6: R1 formulae create the core peptide “alphabet”
Claim 3 specifies that R1 can include a sub-sequence:
- Xaa1–Val–Glu–Arg–Xaa2–Xaa3
with:
- Xaa1: Cys or Lys
- Xaa2: Phe or Ala
- Xaa3: Cys or Asp
Claim 4 narrows further:
- bridging moiety between Xaa1 and Xaa3
Claim 5 extends R1:
- Xaa1–Val–Glu–Arg–Xaa2–Xaa3–Xaa4
where:
- Xaa4 is selected from Asp, Ala, (S)-2-amino-3-(1H-tetrazol-5-yl)propanoic acid, alpha-methyl Asp, N-methyl Asp, cycloleucine, 4-amino-tetrahydro-pyran-4-carboxylic acid
Claim 6 extends again:
- Xaa1–Glu–Arg–Xaa2–Xaa3–Xaa4–Xaa5
where:
- Xaa5: tert-butylglycine or Val
Claim interaction note for scope: Claim 5 and claim 6 present alternative ways the R1 sequence can be formed depending on the numbering in the claim text, but they both function as additional limitations that make dependent claims narrower than claim 1. A competitor that avoids these specific R1 enumerations may still be assessed under claim 1 if the motif and binding requirement are met.
Dependent Claims 7–10: R2 is optional sub-sequence with constrained choices
Claim 7 defines R2 as:
- Pro–Xaa6–Xaa7
with optional presence/absence:
- Xaa6 selected from: cyclohexylglycine, phenylglycine (Phg), D-Phg, N-methyl Phg, Ala, amino isobutyric acid, or is absent
- Xaa7 selected from: Lys, norvaline, Pro, or is absent
This adds both:
- residue-level restrictions at Xaa6 and Xaa7, and
- an option that segments can be absent, which affects how many residues the competitor must include to land in the literal claim.
Claim 8 nails Xaa7:
Claim 9 then requires conjugation:
- the Lys is conjugated with a lipid
Claim 10 defines permitted modified lysine lipid substitutions. Covered examples include:
- N-ε-palmitoyl lysine
- N-ε-lauryl lysine
- N-ε-capryl/caprylic lysine variants
- PEG-linked lipid-γ-glutamic acid conjugate examples:
- N-ε-(PEG2-γ-glutamic acid-N-α-octadecanedioic acid)lysine
- N-ε-(PEG24-γ-glutamic acid-N-α-hexadecanoyl)lysine
- A cyclohexenone-type linker example:
- N-ε-1-(4,4-dimethyl-2,6-dioxocyclohex-1-ylidene)-3-methylbutyl-L-lysine
These dependent claims create a focused “lyso-lipid conjugate” fence. They are not required by claim 1, but if a competitor uses a lipid-conjugated lysine with one of these structures, it can be pulled into claims 9–10 rapidly.
Dependent Claims 11–12: terminal modifications
Claim 11: N-terminal acetyl
Claim 12: C-terminal —NH2
These are common peptide stabilization/conformation features. Their presence/absence can create infringement gaps if competitors use other terminal formats (free acid, other caps, longer propeptides, etc.). Still, these are dependent claims; if a competitor omits them, claim 1 can remain in play if the scaffold and binding are satisfied.
What is the likely scope for “polypeptides that bind C5” and how does the functional language limit it?
Straight answer: “Binds complement component C5” is functional, but because claim 1 is already defined by sequence motif and enumerated residue analogs, the functional language is unlikely to expand the claim to unrelated C5 binders with a different scaffold. It is instead used to confirm that the defined sequence behaves as a C5-binding polypeptide.
From a litigation standpoint, this claim pattern shifts the factual dispute toward:
- whether the competitor polypeptide containing the motif and allowed Xaa0/R1/R2 residues actually binds C5, and
- whether the competitor’s binding assay shows the same binding phenotype contemplated in the patent.
The “binding” element can also complicate invalidity arguments if the motif is narrow enough that the binding function is argued as co-extensive with the structure.
What formulations are covered by US 11,965,040?
Straight answer: The patent is a composition patent: it covers the polypeptide (with the sequence/chemistry limits) in a pharmaceutically acceptable carrier or excipient. The claim language does not restrict route of administration, dosage form, or release profile.
In-scope formulation scenarios:
- Injectable solutions or suspensions
- Lyophilized drug reconstituted before administration
- Excipients for peptide stability, buffering, tonicity adjustment, and surfactants
- Potentially solid oral forms only if a competitor asserts binding function is retained, but the patent claim itself does not specify dosage form.
Out-of-scope based on claim text:
- Non-pharmaceutical carriers (not “pharmaceutically acceptable”)
- Formats where the active polypeptide sequence is not present in a way that meets the motif and Xaa0 constraints.
How does the claim language define “bridging moiety,” and why does it matter?
Straight answer: The bridging moiety is introduced only in dependent claims (2 and 4). It likely covers internal cyclization or a covalent linkage connecting two amino acids.
Key scope implications:
- If a competitor uses a linear peptide without internal bridging, it may be outside claims 2 and 4.
- But it could still infringe claim 1 if claim 1 is satisfied (motif + allowed Xaa0 + R1/R2 scaffold + C5 binding), depending on how the patentee argues that “R1 comprises a polypeptide” is compatible with a non-bridged linear structure.
Bridging thus becomes a critical fallback limitation in case claim 1’s breadth is challenged.
Where are the most enforceable “hot spots” in US 11,965,040’s claim set?
Straight answer: The most commercially enforceable elements are typically those that are both (i) narrow and (ii) likely to be chosen by product developers.
- Xaa0 enumeration (Trp, azaTrp, N-methyl Trp, 1-methyl Trp, 3-aminomethyl Phe)
- R1 sub-sequences and constrained variants (Val-Glu-Arg plus allowed positions)
- Bridging moiety between specific residues (Xaa1 and Xaa3) in claim 4
- R2 definition with Pro–Xaa6–Xaa7 and “absent” options
- Lipid-conjugated lysine (claim 9–10), which often is a key differentiator for half-life extension and formulation behavior
- Terminal caps (acetyl N-terminus; C-terminal —NH2)
If a competitor’s product uses a lipid-conjugated lysine with one of the enumerated modified lysine structures, claim 10 becomes a direct path to literal infringement, assuming the rest of the scaffold is met.
What generic entry risks exist for peptide C5 inhibitors under US 11,965,040?
Straight answer: A “generic” risk profile depends on whether the competitor is making a peptide therapeutic that could be substituted via pathway and whether it remains structurally within the claimed peptide scaffold.
For this claim set:
- Literal infringement risk is high if a competitor copies the motif and selected residues/bridging and uses one of the enumerated lipid-lysine conjugates.
- Non-literal risk still exists because claim 1 is a scaffold claim and not solely a specific sequence string, but the presence of enumerated Xaa0 and constrained residue choices reduces the range of plausible equivalents.
Also, “generic” substitution is typically less straightforward for peptides than for small molecules due to manufacturing and analytical complexity, but the patent analysis hinges on whether a redesigned peptide avoids the motif and residue lists.
Patent estate mapping: how US 11,965,040 is likely situated within a complement C5 inhibitor portfolio
Straight answer: Based on the claims alone, US 11,965,040 sits in a portfolio cluster for:
- Complement C5 binding peptide compositions
- Sequence-optimized C5-binding motifs
- Conformation-stabilized variants (bridging moiety)
- Half-life extension via lipid conjugation on Lys
- Terminal stabilization via acetyl and amidation
Practical portfolio implication: If a company built this around a specific peptide scaffold, it typically has companion filings:
- additional peptide analogs with different Xaa0 or R1/R2 options
- manufacturing/solid-phase synthesis claims
- formulation claims for injection
- method-of-treatment claims (not shown in the claim text you provided)
However, a complete landscape requires bibliographic data and family members, which is not included in the claim text provided.
How does US 11,965,040 compare with other C5 inhibitor classes (antibodies vs peptidomimetics)?
Straight answer: The patent is targeted at peptide/polypeptide C5 inhibitors, not antibodies or small molecules.
If the competitor is an antibody targeting C5
- It is unlikely to meet the “polypeptide comprising formula R1–Tyr–Xaa0–Glu–Tyr–R2” requirement, so claim 1 would typically not cover it.
- In that case, risk is low under literal terms, with only theoretical doctrine-of-equivalents arguments possible if a court deems the motif and binding function to be functionally equivalent.
If the competitor is a different peptide binder to C5
- Risk rises sharply if the competitor uses the same motif and allowed Xaa0 list.
- Lipid conjugation on lysine with enumerated modified lysines creates a second infringement lane (claims 9–10).
Key Takeaways
- US 11,965,040 is a composition claim anchored on a specific C5-binding polypeptide scaffold: R1–Tyr–Xaa0–Glu–Tyr–R2.
- Xaa0 is tightly enumerated, creating a practical design-around lever.
- Claims 2–6 restrict conformation and R1 micro-sequences, including an explicit bridging moiety between defined residues.
- Claims 7–10 restrict R2 and then narrow further into lipid-conjugated lysine with enumerated modified lysine structures, which is the most product-specific enforcement zone.
- Claims 11–12 add terminal modification limitations (N-terminal acetyl; C-terminal —NH2), relevant for peptide manufacturability and variant selection.
FAQs
-
Does US 11,965,040 cover linear C5-binding peptides without a bridging moiety?
Yes, in principle under claim 1, since bridging is a limitation only in dependent claims 2 and 4, but only if the peptide still has the required R1–Tyr–Xaa0–Glu–Tyr–R2 scaffold and binds C5.
-
Which amino-acid positions are the main “literal infringement” chokepoints?
Xaa0 (enumerated set), the constrained R1 positions (Xaa1–Xaa4 plus alternate R1 sequence in claim 6), and R2’s Xaa6/Xaa7 (plus lipid-conjugated lysine when Xaa7 is Lys).
-
What does a competitor most likely change to avoid claims 9–10?
Use a lysine lipid conjugate that is not one of the listed modified lysine structures, or avoid lipid conjugation at the lysine corresponding to Xaa7.
-
Are terminal modifications required for infringement of claim 1?
No. N-terminal acetyl and C-terminal —NH2 are in dependent claims 11 and 12.
-
Could a different C5-binding mechanism avoid infringement even if it contains Tyr-Glu-Tyr?
Yes if the polypeptide does not meet the full scaffold R1–Tyr–Xaa0–Glu–Tyr–R2 with the enumerated Xaa0 and the constrained R1/R2 structures, or if it is not a C5-binding polypeptide as claimed.
References (APA)
No sources cited because the prompt provides only the asserted claim text and does not include patent bibliographic details, prosecution history, or related documentation needed for citation-backed analysis.
