[T001]AI-powered Standard Essential Patent (SEP) Analysis

post
https://connect.patsnap.com/open_api/task/aicc
Try in Sandbox

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 content populated (SEP determination conclusion)

Flow when ts is provided (skip TS recommendation): INITFIND_SECTIONSCC_COMPARE

Flow when ts is omitted (auto-recommend TS): INITRECOMMEND_TSFIND_SECTIONSCC_COMPARE

Request Parameters

List of parameters supported by this API endpoint

NameTypeExampleDescription
x-site-lang
stringEN
Response language for AI-generated text (explanation, reason, etc.)

Response Schema

Structure of the API response data

Field NameTypeExampleDescription
data
Required
objectPlease check the form: SseData
Business payload of the SSE event
step
stringCC_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.
status
Required
stringPROCESSING
PROCESSING = in progress (no content); FINISH = final result (content populated)
content
objectPlease 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
stringbe561264-14b0-4978-ad3b-e2c961d1d687
Internal patent ID
claim
string1. 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
stringExternal service timeout
Error message when success=false
success
booleantrue
Whether CC comparison succeeded for this TS
cc_result
objectPlease 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
stringTS 38.300
Technical standard code
version
stringv19.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
stringtransmitting, by a requesting device, at least one resource request to a responding device,
A single feature/element extracted from the claim
task_id
Required
stringe0a90f0b-461e-4d51-abd9-e62ad65310e1
Task ID, consistent across all events in the stream
status
Required
booleantrue
true = success, false = error
error_code
Required
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 CodeDescription
68300004Invalid parameter!
68300005Search api failure!
68300006Analytic basic access error!
68300007Bad request!
68300008Service error, please try again later!
68300010The file does not comply with upload specifications!

Platform Errors

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

HTTP Status Codes

Status CodeDescription
0Success
401Unauthorized
403Forbidden
404Not Found