What is the endpoint for [AI35-12]Novelty Check - Add Comparison Document or Patent?

The [AI35-12]Novelty Check - Add Comparison Document or Patent endpoint is POST https://connect.patsnap.com/ai/novelty-search/feature/comparison/generate.

Where can I find the OpenAPI schema for [AI35-12]Novelty Check - Add Comparison Document or Patent?

The OpenAPI schema is available at /openapi.json#/paths/~1ai~1novelty-search~1feature~1comparison~1generate/post. You can also browse the full specification at /openapi.json.

[AI35-12]Novelty Check - Add Comparison Document or Patent

Q: What data can [AI35-12]Novelty Check - Add Comparison Document or Patent return?

[AI35-12]Novelty Check - Add Comparison Document or Patent For cases where the user needs to manually add comparison documents or patents, the output parameters of this interface can be used as part of the input parameters for the 'final_result' in '[AI35-9] Novelty Search - Confirm Filter List and Feature Comparison'. See the Response Schema and Success Response Example on this page for the full structure.

post

https://connect.patsnap.com/ai/novelty-search/feature/comparison/generate

Try in Sandbox

For cases where the user needs to manually add comparison documents or patents, the output parameters of this interface can be used as part of the input parameters for the 'final_result' in '[AI35-9] Novelty Search - Confirm Filter List and Feature Comparison'.

Note: This is an auxiliary function and not a mandatory step. Valid technical features and request parameters must be provided.

Request Parameters

List of parameters supported by this API endpoint

Name	Type	Example	Description
`request` Required	`object`	`{ "pn": "CN118289111A", "is_add_patent": true, "add_patent_selected": true }`	Feature comparison parameter
`add_patent_selected`	`boolean`	`true`	Whether the newly added patent is selected for literature confirmation by default
`is_add_patent`	`boolean`	`true`	Whether to add patent
`pn` Required	`string`	`CN118289111A`	Patent PN number
`tech_features` Required	`array`	[ { "selected": true, "user_add": false, "feature_num": "F1", "feature_weight": "topic", "feature_elements": "电话机, 图像识别能力", "feature_function": "提供一种能够实现图像信息采集、文字识别及信息获取功能的电话机整体结构", "feature_text_original": "具有图像识别能力的电话机", "feature_weight_reason": "本技术方案的主题名称，明确保护对象为具有图像识别能力的电话机" }, { "selected": true, "user_add": false, "feature_num": "F1.1", "feature_weight": "core", "feature_elements": "电话, 摄像装置, 链接关系", "feature_function": "通过在电话机中集成摄像装置，实现电话机对外部图像信息的采集", "feature_text_original": "包括电话、与电话链接的摄像装置", "feature_weight_reason": "现有电话机通常不具备与摄像装置链接的结构，属于本方案为实现图像采集功能而新增的结构" }, { "selected": true, "user_add": false, "feature_num": "F1.2", "feature_weight": "core", "feature_elements": "命令, 摄像装置, 控制", "feature_function": "通过命令控制摄像装置的工作，实现电话机对图像采集过程的自动化管理", "feature_text_original": "至少包括一个用于控制与电话链接的摄像装置工作的命令", "feature_weight_reason": "现有电话机未涉及通过命令控制外部摄像装置工作的功能，属于本方案为实现自动化图像采集新增的控制手段" }, { "selected": true, "user_add": false, "feature_num": "F1.3", "feature_weight": "core", "feature_elements": "图像信息, 文字信息, 获取", "feature_function": "利用图像识别技术对采集到的图像进行处理，自动提取图像中的文字信息，实现图像到文字的转换", "feature_text_original": "根据摄取的图像信息获取该图像信息源的文字信息", "feature_weight_reason": "现有电话机无法自动识别图像中的文字信息，属于本方案为实现文字信息自动提取而新增的功能" }, { "selected": true, "user_add": false, "feature_num": "F1.4", "feature_weight": "core", "feature_elements": "文字信息, 电话显示器, 显示", "feature_function": "将识别出的文字信息通过电话显示器展示，实现用户对图像文字内容的直接获取", "feature_text_original": "并将文字信息显示在电话显示器上", "feature_weight_reason": "现有电话机不具备将图像识别出的文字信息显示的功能，属于本方案为提升用户体验新增的显示手段" }, { "selected": true, "user_add": false, "feature_num": "F1.5", "feature_weight": "core", "feature_elements": "电路算法, 地址, 网络数据库, 文字信息", "feature_function": "通过电路算法解析获取图像相关信息的地址，并从网络数据库中进一步获取相关文字信息，实现电话机信息获取能力的扩展", "feature_text_original": "电话机通过电路算法首先得到地址，再通过该地址从相关显示器的网络数据库得到文字信息", "feature_weight_reason": "现有电话机不具备通过电路算法获取地址并从网络数据库获取相关文字信息的功能，属于本方案为实现信息扩展获取而新增的技术手段" } ]	Technical features list
`feature_elements`	`string`	`电话机, 图像识别能力`	Feature elements
`feature_function`	`string`	`提供一种能够实现图像信息采集、文字识别及信息获取功能的电话机整体结构`	Feature function
`feature_num`	`string`	`F1`	Feature number
`feature_text`	`string`	`具有图像识别能力的电话机`	Feature text
`feature_text_original`	`string`	`具有图像识别能力的电话机`	Original feature text
`feature_weight`	`string`	`topic`	Feature weight
`feature_weight_reason`	`string`	`本技术方案的主题名称，明确保护对象为具有图像识别能力的电话机`	Feature weight reason
`selected`	`boolean`	`true`	Selected
`user_add`	`boolean`	-	User added

Request Example

Example request body for this API endpoint

JSON

{
  "request": {
    "pn": "CN118289111A",
    "is_add_patent": true,
    "add_patent_selected": true
  },
  "tech_features": [
    {
      "selected": true,
      "user_add": false,
      "feature_num": "F1",
      "feature_text": "具有图像识别能力的电话机",
      "feature_weight": "topic",
      "feature_elements": "电话机, 图像识别能力",
      "feature_function": "提供一种能够实现图像信息采集、文字识别及信息获取功能的电话机整体结构",
      "feature_text_original": "具有图像识别能力的电话机",
      "feature_weight_reason": "本技术方案的主题名称，明确保护对象为具有图像识别能力的电话机"
    }
  ]
}

Response Schema

Structure of the API response data

Field Name	Type	Example	Description
`data`	`object`	-	response data
`final_res`	`array`	`[ { "lang": "zh", "claims": [ { "claim_num": 1, "claim_text": "一种数据处理方法，其特征在于..." } ], "document": "一种基于人工智能的数据处理方法", "features": [ { "score": 85, "public_score": 90, "tech_feature": "人工智能算法", "comparison_feature": "机器学习算法" } ], "patent_id": "CN123456789A", "public_score": 87.5 } ]`	Final results
`lang`	`string`	`zh`	Language
`claims`	`array`	`[ { "claim_num": 1, "claim_text": "一种数据处理方法，其特征在于..." } ]`	Claims original text list
`claim_num`	`integer<int32>`	`1`	Claim number (claim 1, claim 2, claim 3)
`claim_text`	`string`	`一种数据处理方法，其特征在于：包括数据采集步骤、数据预处理步骤和数据分析步骤。`	Claim original text
`document`	`string`	`一种基于人工智能的数据处理方法`	Document
`features`	`array`	`[ { "score": 85, "public_score": 90, "tech_feature": "人工智能算法", "comparison_feature": "机器学习算法" } ]`	Feature list
`type`	`string`	`public`	CC tag type
`score`	`integer<int32>`	`85`	Score
`differ`	`string`	`NONE`	Difference identifier
`public_score`	`integer<int32>`	`90`	Disclosure score
`tech_feature`	`string`	`人工智能算法`	Technical feature
`comparison_feature`	`string`	`机器学习算法`	Comparison feature
`patent_id`	`string`	`CN123456789A`	Patent ID
`public_score`	`number<float>`	`87.5`	Disclosure score
`threshold`	`integer<int32>`	`75`	Threshold
`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": {
    "final_res": [
      {
        "lang": "zh",
        "claims": [
          {
            "claim_num": 1,
            "claim_text": "一种数据处理方法，其特征在于：包括数据采集步骤、数据预处理步骤和数据分析步骤。"
          }
        ],
        "document": "一种基于人工智能的数据处理方法",
        "features": [
          {
            "type": "public",
            "score": 85,
            "differ": "NONE",
            "public_score": 90,
            "tech_feature": "人工智能算法",
            "comparison_feature": "机器学习算法"
          }
        ],
        "patent_id": "CN123456789A",
        "public_score": 87.5
      }
    ],
    "threshold": 75
  },
  "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