客户版 · 仿真验证CUSTOMER EDITION · SIMULATION VERIFICATION
USB 3.2 Device IP 测试范围说明USB 3.2 Device IP Verification Test Scope
按功能归并已执行的仿真测试主题，涵盖链路层、协议层、端点传输、链路训练、错误处理及压力场景。本清单汇总已执行范围，不列逐项通过／失败结论，也不代表已完成全部回归或认证。Simulation test topics performed, grouped by functional area: link layer, protocol layer, endpoint traffic, link training, error handling and stress scenarios. This inventory summarizes performed scope; it does not provide item-by-item pass/fail results, complete regression sign-off, or certification.
测试范围概览Overview of performed tests
端到端业务仿真主要针对 Gen2x2（20 Gbit/s）、控制端点 EP0，以及 EP1 Bulk IN / OUT。Gen2x1（10 Gbit/s）与 Gen1x1（5 Gbit/s）另有选定的协商、训练和接口级场景。End-to-end traffic simulations primarily target Gen2x2 (20 Gbit/s), control endpoint EP0, and EP1 Bulk IN / OUT. Selected negotiation, training and interface-level scenarios also address Gen2x1 (10 Gbit/s) and Gen1x1 (5 Gbit/s).
阅读说明：Reading note:
本清单汇总不同验证阶段已执行的测试内容，不列逐项通过／失败结论，不代表同一版本已完成全部回归。执行范围不等于完整 USB-IF CTS、USB3CV 或电气一致性认证。This inventory summarizes tests performed across verification stages. It does not provide item-by-item pass/fail results or establish a complete regression sign-off for a single revision. The listed scope does not constitute full USB-IF CTS, USB3CV or electrical compliance certification.
编号说明：Reference key:
下表逐项区分 CTS 相关场景、协议正文派生和自定义测试。CTS 编号仅说明对应关系，不代表完成该条全部步骤或获得认证；同一 TD 可以关联多个主题，不重复计为多项 CTS。Each topic distinguishes CTS-related scenarios, base-specification-derived tests and custom tests. A CTS reference identifies a relationship, not completion of every step or certification. Multiple topics may refer to one TD and do not count as multiple CTS tests.
基础事务与报文Baseline transactions and packet handling
| 测试内容Tests performed | CTS／规范依据及覆盖边界CTS / specification reference and scope |
|---|---|
基本枚举流程 SET_ADDRESS、GET_DESCRIPTOR 与 SET_CONFIGURATION 事务。 Baseline enumeration SET_ADDRESS, GET_DESCRIPTOR and SET_CONFIGURATION transactions. | 仅枚举与配置的基础事务子集；不是完整 USB3CV 测试。Baseline enumeration and configuration transactions only; not a complete USB3CV execution. |
Host 事务包输入 ACK、NRDY、ERDY、STALL 与 PING 报文发送、接收及选定响应检查。 Host transaction-packet inputs Transmission and reception of ACK, NRDY, ERDY, STALL and PING, with selected response checks. | 协议正文派生；基础发包与选定回复，无独立 CTS TD 对应。Specification-derived packet generation and selected responses; no standalone CTS TD assigned. |
数据包基本传输 DPH 与 DPP 组合传输，以及描述符和 Bulk 数据的长度、内容与校验。 Basic data-packet transfers Combined DPH and DPP transfers, including length, content and integrity checks for descriptor and Bulk data. | 协议正文派生；数据包基础传输。Specification-derived baseline data transfers. |
基本链路命令 LGOOD、LBAD、LRTY、Type1 / Type2 LCRD 的报文处理。 Basic link commands Handling of LGOOD, LBAD, LRTY and Type1 / Type2 LCRD commands. | 链路基本功能；专项错误场景见第 02 类所列 CTS。Baseline link functionality; see category 02 for CTS-related fault scenarios. |
基本双向端点业务 EP1 Bulk OUT、Bulk IN 及 IN / OUT 交替传输。 Baseline bidirectional endpoint traffic EP1 Bulk OUT, Bulk IN and alternating IN / OUT transfers. | 协议正文派生；不是 Host 控制器 Bulk Loopback CTS。Specification-derived; not a host-controller Bulk Loopback CTS test. |
基础发包覆盖不等于每一种 TP 的完整端点状态流程均已验证。Baseline packet-generation coverage does not establish complete endpoint-state coverage for every TP type.
链路完整性、序号与流控Link integrity, sequence handling and flow control
| 测试内容Tests performed | CTS／规范依据及覆盖边界CTS / specification reference and scope |
|---|---|
链路命令起始定界容错 起始序列中不同 symbol 位置的单符号错误输入。 Link-command start-framing tolerance Single-symbol faults at different positions in the start sequence. | LCSTART 单 symbol 错误场景子集。LCSTART single-symbol fault scenario subset. |
HP 起始定界容错 不同起始 symbol 的错误、有效起始识别及无效起始拒绝场景。 Header-packet start-framing tolerance Faults in different start symbols, valid-start recognition and invalid-start rejection scenarios. | HPSTART 定界容错场景子集。HPSTART framing-tolerance scenario subset. |
LCW 副本校验与选择 单副本 CRC 错误、双副本 CRC 错误，以及两副本 CRC 正确但内容不同。 LCW copy validation and selection One invalid CRC copy, two invalid CRC copies, and differing copies with individually valid CRCs. | TD 7.3：副本 CRC5；TD 7.4：两副本均有效但内容不同。TD 7.3: copy CRC5 checks; TD 7.4: valid copies with conflicting contents. |
Header CRC 错误响应 HP CRC16 与 LCW CRC5 错误注入、LBAD 响应及后续修复传输。 Header CRC error responses HP CRC16 and LCW CRC5 fault injection, LBAD responses and subsequent corrected transmissions. | 接收重试相关子集；CRC16 注入含扩展场景。Receive-retry subset, including additional CRC16 injection scenarios. |
HP 序号 正常推进、跳号、回绕与重传期间序号保持。 HP sequence handling Normal progression, skipped sequence numbers, wraparound and sequence retention during replay. | 错误 HP 序号场景子集，另含正常递增、回绕及重传扩展。Wrong-HP-sequence subset plus progression, wraparound and replay extensions. |
Type1 / Type2 credit 独立 credit 返回、编号顺序、异常编号及重传前 credit 可用性。 Type1 / Type2 credits Independent credit return, credit-number ordering, invalid credit numbers and credit availability before replay. | Type1 / Type2 错误 credit 序号子集，另含可用数量检查。Type1 / Type2 credit-sequence fault subset plus credit-availability checks. |
接收方向链路重试 Device 发 LBAD、Host 发 LRTY；区分重试边界前的旧报文与边界后的修复报文。 Receive-side link retry Device-generated LBAD followed by Host LRTY; distinction between earlier packets and corrected packets after the retry boundary. | 接收重试子集；附加旧包 / 新包与 LRTY 边界检查。Receive-retry subset with additional old/new packet and LRTY boundary checks. |
发送方向链路重试 Host 发 LBAD、Device 发 LRTY；单个及混合 HP 重传的顺序和内容。 Transmit-side link retry Host-generated LBAD followed by Device LRTY; replay ordering and content for individual and mixed header packets. | 发送重试子集，扩展到单个及混合 HP。Transmit-retry subset extended to individual and mixed HP traffic. |
空待重传集合 不存在未确认 HP 时收到 LBAD 的响应。 Empty pending-replay set Response to LBAD when no unacknowledged header packet is pending. | TD 相关断言扩展：空待重传集合收到 LBAD。Associated assertion extension: LBAD with no outstanding replay headers. |
重传与新包的次序 待发送新包、已确认前缀、序号回绕和重复 LBAD 交叠场景。 Replay versus new-packet ordering Pending new packets, acknowledged prefixes, sequence wraparound and overlapping repeated-LBAD scenarios. | 自定义次序压力扩展；不是该 TD 的完整官方步骤。Custom ordering-stress extension, not the complete official TD procedure. |
重传 credit 语义 LRTY 重传与 Recovery 后重传的 credit 处理区别。 Replay credit semantics Credit-accounting distinctions between LRTY replay and replay after Recovery. | 重试与 Recovery 的 credit 语义扩展；各 TD 仅相关场景。Credit-accounting extensions across retry and Recovery; related scenarios only. |
头部独立重传 TP / DPH 的 DL 字段、头部内容和序号；DPH 链路重传不附带 DPP。 Header-only replay DL fields, header identity and sequence numbers for TP / DPH replay; DPH link replay without an accompanying DPP. | TP / DPH、DL 与无 DPP 重传的相关场景扩展。Related extensions for TP / DPH, DL and header-only replay without DPP. |
链路命令突发与背压 连续命令、命令与 HP 交叠、排队及处理次序。 Link-command bursts and backpressure Consecutive commands, command / HP overlap, queued traffic and processing order. | 自定义命令突发、背压和顺序压力；无独立 CTS TD。Custom command-burst, backpressure and ordering stress; no standalone CTS TD. |
接收对齐与报文边界Receive alignment and packet boundaries
| 测试内容Tests performed | CTS／规范依据及覆盖边界CTS / specification reference and scope |
|---|---|
任意字节起始位置 128-bit 接收数据块内的 0～15 字节起点及原 DWORD 对齐位置。 Arbitrary byte start positions Start offsets 0–15 within a 128-bit receive block, including DWORD-aligned positions. | 0–15 字节位置子集；不声明完成全流程及 50 ms 驻留。Byte positions 0–15 subset; full procedure and 50 ms dwell are not claimed. |
跨块定界与字段 起始序列、HP 及链路命令字段跨越接收数据块的情况。 Cross-block framing and fields Start sequences, headers and link-command fields spanning receive-block boundaries. | 跨块接收扩展；不是独立新增的 CTS 条目。Cross-block reception extension, not an additional official CTS item. |
报文与链路命令独立对齐 HP / DPH / DPP 与链路命令在混合流中的独立定位和次序。 Independent packet and command alignment Independent identification and ordering of HP / DPH / DPP and link commands in mixed streams. | 相关对齐扩展；分别检查报文和链路命令。Related alignment extension checking packets and link commands separately. |
连续报文与相位变化 同相位及变相位连续报文、紧邻 HP、不同包间空闲长度。 Consecutive packets and phase changes Consecutive packets at unchanged and changing phases, closely spaced headers and varying inter-packet idle lengths. | 连续变相位与包间距压力扩展。Stress extension with consecutive phase changes and varying packet spacing. |
Payload 伪定界图样 数据中包含与起始序列相同或符合 3-of-4 匹配的图样，包括类似链路重试命令的内容。 Framing-like payload patterns Payload patterns identical to start sequences or matching a 3-of-4 criterion, including patterns resembling link-retry commands. | 自定义 payload 伪定界防误判测试；不冒用 framing 容错 TD。Custom payload false-framing checks; not labeled as a framing-fault CTS TD. |
长度与字节相位组合 零长度、短包、边界长度及最大长度包与起始字节相位的选定交叉矩阵。 Length and byte-phase combinations Selected cross-matrices of zero-length, short, boundary-length and maximum-length packets against starting byte phase. | 长度 × 相位的选定组合扩展，不是全组合 CTS。Selected length-by-phase matrix extension, not exhaustive CTS coverage. |
连续输入及有效空拍 正常链路停顿、接收有效空拍及高负载 DP / 链路命令混合流。 Continuous input and valid-data gaps Normal link stalls, receive-valid gaps and heavily loaded mixed DP / link-command streams. | 持续流量与有效空拍的压力扩展。Stress extension with sustained traffic and valid-data gaps. |
报文中断边界 接收中途退出 U0、部分 HP / DPP 中断及恢复后的报文边界处理。 Interrupted-packet boundaries U0 exit during reception, interrupted HP / DPP traffic and packet-boundary handling after recovery. | 自定义中断与重新进入边界检查；无独立 CTS TD。Custom interruption and re-entry boundary checks; no standalone CTS TD. |
控制端点与回复语义Control-endpoint and response semantics
| 测试内容Tests performed | CTS／规范依据及覆盖边界CTS / specification reference and scope |
|---|---|
控制端点回复字段 EP0 NRDY 的方向字段及保留位；零长度数据包的方向、EOB、端点、类型、序号与长度。 Control-endpoint response fields Direction and reserved fields in EP0 NRDY; direction, EOB, endpoint, type, sequence and length for zero-length data packets. | 协议正文派生：EP0 NRDY 及零长度 DP 字段。Specification-derived EP0 NRDY and zero-length DP field checks. |
STATUS 与端点交错 控制传输中穿插 Bulk OUT 后，STATUS ACK 的事务类型和字段。 STATUS with interleaved endpoint traffic Transaction type and fields of STATUS ACK after Bulk OUT traffic is interleaved with a control transfer. | 协议正文派生，附加端点交错场景。Specification-derived, with endpoint-interleaving extensions. |
Deferred STATUS 已就绪、等待应用完成、ERDY 后重新请求，以及 halted 控制请求的处理。 Deferred STATUS Ready and application-pending conditions, renewed requests following ERDY, and handling of halted control requests. | 协议正文派生：Deferred STATUS 流程及回复。Specification-derived Deferred STATUS flow and responses. |
新 SETUP 与状态阶段副作用 新 SETUP 对旧控制事务的替代，以及地址更新与有效状态阶段完成的关联。 New SETUP and status-stage side effects Replacement of an earlier control transaction by a new SETUP, and address updates associated with valid status-stage completion. | 协议正文派生的新 SETUP / STATUS 边界；不是完整枚举 CTS。Specification-derived new-SETUP / STATUS boundaries; not a complete enumeration CTS. |
PING_RESPONSE 对应关系 不同端点及方向的 PING，在连续请求和背压下的回复字段与顺序。 PING_RESPONSE association Response fields and ordering for PINGs targeting different endpoints and directions under consecutive requests and backpressure. | 协议正文派生，附加请求交错与背压检查。Specification-derived, with request-interleaving and backpressure checks. |
STALL 与成功接收的互斥 已 halted 端点接收 OUT 时的 STALL、成功 ACK、数据交付与序号行为。 Mutual exclusion of STALL and successful acceptance STALL, successful ACK, data delivery and sequence behavior for OUT traffic to a halted endpoint. | EP0 STALL 回复语义检查；不宣称完成 USB3CV 端点 Halt 测试。EP0 STALL-response semantics; no claim of completing the USB3CV endpoint-halt test. |
Host ACK 方向检查 错误方向 ACK 在无数据、数据已就绪及传输进行中场景下的处理。 Host ACK direction validation Handling of wrong-direction ACKs when data is unavailable, ready or already in transit. | 协议正文派生的错误方向输入检查。Specification-derived wrong-direction input checks. |
控制数据序号 SETUP 序号、后续 DATA 阶段初始序号与新控制事务的重新初始化。 Control-transfer data sequence SETUP sequence numbers, the initial sequence of the subsequent DATA stage and reinitialization for a new control transfer. | 协议正文派生的控制传输序号检查。Specification-derived control-transfer sequence checks. |
部分字段检查在协议接口层进行，不等同于各速率下完整的端到端控制传输认证。Some field checks are performed at the protocol interface and do not constitute complete end-to-end control-transfer certification at every rate.
Bulk 端点协议与流控Bulk endpoint protocol and flow control
| 测试内容Tests performed | CTS／规范依据及覆盖边界CTS / specification reference and scope |
|---|---|
持续 Bulk IN / OUT 1024 字节满包、单方向连续传输及双方向交替传输。 Sustained Bulk IN / OUT 1024-byte full packets, continuous unidirectional traffic and alternating bidirectional traffic. | 协议正文派生及持续业务扩展。Specification-derived with sustained-traffic extensions. |
零长度及短包 ZLP、不同短包长度、最大包长附近边界及有效数据内容检查。 Zero-length and short packets ZLPs, varying short-packet lengths, boundaries near the maximum packet size and payload-content checks. | 协议正文派生的 ZLP / 短包场景。Specification-derived ZLP and short-packet scenarios. |
紧贴 ZLP / 短包 零长度与短数据包的两种先后顺序、多字节起始相位及最小间隔场景。 Closely spaced ZLP / short packets Both ordering combinations of zero-length and short data packets, multiple byte phases and minimum-gap scenarios. | 短包协议场景 × 字节相位压力扩展；CTS 仅指相关对齐维度。Short-packet scenarios crossed with byte-phase stress; CTS relates only to alignment. |
DPH 数据序号 期望序号、初始错误序号、重复包、跳号、31→0 回绕及交付唯一性。 DPH data sequence Expected and invalid initial sequence numbers, duplicates, skipped numbers, 31-to-0 wraparound and exactly-once delivery checks. | 协议正文派生：错误、重复、跳号及模 32 回绕。Specification-derived wrong, duplicate, skipped and modulo-32 sequence checks. |
DPP CRC 错误与协议重试 坏数据拒绝、Retry 响应、同一数据序号重发及内容保持。 DPP CRC faults and protocol retry Rejection of corrupted data, Retry responses, retransmission with the same data sequence and payload preservation. | 协议层 DPP CRC / ACK Retry；不是 TD 7.7 的 HP 链路重试。Protocol DPP CRC / ACK Retry, distinct from TD 7.7 HP link retry. |
NRDY → ERDY → 重试 接收端暂不可用、资源释放、再次就绪通知及后续 OUT 恢复。 NRDY → ERDY → retry Temporary receiver unavailability, resource release, readiness notification and subsequent OUT resumption. | 协议正文派生的端点流控及恢复就绪。Specification-derived endpoint flow control and restored readiness. |
重复就绪周期 连续多轮不可用 / 就绪变化、Deferred 数据请求与 ERDY 请求处理。 Repeated readiness cycles Repeated not-ready / ready transitions, deferred data requests and ERDY request handling. | 协议正文派生，附加重复就绪与等待边界。Specification-derived, with repeated-readiness and waiting-boundary extensions. |
端点回复关联 端点业务交错及回复受背压时，ACK、NRDY、Retry 的端点、方向与序号对应关系。 Endpoint-response association Endpoint, direction and sequence association for ACK, NRDY and Retry under interleaved traffic and response backpressure. | 协议正文派生，附加端点交错与回复关联。Specification-derived, with endpoint-interleaving and response-association extensions. |
ACK 积压与发送背压 应答积压、资源达到容量边界、恢复接收以及应答完整性和顺序。 ACK backlog and transmit backpressure Accumulated responses, capacity boundaries, resumed reception, and response completeness and ordering. | 自定义背压与 ACK 积压压力；无独立 CTS TD。Custom backpressure and ACK-backlog stress; no standalone CTS TD. |
NumP 窗口 1、2、7、16 包窗口、连续突发、NumP=0 关闭窗口及后续重新请求。 NumP windows Windows of 1, 2, 7 and 16 packets, consecutive bursts, window closure with NumP=0 and subsequent renewed requests. | 协议正文派生的突发窗口与重开。Specification-derived burst-window and reopening checks. |
连续 IN 的紧邻 ACK 两包或四包 ACK 连续到达、包间距及对发送中数据流的交叠。 Closely spaced ACKs during continuous IN Trains of two or four ACKs, inter-header spacing and overlap with outgoing data traffic. | 自定义紧邻 ACK 压力，基于 Bulk IN 协议；无独立 CTS TD。Custom adjacent-ACK stress based on Bulk IN protocol; no standalone CTS TD. |
EOB 与传输结束 持续供数、有限数据提交、最后数据包、窗口重开及连续发送。 EOB and transfer termination Sustained data availability, finite submitted transfers, final packets, window reopening and continuous transmission. | 协议正文派生，附加连续传输与提交边界。Specification-derived, with continuous-transfer and submission-boundary extensions. |
重传、Recovery 与错误压力Retry, Recovery and fault-injection stress
| 测试内容Tests performed | CTS／规范依据及覆盖边界CTS / specification reference and scope |
|---|---|
双向链路重试 Host 或 Device 发起 LBAD / LRTY，并与 Bulk IN / OUT 业务组合。 Bidirectional link retry Host- or Device-initiated LBAD / LRTY sequences combined with Bulk IN / OUT traffic. | 两个方向的重试相关场景与 Bulk 组合压力。Retry-related scenarios in both directions combined with Bulk stress. |
连续 Header 错误 连续 HP CRC 故障、重试次数与进入 Recovery 的响应。 Consecutive header faults Consecutive HP CRC faults, retry responses and transition into Recovery. | 连续错误触发 Recovery 的场景子集；CRC16 含扩展。Consecutive-error Recovery scenario subset, including CRC16 extensions. |
未确认 Header 超时 缺少 LGOOD 时的超时、Recovery、返回 U0 后重传及后续业务。 Unacknowledged-header timeout Timeout without LGOOD, Recovery, replay after return to U0 and follow-on traffic. | 未确认 HP 超时场景子集，附加恢复后重传。Unacknowledged-HP timeout subset with post-recovery replay extensions. |
Recovery 后业务连续性 重新建立链路序号 / credit 交互，以及端点数据序号、重试与 IN / OUT 恢复。 Traffic continuity after Recovery Re-established link sequence / credit exchanges, endpoint data sequences, retries and resumed IN / OUT traffic. | Recovery → U0 相关场景与业务恢复扩展。Recovery-to-U0 related scenarios with traffic-resumption extensions. |
混合错误压力 CRC 错误、双向链路重试、协议 Retry 与周期性 Recovery 的可重复组合。 Mixed-error stress Reproducible combinations of CRC faults, bidirectional link retry, protocol Retry and periodic Recovery. | 自定义组合压力；所列 TD 标明组成机制，不代表整套 CTS。Custom combined stress; TDs identify component mechanisms, not complete CTS execution. |
大数据量 OUT 联合压力 1 MiB 连续满包业务，叠加错误注入、不同接收消费速度、NRDY / ERDY 与 Recovery。 Large-volume combined OUT stress 1 MiB of continuous full-packet traffic with fault injection, varying receive-consumption rates, NRDY / ERDY and Recovery. | 1 MiB 自定义压力；TD 仅对应其中重试与恢复机制。Custom 1 MiB stress; TDs identify only the retry and recovery mechanisms. |
在途数据重试 错误包之后仍有未确认数据包时，首个未确认序号、重发范围及避免重复交付。 Retry with data in flight First-unacknowledged sequence handling, retransmission range and duplicate-delivery checks when later packets remain outstanding. | 协议正文派生的在途重试扩展，无独立 CTS TD。Specification-derived in-flight protocol-retry extension; no standalone CTS TD. |
Recovery 中断 DPP 不同数据截断点、字节相位和恢复时序；等待 Retry 后重发完整数据包的选定组合。 DPP interruption by Recovery Selected combinations of payload interruption points, byte phases and recovery timing, followed by full-packet retransmission after Retry. | 自定义 DPP 截断与恢复组合；不是 TD 7.26 的完整步骤。Custom DPP interruption / recovery combination, not the full TD 7.26 procedure. |
非正常输入健壮性探测 额外 LRTY、密集重复 LBAD 及提前重发场景的行为观察。 Abnormal-input robustness probes Behavioral observations under additional LRTY commands, closely repeated LBADs and premature retransmission scenarios. | 自定义健壮性观察；非正常 LRTY 不定义为 CTS 必通过行为。Custom robustness observation; abnormal LRTY is not assigned mandatory CTS behavior. |
错误压力为报文级故障注入，不是物理通道 BER 测量。探索性或不符合正常握手顺序的输入不作为规范必通过项。Fault stress uses packet-level injection, not physical-channel BER measurement. Exploratory inputs or inputs outside normal handshake ordering are not treated as mandatory compliance pass criteria.
链路训练与速率协商Link training state machine and rate negotiation
| 测试内容Tests performed | CTS／规范依据及覆盖边界CTS / specification reference and scope |
|---|---|
初始训练与 U0 Gen2x2 启动协商、进入 U0 及稳定观察。 Initial training and U0 Gen2x2 startup negotiation, U0 entry and stable-state observation. | 启动与 U0 功能子集，不等于全部子测试。Startup and U0 functional subset, not all bring-up subtests. |
Recovery.Active TS1 / TS2 接收数量、同类型连续性、不足数量与类型切换。 Recovery.Active TS1 / TS2 receive counts, consecutive same-type sequences, insufficient counts and sequence-type changes. | 接收数量、连续性和发送选择的接口子集。Interface subset for receive counts, continuity and transmit selection. |
Recovery.Configuration TS2 发送选择、接收门限、发送完成门限及中断后重新计数。 Recovery.Configuration TS2 transmission selection, receive and transmit-completion thresholds, and restart after interruption. | TS2 握手门限与完成条件的接口子集。Interface subset for TS2 handshake thresholds and completion conditions. |
不同发送 / 接收节奏 接收先完成、发送先完成、发送暂停与慢速有序集完成事件。 Different transmit / receive timing Receive-first and transmit-first completion, paused transmission and slow ordered-set completion events. | 步骤 4–6 接口发送 / 接收节奏的附加边界场景。Additional interface transmit / receive timing-boundary scenarios. |
Recovery 超时 Active、Configuration 和 Idle 阶段的超时路径。 Recovery timeouts Timeout paths in Active, Configuration and Idle phases. | Active / Configuration 为相关超时子集；Idle 超时依据协议正文。Related Active / Configuration timeout subset; Idle timeout derives from the base specification. |
Recovery 往返 U0 接收训练序列后的转移、重复 Recovery → U0 及返回后的业务测试。 Recovery round trips Transitions triggered by training sequences in U0, repeated Recovery-to-U0 cycles and follow-on traffic tests. | Recovery 往返相关子集及重复恢复扩展。Related Recovery round-trip subset with repeated-recovery extensions. |
低功耗退出 U1 / U2 / U3 的 LFPS 包络响应、持续时间及接口级返回路径。 Low-power exit LFPS envelope responses, response duration and interface-level return paths from U1 / U2 / U3. | U1 / U2 的步骤 8、U3 的步骤 7 所涉 LFPS 包络子集；不含完整 PM 握手。LFPS envelope subsets related to step 8 for U1 / U2 and step 7 for U3; not full PM handshakes. |
Hot Reset 边界 U0 及 Recovery.Idle 的接口级 Hot Reset 场景，以及同时出现其他完成条件的情况。 Hot Reset boundaries Interface-level Hot Reset scenarios in U0 and Recovery.Idle, including coincident completion conditions. | 仅接口功能相关及并发边界；未宣称完成线上 Reset 位检测流程。Interface-related functionality and coincident boundaries only; full on-wire Reset-bit detection is not claimed. |
VBUS 撤销观察 撤销 VBUS 后的接口级状态行为观察。 VBUS-deassertion observation Interface-level observation of state behavior following VBUS deassertion. | 自定义接口状态观察，需结合供电 / 顶层适用性；无独立 CTS TD。Custom interface-state observation subject to power / top-level applicability; no standalone CTS TD. |
5 Gbit/s 兼容协商 仅发送普通 LFPS 的对端，不同重复周期及有限数量 LFPS 后停止的场景。 5 Gbit/s compatibility negotiation Peers sending ordinary LFPS only, with varying repetition periods and finite LFPS sequences followed by silence. | 普通 LFPS 协商与有限突发场景子集。Ordinary-LFPS negotiation and finite-burst scenario subsets. |
静默回退及误判防护 静默窗口前后的转移条件、少量 LFPS，以及有效 SCD 识别与普通 LFPS 区分。 Quiet-period fallback and false-detection checks Transition conditions around the quiet interval, limited LFPS observations, and distinction between valid SCD patterns and ordinary LFPS. | 回退条件子集与误判防护扩展。Fallback-condition subsets and false-detection extensions. |
10 Gbit/s 对端能力 不支持双通道 20 Gbit/s 的对端通过 SCD / LBPM 协商 Gen2x1。 10 Gbit/s peer capability SCD / LBPM negotiation of Gen2x1 with a peer that does not support dual-lane 20 Gbit/s operation. | Gen2x1 能力协商的相关功能子集。Related functional subset for Gen2x1 capability negotiation. |
Gen1 能力通告与 LFPSPlus 回退 对端通告 Gen1 能力、LFPSPlus 阶段撤回增强模式及后续训练。 Gen1 capability advertisement and LFPSPlus fallback Peer advertisement of Gen1 capability, withdrawal of enhanced signaling during LFPSPlus and subsequent training. | 能力协商与回退扩展，不标为完整 PortMatch Retry CTS。Capability-negotiation and fallback extensions, not a complete PortMatch Retry CTS. |
SCD 起始相位 SCD1 / SCD2 不同循环起始相位及易混淆 LFPS 周期组合。 SCD starting phase Different cyclic starting phases of SCD1 / SCD2 and potentially ambiguous LFPS period combinations. | 自定义 SCD 相位和误识别扩展。Custom SCD-phase and false-detection extensions. |
切速与 PHY 就绪 速率确认延迟、确认缺失、切速期间 PHY 暂不可用，以及电源确认和 PHY 就绪不同步。 Rate switching and PHY readiness Delayed or missing rate confirmation, temporary PHY unavailability during rate changes, and non-coincident power confirmation and PHY readiness. | 自定义 PHY 接口应答边界；无独立 CTS TD。Custom PHY-interface acknowledgement boundaries; no standalone CTS TD. |
Gen1 训练及重新协商 选定的完整 TSEQ 发送、TS1 / TS2 / Idle 训练、Recovery 往返，以及复位后重新协商较高速率。 Gen1 training and renegotiation Selected full-length TSEQ transmission, TS1 / TS2 / Idle training, Recovery round trips and renegotiation of a higher rate after reset. | 选定 Gen1 训练 / Recovery 集成子集，附加复位后重新协商。Selected Gen1 training / Recovery integration subsets plus post-reset renegotiation. |
训练到正常业务的交接 有序集完成边界、SDS 发送及重新进入 U0 后的链路初始化和业务恢复。 Handover from training to normal traffic Ordered-set completion boundaries, SDS transmission, and link initialization and traffic resumption after U0 re-entry. | 步骤 TD 7.26: 7–8 训练交接与 U0 初始化相关子集，含选定业务恢复检查。Related training-handover and U0-initialization subsets with selected traffic-resumption checks. |
接口级低功耗、复位和 VBUS 场景不等于完整线上握手或电气行为认证；选定 Gen1 PIPE 场景也不代表所有 Host 互通组合已覆盖。Interface-level low-power, reset and VBUS scenarios do not establish complete on-wire handshake or electrical compliance. Selected Gen1 PIPE scenarios do not establish coverage of all Host interoperability combinations.
持续传输与性能评估Sustained traffic, backpressure and performance evaluation
| 测试内容Tests performed | CTS／规范依据及覆盖边界CTS / specification reference and scope |
|---|---|
大块连续业务 4 MiB Bulk IN / OUT、1024 字节连续满包，以及跨应用提交边界的传输。 Large sustained transfers 4 MiB Bulk IN / OUT, consecutive 1024-byte full packets and traffic across application-submission boundaries. | 自定义大数据量持续压力；无独立 CTS TD。Custom large-volume sustained stress; no standalone CTS TD. |
接收消费速度变化 快速与慢速应用接收、反复背压及就绪恢复。 Varying receive-consumption rates Fast and slow application reception, repeated backpressure and readiness recovery. | 自定义消费速度与背压压力；无独立 CTS TD。Custom consumption-rate and backpressure stress; no standalone CTS TD. |
包级发送准入 链路停顿期间新包准入、已开始报文的连续供数及正常编码停顿。 Packet-level transmit admission Admission of new packets during link stalls, continuous supply of admitted packets and normal encoding-related pauses. | 自定义发送准入与编码停顿测试；非独立 CTS 项。Custom transmit-admission and encoding-pause tests; not a standalone CTS item. |
吞吐与效率测量 有效载荷吞吐、链路有效传输占比、PIPE 有效数据占比与协议开销。 Throughput and efficiency measurements Payload throughput, active link-transfer utilization, PIPE data utilization and protocol overhead. | 自定义仿真性能评估；非 CTS 吞吐认证。Custom simulation-performance evaluation; not CTS throughput certification. |
窗口重开与包间开销 EOB、NumP 窗口、发送停顿及相邻数据包间隔的影响。 Window reopening and inter-packet overhead Effects of EOB, NumP windows, transmit stalls and spacing between consecutive data packets. | 自定义窗口 / 包间开销分析；无独立 CTS TD。Custom window / inter-packet overhead analysis; no standalone CTS TD. |
连续发送优化的功能保护 连续传输与预准备场景下的数据一致性，以及取消、重试和 Recovery 边界。 Functional checks for continuous-transmit optimization Data integrity during continuous and advance-preparation scenarios, including cancellation, retry and Recovery boundaries. | 自定义连续发送与取消边界回归；无独立 CTS TD。Custom continuous-transmit and cancellation-boundary regression; no standalone CTS TD. |
本清单仅列出性能评估项目，不给出产品吞吐保证，也不把仿真性能等同于实际 Host / 驱动性能。This document lists performance-evaluation topics only. It does not provide a product-throughput guarantee or equate simulation performance with actual Host / driver performance.
数据一致性与检查器Data integrity and checker validation
| 测试内容Tests performed | CTS／规范依据及覆盖边界CTS / specification reference and scope |
|---|---|
独立报文校验 HP CRC16、LCW / 命令 CRC5、DPP CRC32、字段及长度检查。 Independent packet validation HP CRC16, LCW / command CRC5, DPP CRC32, field and length checks. | 检查方法及工具自校验，不是新增 CTS 用例。Checking methods and tool validation, not additional CTS cases. |
逐字节数据一致性 发送到接收的数据、顺序、实际起始相位和应用交付内容比对。 Byte-level data consistency Comparison of transmitted and received bytes, ordering, actual start phase and application-delivered content. | 跨测试使用的数据比对方法，不是独立 CTS 用例。Data-comparison method shared across tests, not a standalone CTS case. |
序号、重传与 credit 记账 HP / DP 序号、DL、重传身份、双向 credit 及未完成事务跟踪。 Sequence, replay and credit accounting Tracking of HP / DP sequences, DL, replay identity, bidirectional credits and outstanding transactions. | CTS 与协议场景共用的记账检查，不重复计为 CTS 条目。Accounting checks shared by CTS-related and protocol scenarios; not counted as separate CTS items. |
丢失、重复与错误交付检测 额外报文、缺失报文、坏包交付、重复交付及传输结束后的残留行为。 Loss, duplication and incorrect-delivery detection Extra or missing packets, delivery of corrupted data, duplicate delivery and residual behavior after transfer completion. | 跨测试使用的结果检查方法，不是独立 CTS 用例。Outcome checks shared across tests, not a standalone CTS case. |
检查器正反例自测 故意改变数据、制造伪定界、删除或重复命令，以及构造错误重传响应，检查验证环境的检测能力。 Positive and negative checker self-tests Deliberately altered data, false framing, deleted or duplicated commands and incorrect replay responses to exercise the verification environment's detection capability. | 验证环境自测；不代表 Device IP 通过 CTS。Verification-environment self-tests; not evidence of Device IP CTS compliance. |
检查器自测用于验证测试环境本身，不单独构成 Device IP 的协议一致性通过结论。Checker self-tests validate the verification environment itself; they do not independently establish protocol compliance of the Device IP.
CTS 编号与规范版本CTS identifiers and reference editions
以下为本清单使用的正式规范版本。条目名称为简述；正式定义及完整步骤以对应规范为准。These are the reference editions used in this inventory. Topic labels are abbreviated; the cited specifications define the official tests and complete procedures.
LINK-CTS
USB 3.2 Link Layer Test Specification · Revision 1.1 · 2024-03-03
下列 TD 关联到已执行的场景子集或扩展。接口事件、缩短观察时间及附加压力不得解释为完整线上 CTS。The TDs below relate to performed scenario subsets or extensions. Interface events, shortened observation periods and added stress do not establish complete on-wire CTS execution.
| 正式编号Official identifier | 对应主题（简述）Related topic (abbreviated) |
|---|---|
| Link CTS · TD 7.1 | 启动与能力协商Bring-up / negotiation |
| Link CTS · TD 7.1.3 | 普通 LFPS 对端回退Ordinary-LFPS fallback |
| Link CTS · TD 7.1.5 | 有限 LFPS 后的回退Finite-LFPS fallback |
| Link CTS · TD 7.2 | 链路命令定界容错Command-framing faults |
| Link CTS · TD 7.3 | 命令副本 CRC5Command-copy CRC5 |
| Link CTS · TD 7.4 | 命令副本一致性Command-copy consistency |
| Link CTS · TD 7.5 | HP 定界容错HP-framing faults |
| Link CTS · TD 7.7 | 接收 HP 重试HP receive retry |
| Link CTS · TD 7.8 | 发送 HP 重试HP transmit retry |
| Link CTS · TD 7.11 | HP 未确认超时HP acknowledgement timeout |
| Link CTS · TD 7.13 | 错误 HP 序号HP sequence faults |
| Link CTS · TD 7.15 | 错误 credit 序号Credit sequence faults |
| Link CTS · TD 7.23 | U1 低功耗事务U1 power transaction |
| Link CTS · TD 7.24 | U2 低功耗事务U2 power transaction |
| Link CTS · TD 7.25 | U3 低功耗事务U3 power transaction |
| Link CTS · TD 7.26 | Recovery 返回 U0Recovery return to U0 |
| Link CTS · TD 7.28 | U0 下的 Hot ResetHot Reset from U0 |
| Link CTS · TD 7.30 | 连续三个坏 HP 后恢复Recovery after three bad HPs |
| Link CTS · TD 7.42 | 报文起始字节相位Packet-start byte phase |
CV-CTS
USB Command Verifier Compliance Test Specification for the USB 3.2 Architecture · Version 1.22
采用 USB-IF 2025-08 分发包中的 1.22 版，分发包日期不代表规范修订日期。本清单仅将基础配置与枚举事务关联到下列条目，未运行完整 USB3CV 验证程序。Version 1.22 from the USB-IF August 2025 distribution; the distribution date is not the specification revision date. Only baseline configuration and enumeration transactions are related to the items below; a complete USB3CV program was not executed.
| 正式编号Official identifier | 相关子集Related subset |
|---|---|
| CV-CTS · TD 9.13 | SET_CONFIGURATION 基础事务Baseline SET_CONFIGURATION transaction |
| CV-CTS · TD 9.16 | 基础枚举过程Baseline enumeration flow |
BASE
Universal Serial Bus 3.2 Specification · Revision 1.1 · June 2022
"BASE §"表示协议正文的章节，不是 CTS 的 TD 编号。NRDY / ERDY、ACK Retry、DPH 数据序号、NumP、EOB 和控制传输等按正文派生测试；无法对应正式 TD 的组合压力与工具自测明确标为自定义。"BASE §" identifies a base-specification section, not a CTS TD. NRDY / ERDY, ACK Retry, DPH data sequence, NumP, EOB and control-transfer tests derive from the base specification. Combined stress and checker self-tests without a formal TD are identified as custom tests.
断言号与 TD 编号是两套标识。例如 7.2.4.1.12#4 为 Link CTS 所列断言；TD 7.8 才是测试描述编号。引用不表示断言或 TD 的全部适用条件均已覆盖。Assertion identifiers and TD identifiers are distinct. For example, 7.2.4.1.12#4 is an assertion listed in Link CTS, whereas TD 7.8 identifies a test description. A reference does not imply coverage of all applicable conditions.
适用边界Applicability and limitations
- 测试主题为累计已执行范围；不同条目可能来自集成仿真、接口单测或探索性压力场景。
- 场景矩阵为选定组合，不表示所有长度、相位、速率、端点、错误时刻与随机种子的全交叉覆盖。
- 业务覆盖重点为 EP0 与 EP1；不声明已完成所有端点、Streams 或全部 Chapter 9 功能。
- Link CTS 派生用例及自定义压力测试不等同于完整官方 CTS 程序，也不构成 USB-IF 认证。
- 本清单不包含完整电气层测试、真实 Host / 操作系统兼容性矩阵或长期物理误码测试。
- 具体交付版本的验收结果，应以该版本对应的正式验证结论为准。
- The topics represent cumulative tests performed. Individual items may use integrated simulation, interface-level testing or exploratory stress scenarios.
- Scenario matrices cover selected combinations, not the full cross-product of lengths, phases, rates, endpoints, fault timing and random seeds.
- Traffic coverage focuses on EP0 and EP1. Coverage of every endpoint, Streams or all Chapter 9 functions is not claimed.
- Link CTS-derived cases and custom stress tests are not equivalent to the complete official CTS procedures and do not constitute USB-IF certification.
- This document does not include complete electrical testing, a real-Host / operating-system compatibility matrix or long-duration physical bit-error testing.
- Acceptance of a specific delivered revision should be based on the formal verification results for that revision.
术语Terminology
| 缩写Term | 说明Meaning |
|---|---|
| HP / TP | 头包 / 事务包Header Packet / Transaction Packet |
| DPH / DPP | 数据包头 / 数据包载荷Data Packet Header / Data Packet Payload |
| LCW / CRC | 链路控制字 / 循环冗余校验Link Control Word / Cyclic Redundancy Check |
| DL / EOB / ZLP | Delayed 标志 / 突发结束 / 零长度包Delayed flag / End of Burst / Zero-Length Packet |
| NRDY / ERDY | 未就绪 / 端点就绪Not Ready / Endpoint Ready |
| LTSSM / U0 | 链路训练与状态管理 / 正常链路工作状态Link Training and Status State Machine / Normal operational link state |
| LFPS / PIPE | 低频周期信号 / PHY 数字接口Low Frequency Periodic Signaling / PHY digital interface |
| CTS / BER | 一致性测试规范 / 误码率Compliance Test Specification / Bit Error Rate |