This TNFRSF11A Biologics Sequence Review Report was produced with PatSnap Biology Modality MCP workflows. It turns patent-scale sequence search, sequence retrieval, pairwise alignment and target evidence into a reproducible diligence narrative. Explore the PatSnap MCP servers used in this report.
Review date: 5 August 2026. This report supports R&D, competitive-intelligence and IP triage. It is not a legal opinion, freedom-to-operate conclusion or validity analysis. A sequence hit does not establish infringement, and a no-hit or low-hit result does not establish clearance.
TNFRSF11A is a reviewed human protein asset represented by UniProt entry Q9Y6Q6. The reference sequence contains 616 amino acids and is annotated as Tumor necrosis factor receptor superfamily member 11A. PatSnap’s patent-scale screen returned 60 matching records in the configured result universe. The leading reviewed hit showed 100.00% query identity across 616/616, with the database claim annotation recorded as Yes.
The resulting screen is classified as elevated diligence priority. That label prioritizes diligence; it does not classify the asset as blocked, available or unique. Whole-protein identity can be driven by conserved domains, common signal peptides, transmembrane regions or endogenous human sequence. Patent relevance depends on whether live claims cover the complete sequence, a fragment, an engineered variant, an antibody recognizing the target, a use, or a functional genus.
Tumor necrosis factor receptor superfamily member 11A is a traceable human protein sequence suitable for systematic similarity screening. For biologics teams, the sequence can matter in several distinct ways: it may be the administered protein, an extracellular target, an antigen used to raise antibodies, a receptor domain incorporated into a fusion, or a reference against which engineered variants are defined. Those possibilities produce different patent questions even when they share the same gene symbol.
This report therefore separates sequence proximity from legal scope. A close patent-sequence match can identify families worth reading, yet naturally occurring human protein sequence is not itself a conclusion about enforceable rights. Conversely, engineered substitutions, truncations, Fc fusions, linkers, glycosylation-site changes or epitope-defined claims may be commercially important even when the full-length reference is not reproduced verbatim.
The workflow began with ls_sequence_search_submit against ALLPATENT protein records and used ls_sequence_search_get_results to retrieve the leading evidence. ls_sequence_fetch resolved the selected patent-sequence record, and ls_sequence_alignment performed a PSA comparison to the reviewed UniProt query. Finally, ls_antibody_antigen_search tested target-linked antibody evidence and ls_patent_sequence_fetch retrieved sequences from a resolved patent record where available.
| Evidence step | TNFRSF11A result | Interpretive limit |
|---|---|---|
| Reference query | 616 aa; reviewed human UniProt Q9Y6Q6 | Reference protein may differ from a therapeutic construct or isoform. |
| Patent similarity | 60 records; leading identity 100.00%; coverage 616/616 | Records are not deduplicated patent families or live claims. |
| Sequence detail | Sequence 1187157645, 1,091 aa | Sequence annotations require specification-level confirmation. |
| PSA | 1 alignment block(s) | Coordinates do not identify claim scope or biological function. |
| Target evidence | 0 antibody–antigen records | Aliases and research antibodies can affect counts. |
| Patent sequences | 0 associated sequences | Listings can contain controls, fragments and unrelated examples. |
The leading result was evaluated under a supplementary sensitivity search using 50–100% identity and 50–100% query coverage. It reported 616/616 identical positions, query coverage 616/616, subject coverage 616/1091, E-value 0 and 0/616 gaps. The database marked the record as Yes for the claim annotation field.
The strict primary window did not yield a usable alignment within the initial service run, so this report also records a broader sensitivity screen. The broader result is explicitly secondary evidence and should not be compared directly with a strict-window hit without noting the threshold change.
The raw count of 60 records should not be read as the number of independent inventions. One sequence can appear in applications, grants, continuations, divisionals and multiple jurisdictions. It can also recur as a reference, antigen, control or prior-art comparator. Family consolidation by earliest priority, applicant, simple family and legal status is therefore essential before ranking competitive risk.
ls_sequence_fetch resolved sequence number 1187157645 with a length of 1,091 aa. The fetched record was then supplied to ls_sequence_alignment for pairwise comparison with the reviewed TNFRSF11A sequence.
The PSA returned 1 alignment block(s). Reviewers should map mismatches to functional domains, extracellular segments, transmembrane regions, cleavage sites and engineered junctions. A concentrated change at a binding interface can matter more than a similar number of substitutions distributed across a nonfunctional region.
The exact TNFRSF11A target-name query returned no antibody–antigen record in the configured page. This is an alias and coverage limitation, not evidence that the target lacks antibody activity or patent disclosure. Follow-up should include the full protein name, synonyms, development codes and pathway aliases.
No direct patent sequence bundle was resolved from the leading antibody–antigen record. This does not indicate an empty patent landscape. Relevant families may use different target aliases, functional definitions, percentage-identity language or sequence listings not connected to the first target record.
Target-level evidence complements sequence similarity because biologics patents often define inventions through binding, epitope, function, disease use or combinations rather than an exact full-length target sequence. The strongest review links the returned sequence to a patent family, verifies the role of the sequence in the specification, and then reads live claims in the jurisdictions relevant to development or commercialization.
| Dimension | Screening signal | Required next check |
|---|---|---|
| Sequence proximity | 100.00% leading query identity | Map differences by domain, isoform and engineered construct. |
| Coverage | 616/616 | Determine whether the match is full-length, fragmentary or domain-specific. |
| Claim annotation | Yes | Verify the sequence number against live independent and dependent claims. |
| Target evidence | 0 records | Search gene, protein-name, alias and pathway terminology. |
| Legal conclusion | Not determined | Review priority, ownership, licensing, prosecution, validity and territory. |
TNFRSF11A produced a traceable sequence-search result with 100.00% leading identity, 616/616 query coverage, 1 PSA block(s), 0 target-linked antibody records and 0 directly fetched patent sequences. Together, these signals support elevated diligence priority and a prioritized family-and-claim review. They do not support a binary clearance or infringement statement.
Reference sequence metadata: reviewed human UniProt entry Q9Y6Q6. Patent-scale similarity, sequence detail, PSA, patent-sequence and antibody–antigen evidence was retrieved through PatSnap Biology Modality MCP on 5 August 2026. Results are bounded by the configured query, thresholds, aliases, task limits and database coverage; rerun at the decision date.