[T001]AI-powered Standard Essential Patent (SEP) Analysis
Input a patent number to automatically complete TS recommendation, section recall, and Claim Chart (CC) comparison, receiving SEP determination results via Server-Sent Events.
Each SSE event is a data: line containing a JSON object. Events fall into two categories:
- PROCESSING — heartbeat/progress update, no business payload
- FINISH — final result with
contentpopulated (SEP determination conclusion)
Flow when ts is provided (skip TS recommendation): INIT → FIND_SECTIONS → CC_COMPARE
Flow when ts is omitted (auto-recommend TS): INIT → RECOMMEND_TS → FIND_SECTIONS → CC_COMPARE
Request Parameters
List of parameters supported by this API endpoint
| Name | Type | Example | Description |
|---|---|---|---|
| string | EN | Response language for AI-generated text (explanation, reason, etc.) |
Response Schema
Structure of the API response data
| Field Name | Type | Example | Description |
|---|---|---|---|
dataRequired | object | Please check the form: SseData | Business payload of the SSE event |
step | string | CC_COMPARE | Current pipeline step. RECOMMEND_TS only appears when ts is not provided in the request. Present on step-transition events; absent on heartbeat events. |
statusRequired | string | PROCESSING | PROCESSING = in progress (no content); FINISH = final result (content populated) |
content | object | Please check the form: CcCompareContent | Only present when status=FINISH and step=CC_COMPARE |
compare_results | array | [
{
"pid": "be561264-14b0-4978-ad3b-e2c961d1d687",
"claim": "1. A method comprising: transmitting, by a requesting device, at least one resource request...",
"success": true,
"cc_result": {
"is_sep": "部分必要",
"explanation": "该权利要求与3GPP标准中IUC功能存在对应关系,判定为部分必要。",
"all_mappings": []
}
}
] | List of comparison results per TS |
pid | string | be561264-14b0-4978-ad3b-e2c961d1d687 | Internal patent ID |
claim | string | 1. A method comprising:
transmitting, by a requesting device, at least one resource request to a responding device, the resource request being transmitted on a first radio channel; and
detecting, by the requesting device, a resource response on the first radio channel from the responding device after the resource request. | Full text of the patent claim being compared |
error | string | External service timeout | Error message when success=false |
success | boolean | true | Whether CC comparison succeeded for this TS |
cc_result | object | Please check the form: CcResult | AI SEP determination result for this claim, including SEP verdict, explanation, and feature-level mapping details |
is_sep | string | 部分必要 | SEP determination result. Localized string, e.g. 'yes'/'no'/'uncertain' (EN) or '必要'/'非必要'/'部分必要' (CN). |
explanation | string | 该权利要求涉及基于请求的无线资源协调机制,与3GPP标准中关于侧行链路(Sidelink)交互式UE协调(IUC)的功能存在对应关系。然而,标准主要描述为资源选择辅助信息(首选/非首选资源),而非明确的信道预留请求及响应流程,判定为部分必要。 | AI-generated explanation of the SEP determination |
all_mappings | array | [
{
"mappings": [
{
"reason": [
"Claim feature describes transmitting a request; standard describes IUC triggered by an explicit request from a peer UE."
],
"ts_code": "TS 38.300",
"version": "v19.1.0",
"ts_content": [
"The SL UE can support inter-UE coordination (IUC) in Mode 2."
],
"ts_section": [
"16.9.8"
],
"entity_mapping": {
"resource request": "explicit request",
"requesting device": "UE"
}
}
],
"claim_feature": "transmitting, by a requesting device, at least one resource request to a responding device,"
}
] | Claim feature-level mapping breakdown |
mappings | array | [
{
"reason": [
"Both involve a requesting entity initiating communication with a responding entity."
],
"ts_code": "TS 38.300",
"version": "v19.1.0",
"ts_content": [
"The SL UE can support inter-UE coordination (IUC) in Mode 2."
],
"ts_section": [
"16.9.8"
],
"entity_mapping": {
"requesting device": "UE",
"responding device": "peer UE"
}
}
] | List of TS section mappings for this claim feature |
reason | array | [
"Claim feature describes transmitting a request to another device; standard describes IUC information triggered by an explicit request from a peer UE.",
"Both involve a requesting entity initiating communication with a responding entity regarding resource status."
] | AI-generated reasoning for the mapping |
ts_code | string | TS 38.300 | Technical standard code |
version | string | v19.1.0 | Technical standard version |
ts_content | array | [
"The SL UE can support inter-UE coordination (IUC) in Mode 2, whereby a UE sends information about resources to a peer UE, which the peer UE then uses for resource (re)selection.",
"In scheme 1, the transmission of IUC information from a UE can be triggered by a condition at this UE, or by an explicit request from a peer UE."
] | Relevant TS text excerpts |
ts_section | array | [
"16.9.8"
] | TS section numbers that map to this claim feature |
entity_mapping | object | {
"resource request": "explicit request",
"requesting device": "UE",
"responding device": "peer UE"
} | Claim term → TS term correspondence |
claim_feature | string | transmitting, by a requesting device, at least one resource request to a responding device, | A single feature/element extracted from the claim |
task_idRequired | string | e0a90f0b-461e-4d51-abd9-e62ad65310e1 | Task ID, consistent across all events in the stream |
statusRequired | boolean | true | true = success, false = error |
error_codeRequired | integer | - | Error code, 0 = no error |
Success Response Example
Example of a successful API response
JSON
{
"data": {
"step": "CC_COMPARE",
"status": "PROCESSING",
"content": {
"compare_results": [
{
"pid": "be561264-14b0-4978-ad3b-e2c961d1d687",
"claim": "1. A method comprising:\ntransmitting, by a requesting device, at least one resource request to a responding device, the resource request being transmitted on a first radio channel; and\ndetecting, by the requesting device, a resource response on the first radio channel from the responding device after the resource request.",
"error": "External service timeout",
"success": true,
"cc_result": {
"is_sep": "部分必要",
"explanation": "该权利要求涉及基于请求的无线资源协调机制,与3GPP标准中关于侧行链路(Sidelink)交互式UE协调(IUC)的功能存在对应关系。然而,标准主要描述为资源选择辅助信息(首选/非首选资源),而非明确的信道预留请求及响应流程,判定为部分必要。",
"all_mappings": [
{
"mappings": [
{
"reason": [
"Claim feature describes transmitting a request to another device; standard describes IUC information triggered by an explicit request from a peer UE.",
"Both involve a requesting entity initiating communication with a responding entity regarding resource status."
],
"ts_code": "TS 38.300",
"version": "v19.1.0",
"ts_content": [
"The SL UE can support inter-UE coordination (IUC) in Mode 2, whereby a UE sends information about resources to a peer UE, which the peer UE then uses for resource (re)selection.",
"In scheme 1, the transmission of IUC information from a UE can be triggered by a condition at this UE, or by an explicit request from a peer UE."
],
"ts_section": [
"16.9.8"
],
"entity_mapping": {
"resource request": "explicit request",
"requesting device": "UE",
"responding device": "peer UE"
}
}
],
"claim_feature": "transmitting, by a requesting device, at least one resource request to a responding device,"
}
]
}
}
]
},
"task_id": "e0a90f0b-461e-4d51-abd9-e62ad65310e1"
},
"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 |
401 | Unauthorized |
403 | Forbidden |
404 | Not Found |