What is the endpoint for [P100]Claim Similarity Analysis?

The [P100]Claim Similarity Analysis endpoint is POST https://connect.patsnap.com/search/patent/claim-sim.

Where can I find the OpenAPI schema for [P100]Claim Similarity Analysis?

The OpenAPI schema is available at /openapi.json#/paths/~1search~1patent~1claim-sim/post. You can also browse the full specification at /openapi.json.

[P100]Claim Similarity Analysis

Q: What data can [P100]Claim Similarity Analysis return?

[P100]Claim Similarity Analysis Analyze the similarity between two claim texts and return a similarity score between 0-1. This interface is based on deep learning models that can accurately identify similarities in technical features, structural composition, and expression methods of claims. See the Response Schema and Success Response Example on this page for the full structure.

post

https://connect.patsnap.com/search/patent/claim-sim

Try in Sandbox

Analyze the similarity between two claim texts and return a similarity score between 0-1. This interface is based on deep learning models that can accurately identify similarities in technical features, structural composition, and expression methods of claims.

Notes: 1. Input claim texts should be complete claims including technical features and limitations 2. Similarity scores above 0.8 indicate high similarity, 0.6-0.8 indicate moderate similarity, below 0.6 indicate low similarity 3. Supports analysis of Chinese and English claim texts

Request Parameters

List of parameters supported by this API endpoint

Name	Type	Example	Description
`src` Required	`string`	1. A server system \r\rincluding:\r\n\ta permission server in communication with a plurality of clients, wherein the permission server utilizes client device information provided by the plurality of clients to determine an identifier corresponding to at least one data stream of a plurality of data streams for each of the plurality of clients;\t\n\ta memory; and\t\n\tat least one processor configured to multicast data to the plurality of clients, each client storing the identifier provided by the permission server and corresponding to at least one data stream of the plurality of data streams associated with the client,\t\n\twherein the at least one processor is further configured to:\t\n\treceive the plurality of the data streams, each of the data streams including data;\t\n\tdetermine the identifier corresponding to at least one of the plurality of received data streams;\t\n\ttransmit, to the plurality of clients, a mapping between each identifier and a respective multicast stream; and\t\n\tmulticast data of the plurality of received data streams in accordance with the mapping.	Source claim text
`tgt` Required	`string`	1. A server system \r\rincluding:\r\n\ra memory; and\r\n\rat least one processor configured to multicast data to a plurality of clients, each client storing an identifier corresponding to at least one data stream of a plurality of data streams associated with the client,\r\n\rwherein the at least one processor is further configured to:\r\n\rreceive the plurality of the data streams, each of the data streams including data;\r\n\rdetermine the identifier corresponding to at least one of the plurality of received data streams;\r\n\rtransmit, to the plurality of clients, a mapping between each identifier and a respective multicast stream; and\r\n\rmulticast data of the plurality of received data streams in accordance with the mapping.	Target claim text

Request Example

Example request body for this API endpoint

JSON

{
  "src": "1. A server system \\r\\rincluding:\\r\\n\\ta permission server in communication with a plurality of clients, wherein the permission server utilizes client device information provided by the plurality of clients to determine an identifier corresponding to at least one data stream of a plurality of data streams for each of the plurality of clients;\\t\\n\\ta memory; and\\t\\n\\tat least one processor configured to multicast data to the plurality of clients, each client storing the identifier provided by the permission server and corresponding to at least one data stream of the plurality of data streams associated with the client,\\t\\n\\twherein the at least one processor is further configured to:\\t\\n\\treceive the plurality of the data streams, each of the data streams including data;\\t\\n\\tdetermine the identifier corresponding to at least one of the plurality of received data streams;\\t\\n\\ttransmit, to the plurality of clients, a mapping between each identifier and a respective multicast stream; and\\t\\n\\tmulticast data of the plurality of received data streams in accordance with the mapping.",
  "tgt": "1. A server system \\r\\rincluding:\\r\\n\\ra memory; and\\r\\n\\rat least one processor configured to multicast data to a plurality of clients, each client storing an identifier corresponding to at least one data stream of a plurality of data streams associated with the client,\\r\\n\\rwherein the at least one processor is further configured to:\\r\\n\\rreceive the plurality of the data streams, each of the data streams including data;\\r\\n\\rdetermine the identifier corresponding to at least one of the plurality of received data streams;\\r\\n\\rtransmit, to the plurality of clients, a mapping between each identifier and a respective multicast stream; and\\r\\n\\rmulticast data of the plurality of received data streams in accordance with the mapping."
}

Response Schema

Structure of the API response data

Field Name	Type	Example	Description
`data`	`object`	-	response data
`score`	`number<float>`	`0.85`	Similarity score, range 0-1, higher value indicates higher similarity
`status` Required	`boolean`	`false`	Status
`error_msg`	`string`	`The request parameter format is incorrect！`	Error Message
`error_code` Required	`integer`	`0`	Error Code

Success Response Example

Example of a successful API response

JSON

{
  "data": {
    "score": 0.85
  },
  "status": true,
  "error_code": 0
}

Error Codes

List of possible error codes returned by this endpoint

Business Errors

Error Code	Description
`68300004`	Invalid parameter!
`68300005`	Search api failure!
`68300006`	Analytic basic access error!
`68300007`	Bad request!
`68300008`	Service error, please try again later!
`68300010`	The file does not comply with upload specifications!

Platform Errors

Error Code	Description
`67200000`	API call exceeds the total limit set by the platform!
`67200001`	API call exceeds the total limit set by the platform!
`67200002`	The current call rate is too fast, exceeding the current configuration limit QPS!
`67200003`	The key and secret parameters for applying for the token are incorrect or the client has been disabled!
`67200004`	The requested api does not have permission. Please contact our support personnel!
`67200005`	Insufficient account balance/number of calls!
`67200006`	The client has exceeded the activation validity period!
`67200007`	The current call exceeds the configured usage limit of the day!
`67200008`	Please check if the required apikey in the query parameter has been transmitted!
`67200009`	The apikey does not match the passed bearerToken. Please check if a valid token is being used!
`67200012`	The request is illegal!
`67200100`	The current server status is busy, request response timeout!
`67200101`	The API requested currently does not exist. Please check the request path!

HTTP Status Codes

Status Code	Description
`0`	Success
`201`	Created
`401`	Unauthorized
`403`	Forbidden
`404`	Not Found

Performance Metrics

Expected performance characteristics for this endpoint

Normal Response Time

5000 ms

Max Response Time

10000 ms