Zhihuiya Patent Legal Status

This skill guides you on how to query patent legal status information via the Zhihuiya (PatSnap) platform, helping users quickly determine the current legal standing and event history of one or more patents.

Core Concepts

The Zhihuiya Patent Legal Status tool returns three layers of legal information for each patent:

1. Simple Legal Status -- A high-level summary of the patent's current standing (e.g., Active, Inactive, Pending, Undetermined, PCT designated period, PCT designated expiration).
2. Legal Status -- A detailed status describing the patent's lifecycle stage (e.g., Published, Examining, Granted, Abandoned, Withdrawn, Rejected, Expired, Revoked, Ceased, Restoration, etc.).
3. Legal Events -- Specific legal actions that have occurred on the patent (e.g., Transfer, License, Pledge, Opposition, Litigation, Re-examination, Customs, Preservation, Invalid-procedure, Oral-procedure, Declassification, Double application, Trust).

Patent identification: Patents can be looked up by either patent ID or publication (announcement) number. When both are provided, patent ID takes priority. Multiple values can be submitted in a single request (comma-separated, up to 100).

Parameter Guide

• If the user provides a publication number (e.g., CN115xxxxxxA, US11xxxxxxB2, EP3xxxxxxA1), use patentNumber.
• If the user provides an internal patent ID, use patentId.
• When both are supplied, patentId takes precedence.

Response Fields

Usage Examples

1. Check whether a single patent is still active

Query the legal status for patent publication number CN115000000A.

2. Batch-check legal status for multiple patents

Look up the legal status for patents US11000000B2, EP3000000A1, and CN115000001A.

3. Identify legal events on a patent

Has patent CN115000000A been involved in any litigation, transfer, or pledge events?

4. Determine if a patent has expired or been revoked

Check if patent US10000000B1 is expired, revoked, or still in force.

5. Look up patents by patent ID

Query the legal status for patent IDs abc123, def456.

Display Rules

1. Present data clearly: Show results in a structured table. Include the publication number, simple legal status, detailed legal status, and legal events for each patent.
2. Translate status values: When the user's language preference is clear, present status labels in that language while keeping the canonical English value in parentheses for precision.
3. Highlight key findings: If the user is checking validity, prominently state whether each patent is Active, Inactive, or Pending at the top of the response.
4. Legal date context: When legalDate is available, include it so users know how recent the status information is.
5. Error handling: If the query fails or returns no results, explain the possible reasons (invalid patent number format, patent not found in database) and suggest the user double-check the input.
6. Volume notice: When querying many patents, present a summary table and note the total count returned.

Important Limitations

• Up to 100 patents per request: The maximum number of patent IDs or publication numbers in a single call is 100.
• At least one identifier required: Either patentId or patentNumber must be provided; the request will fail if both are empty.
• Patent ID priority: When both patentId and patentNumber are provided, the system uses patentId and ignores patentNumber.
• Data coverage: Results depend on the Zhihuiya (PatSnap) database coverage; some very recent filings may not yet be reflected.

User Expression & Scenario Quick Reference

Applicable -- Queries about patent legal standing and events:

Not applicable -- Needs beyond patent legal status:

• Patent search by keyword, classification, or applicant name
• Patent full-text or claims retrieval
• Patent valuation or commercial analysis
• Freedom-to-operate (FTO) analysis
• Patent family or citation analysis

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply:

1. The functionality or purpose described in this skill does not match actual behavior
2. The skill's results do not match the user's intent
3. The user expresses dissatisfaction or praise about this skill
4. Anything you believe could be improved

Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.

For more high-quality, professional cross-border e-commerce skills, set LinkFox Skills.