From 5e163c4bb79ba2127f5a126f19cb81d63d4219e2 Mon Sep 17 00:00:00 2001
From: stu2not <stu2not@stu2notdeMac-mini.local>
Date: Sun, 20 Sep 2026 12:03:40 +0800
Subject: [PATCH] =?UTF-8?q?docs:=20=E4=B8=BA006=E7=BB=91=E5=AE=9A=E5=9B=9E?=
 =?UTF-8?q?=E6=89=A7=E5=A2=9E=E5=8A=A0ICCID?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/architecture/03-binding-flow.md | 25 ++++++-------------------
 talkingq-url/docs/mqtt协议_V2.0.txt  | 21 +++++++++++++--------
 2 files changed, 19 insertions(+), 27 deletions(-)

diff --git a/docs/architecture/03-binding-flow.md b/docs/architecture/03-binding-flow.md
index 2edc8a2..2ff73ef 100644
--- a/docs/architecture/03-binding-flow.md
+++ b/docs/architecture/03-binding-flow.md
@@ -54,22 +54,7 @@ sequenceDiagram
 
 ## Binding Response (V2.0)
 
-The current V2.0 protocol defines the successful `msg_id=006` response as:
-
-```json
-{
-  "msg_id": "006",
-  "status": "success",
-  "data": {
-    "uuid": "53D22B6DA20001"
-  }
-}
-```
-
-The V2.0 response does not define an `iccid` field. Adding ICCID to the
-binding receipt is therefore a protocol extension that requires coordinated
-firmware and backend changes. A compatible proposal is to add it under
-`data`, while preserving the existing `status` and `data.uuid` fields:
+The V2.0 protocol defines the successful `msg_id=006` response as:
 
 ```json
 {
@@ -83,9 +68,11 @@ firmware and backend changes. A compatible proposal is to add it under
 ```
 
 The ICCID must come from the authoritative IMEI-to-ICCID provisioning record
-or a validated device report; it must not be derived from the IMEI. This
-proposed field is not part of the current V2.0 contract until both sides
-accept and implement the extension.
+The `iccid` field is now part of the documented `006` success receipt. It must
+come from the authoritative IMEI-to-ICCID provisioning record or a validated
+device report; it must not be derived from the IMEI. Firmware and backend
+runtime support still need to be deployed together before this field can be
+relied on in production.
 
 ## Related Tables
 
diff --git a/talkingq-url/docs/mqtt协议_V2.0.txt b/talkingq-url/docs/mqtt协议_V2.0.txt
index e4e416f..ddcd455 100644
--- a/talkingq-url/docs/mqtt协议_V2.0.txt
+++ b/talkingq-url/docs/mqtt协议_V2.0.txt
@@ -158,14 +158,19 @@ device/imei/command
   "msg_id": "006"
 }
 device/imei/response
-4G模块响应：
-{
-  "msg_id": "006",
-  "status": "success",
-   "data": {
-    "uuid": "53D22B6DA20001"
-   }
-}
+4G模块响应：
+{
+  "msg_id": "006",
+  "status": "success",
+   "data": {
+    "uuid": "53D22B6DA20001",
+    "iccid": "898604E91123D1334901"
+   }
+}
+
+其中 `iccid` 为完成绑定的设备 SIM 卡 ICCID，由设备或后端登记数据提供，
+必须使用完整值，不得根据 IMEI 推导。旧设备如果未上报该字段，后端应按协议
+兼容策略处理；支持新版协议的设备绑定成功回执必须返回 `iccid`。
 
 7、开关状态
 //0查询状态   1 控制打开    2控制关闭