[AI66-2]FTO Search - Extract Technical Features
Extract technical features based on the task_id.
Note: A valid task ID must be used, and the preceding tasks must have been successfully submitted.
Request Parameters
List of parameters supported by this API endpoint
| Name | Type | Example | Description |
|---|---|---|---|
Required | string | 80d440b7-80a5-4233-a75f-ab72b0885c88 | Task id |
Response Schema
Structure of the API response data
| Field Name | Type | Example | Description |
|---|---|---|---|
data | object | - | response data |
textRequired | string | 空调器及其除霜控制方法\n技术领域\n本发明涉及空调器及其控制技术,具体是一种空调器及其除霜控制方法。\n背景技术\n空调器在制热时,室外换热器易结霜,影响制热效果,需除霜。现有除霜结束判断依据是室外盘管温度高于设定值并持续一段时间。然而,大风天气下,室外换热器散热快,即使霜已融化,盘管温度也可能无法达到除霜退出温度,导致除霜延迟甚至无法退出,影响室内舒适度。\n技术问题\n本发明旨在解决大风天气下,现有空调器因室外换热器散热快导致除霜退出延迟或无法退出的问题。\n技术方案\n本发明提供一种空调器的除霜控制方法,包括:\n除霜运行时,获取室外风速,检测室外盘管温度。\n获取室外风速等级对应的除霜退出温度(不同风速等级对应不同退出温度,风速越高,退出温度越低)。\n当室外盘管温度高于对应风速等级的除霜退出温度时,控制空调器退出除霜。 | User input technical description text |
featuresRequired | array | [
{
"core": true,
"score": 100,
"reason": "包含主题,描述了发明的核心内容。",
"keywords": [
"空调器",
"除霜控制方法"
],
"user_add": false,
"is_select": true,
"tech_feature": "空调器及其除霜控制方法"
},
{
"core": false,
"score": 70,
"reason": "结合风速和盘管温度进行除霜控制具有一定的创新性,尤其是在大风天气下的应用。",
"keywords": [
"除霜运行",
"室外风速",
"室外盘管温度"
],
"user_add": false,
"is_select": true,
"tech_feature": "除霜运行时,获取室外风速,检测室外盘管温度"
}
] | List of technical features extracted from technical description, including feature description, keywords, score, selection status and other information |
coreRequired | boolean | true | Whether it is a core field |
scoreRequired | integer<int32> | 80 | score |
reasonRequired | string | 包含主题,描述了发明的核心内容。 | reason |
keywordsRequired | array | [
"人形机器人",
"腿部动力结构"
] | List of keywords |
user_addRequired | boolean | true | Whether to add for the user |
is_selectRequired | boolean | true | Check or not |
tech_featureRequired | string | 人形机器人的腿部动力结构 | Extracted feature words |
thresholdRequired | integer<int32> | 60 | Technical feature score threshold for filtering important technical features |
statusRequired | boolean | false | Status |
error_msg | string | The request parameter format is incorrect! | Error Message |
error_codeRequired | integer | 0 | Error Code |
Success Response Example
Example of a successful API response
JSON
{
"data": {
"text": "空调器及其除霜控制方法\\n技术领域\\n本发明涉及空调器及其控制技术,具体是一种空调器及其除霜控制方法。\\n背景技术\\n空调器在制热时,室外换热器易结霜,影响制热效果,需除霜。现有除霜结束判断依据是室外盘管温度高于设定值并持续一段时间。然而,大风天气下,室外换热器散热快,即使霜已融化,盘管温度也可能无法达到除霜退出温度,导致除霜延迟甚至无法退出,影响室内舒适度。\\n技术问题\\n本发明旨在解决大风天气下,现有空调器因室外换热器散热快导致除霜退出延迟或无法退出的问题。\\n技术方案\\n本发明提供一种空调器的除霜控制方法,包括:\\n除霜运行时,获取室外风速,检测室外盘管温度。\\n获取室外风速等级对应的除霜退出温度(不同风速等级对应不同退出温度,风速越高,退出温度越低)。\\n当室外盘管温度高于对应风速等级的除霜退出温度时,控制空调器退出除霜。",
"features": [
{
"core": true,
"score": 80,
"reason": "包含主题,描述了发明的核心内容。",
"keywords": [
"人形机器人",
"腿部动力结构"
],
"user_add": true,
"is_select": true,
"tech_feature": "人形机器人的腿部动力结构"
}
],
"threshold": 60
},
"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