[T001]通信标准必要专利(SEP)智能判断
输入专利号,自动完成通信技术标准(TS)推荐、相关章节召回、权利要求对比(CC Compare)全流程,通过SSE流式返回分析进度和最终SEP判定结论。
每个SSE事件为一行 data: 开头的JSON对象,分为两类:
- PROCESSING — 心跳/进度更新,无业务数据
- FINISH — 最终结果,携带
content字段(SEP判定结论)
提供 ts 时的流程(跳过TS推荐):INIT → FIND_SECTIONS → CC_COMPARE
不提供 ts 时的流程(自动推荐TS):INIT → RECOMMEND_TS → FIND_SECTIONS → CC_COMPARE
请求参数
此 API 接口支持的参数列表
| 名称 | 类型 | 示例 | 描述 |
|---|---|---|---|
| string | EN | AI生成文本(explanation、reason等)的返回语言 |
响应结构
API 响应数据的结构说明
| 字段名 | 类型 | 示例 | 描述 |
|---|---|---|---|
data必填 | object | Please check the form: SseData | SSE事件的业务数据体 |
step | string | CC_COMPARE | 当前流程步骤。RECOMMEND_TS 仅在请求未提供ts时出现。步骤切换事件携带此字段,心跳事件不携带 |
status必填 | string | PROCESSING | PROCESSING = 处理中(无content);FINISH = 最终结果(携带content) |
content | object | Please check the form: CcCompareContent | 仅在 status=FINISH 且 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": []
}
}
] | 各TS的对比结果列表 |
pid | string | be561264-14b0-4978-ad3b-e2c961d1d687 | 内部专利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. | 参与对比的专利权利要求全文 |
error | string | External service timeout | success=false 时的错误信息 |
success | boolean | true | 该TS的CC对比是否成功 |
cc_result | object | Please check the form: CcResult | AI对该权利要求的SEP判定结果,包含是否必要、解释说明及特征级别映射明细 |
is_sep | string | 部分必要 | SEP判定结果,本地化字符串。英文:yes/no/uncertain;中文:必要/非必要/部分必要 |
explanation | string | 该权利要求涉及基于请求的无线资源协调机制,与3GPP标准中关于侧行链路(Sidelink)交互式UE协调(IUC)的功能存在对应关系。然而,标准主要描述为资源选择辅助信息(首选/非首选资源),而非明确的信道预留请求及响应流程,判定为部分必要。 | AI生成的SEP判定解释说明 |
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,"
}
] | 权利要求特征级别的映射明细 |
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"
}
}
] | 该特征对应的TS章节映射列表 |
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生成的映射理由 |
ts_code | string | TS 38.300 | 技术标准代码 |
version | string | v19.1.0 | 技术标准版本号 |
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."
] | 相关TS原文摘录 |
ts_section | array | [
"16.9.8"
] | 映射到该权利要求特征的TS章节编号列表 |
entity_mapping | object | {
"resource request": "explicit request",
"requesting device": "UE",
"responding device": "peer UE"
} | 权利要求术语与TS术语的对应关系 |
claim_feature | string | transmitting, by a requesting device, at least one resource request to a responding device, | 从权利要求中提取的单个技术特征 |
task_id必填 | string | e0a90f0b-461e-4d51-abd9-e62ad65310e1 | 任务ID,同一流中所有事件保持一致 |
status必填 | boolean | true | true = 成功,false = 错误 |
error_code必填 | integer | - | 错误码,0 = 无错误 |
成功响应示例
成功调用 API 的响应示例
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
}错误码
此接口可能返回的错误码列表
业务错误码
| 错误码 | 描述 |
|---|---|
68300004 | 请求参数异常! |
68300005 | 查询Api失败! |
68300006 | 解析基本存取错误! |
68300007 | 存在错误的请求! |
68300008 | 服务中断异常,请稍后再试! |
68300010 | 文件不符合上传规范! |
平台错误码
| 错误码 | 描述 |
|---|---|
67200000 | API整体限流错误! |
67200001 | API整体限流错误! |
67200002 | 当前调用速率过快,超过当前配置限制QPS! |
67200003 | 申请token的key和secret传参不正确或者客户端已被禁用! |
67200004 | 请求的接口无权限请联系我们的支持人员! |
67200005 | 账户余额/调用次数不足! |
67200006 | 客户端超过开通有效期! |
67200007 | 当前调用超过当天配置使用额度! |
67200008 | 请检查query参数中必填的apikey是否传输! |
67200009 | apikey与所传的bearerToken不匹配,请检查是否使用在有效期内的token! |
67200012 | 请求不合法! |
67200100 | 当前服务器状态正忙,请求响应超时! |
67200101 | 当前请求的Api不存在请检查请求Path! |
HTTP 状态码
| 状态码 | 描述 |
|---|---|
0 | 请求成功 |
401 | 未授权 |
403 | 禁止访问 |
404 | 资源不存在 |
性能指标
此接口的预期性能特征
正常响应时间
5000 ms
最大响应时间
10000 ms