USB4™ Time Synchronization

Compliance Test Specification

Date: December 2022

Revision: 1.6
Copyright © 2022, USB Implementers Forum, Inc.

All rights reserved

THIS SPECIFICATION IS PROVIDED TO YOU “AS IS” WITH NO WARRANTIES WHATSOEVER,

INCLUDING ANY WARRANTY OF MERCHANTABILITY, NON-INFRINGEMENT, OR FITNESS FOR
ANY PARTICULAR PURPOSE. THE AUTHORS OF THIS SPECIFICATION DISCLAIM ALL LIABILITY,
INCLUDING LIABILITY FOR INFRINGEMENT OF ANY PROPRIETARY RIGHTS, RELATING TO USE
OR IMPLEMENTATION OF INFORMATION IN THIS SPECIFICATION. THE PROVISION OF THIS
SPECIFICATION TO YOU DOES NOT PROVIDE YOU WITH ANY LICENSE, EXPRESS OR IMPLIED,
BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS.

USB Type-C™, USB-C™, USB 2.0 Type-C™, and USB4™ are trademarks of the Universal Serial Bus
Implementers Forum (USB-IF). Thunderbolt™ is a trademark of Intel Corporation. All product names are
trademarks, registered trademarks, or service marks of their respective owners.

2
Revision History:

Revision Issue Date Comments

1.0 September 2020 First Release.

References the USB4 Specification, Version 1.0 with Errata
and ECN through May 4, 2020.

1.1 January 2021 References the USB4 Specification, Version 1.0 with Errata
and ECN through October 15, 2020.

1.2 June 2021 With corrections and clarifications.

References the USB4 Specification, Version 1.0 with Errata
and ECN through October 15, 2020.

1.3 October 2021 With corrections and clarifications.

References the USB4 Specification, Version 1.0 with Errata
and ECN through May 19, 2021.

1.4 December 2021 With corrections and clarifications.

References the USB4 Specification, Version 1.0 with Errata
and ECN through May 19, 2021.

1.5 March 2022 With corrections and clarifications.

References the USB4 Specification, Version 1.0 with Errata
and ECN through May 19, 2021.

1.6 December 2022 With corrections and clarifications.

References the USB4 Specification, Version 1.0 with Errata
and ECN through May 19, 2021 and includes additional
ECN through October 2022.

3
Contents
Introduction ...................................................................................................................................................................7
Terminology ..................................................................................................................................................................8
Assertions ......................................................................................................................................................................9
Chapter 4 ............................................................................................................................................................. 10
Chapter 7 ............................................................................................................................................................. 11
Chapter 8 ............................................................................................................................................................. 20
Test Requirements ....................................................................................................................................................... 21
Testing Approach .................................................................................................................................................... 21
Hardware ................................................................................................................................................................. 21
Measurement Methods ................................................................................................................................................ 22
Direct Time Measurement Method ......................................................................................................................... 22
Standalone Time Stream ..................................................................................................................................... 22
Comparative Time Measurement ........................................................................................................................ 23
Time Measurement Equipment ........................................................................................................................... 24
Indirect Measurement Method (SW) ....................................................................................................................... 25
Testing Subroutines ..................................................................................................................................................... 26
USB4 Link Configuration ....................................................................................................................................... 26
Link Configuration #1 Dual-Lane Link .............................................................................................................. 26
Link Configuration #2 Two Single Lane Links .................................................................................................. 26
Direct Time Measurement ....................................................................................................................................... 26
Time Calculation #1 System Time Consistency (Parameter N) .......................................................................... 26
Comparative Time Measurement ............................................................................................................................ 28
Time Calculation #2 System Time Diff (Parameter N) ...................................................................................... 28
Protocol Validation ................................................................................................................................................. 29
Protocol Check #1: Bi-Directional ...................................................................................................................... 29
Protocol Check #2: Bi-Directional ...................................................................................................................... 30
Protocol Check #3: Uni-Directional ................................................................................................................... 31
Protocol Check #4: Uni-Directional ................................................................................................................... 32
Protocol Check #5: Inter-Domain Timestamp Packet......................................................................................... 33
Statistics Functions.................................................................................................................................................. 34
Stat Sub #1 LocalTime Consistency ................................................................................................................... 34
Stat Sub #2 Time Offset ...................................................................................................................................... 35
Stat Sub #3 Frequency Offset ............................................................................................................................. 36
Stat Sub #4 Correlation between Frequency and Time Offsets .......................................................................... 37
Stat Sub #5 Propagation Delay ........................................................................................................................... 38

4
 Stat Sub #6 Computation Timestamp ................................................................................................................. 39
Stat Sub #7 Inter-Domain Computation Timestamp ........................................................................................... 40
Stat Sub #8 Inter-Domain Time Offset ............................................................................................................... 41
Stat Sub #9 Inter-Domain Frequency Offset ....................................................................................................... 42
Stat Sub #10 Correlation between Inter-Domain Frequency and Inter-Domain Time Offsets ........................... 43
Stat Sub #11 Port Statistics for Bi-Directional DFP ........................................................................................... 44
Stat Sub #12 Port Statistics for Bi-Directional UFP ........................................................................................... 45
Stat Sub #13 Port Statistics for Uni-Directional DFP ......................................................................................... 46
Stat Sub #14 Port Statistics for Uni-Directional UFP ......................................................................................... 47
Stat Sub #15 Port Statistics for Inter-Domain Timestamp Packets ..................................................................... 48
Time Posting Functions ........................................................................................................................................... 49
Time Posting #1: Immediate Posting – 15 days .................................................................................................. 49
Time Posting #2: Immediate Posting – 1 hour .................................................................................................... 50
Time Posting #3: Future Posting – 15 days ........................................................................................................ 51
Time Posting #4: Future Posting – 1 hour .......................................................................................................... 52
Time Posting #5: Immediate Time Posting Upon Configuration ........................................................................ 53
Test Setups................................................................................................................................................................... 54
Single-Port Host ...................................................................................................................................................... 54
Single Domain (SD)............................................................................................................................................ 54
Inter-Domain (ID) ............................................................................................................................................... 54
Multi-Port Host ....................................................................................................................................................... 56
Single Domain (SD)............................................................................................................................................ 56
Inter-Domain (ID) ............................................................................................................................................... 56
Hub .......................................................................................................................................................................... 58
Single Domain (SD)............................................................................................................................................ 58
Inter-Domain (ID) ............................................................................................................................................... 60
Peripheral Device .................................................................................................................................................... 62
Single Domain (SD)............................................................................................................................................ 62
Inter-Domain (ID) ............................................................................................................................................... 63
USB4 Test Descriptions .............................................................................................................................................. 64
Single-Port Host ...................................................................................................................................................... 64
Intra-Domain....................................................................................................................................................... 64
Inter-Domain....................................................................................................................................................... 70
Multi-Port Host ....................................................................................................................................................... 74
Intra-Domain....................................................................................................................................................... 74
Inter-Domain....................................................................................................................................................... 80
Hub .......................................................................................................................................................................... 81

5
 Intra-Domain....................................................................................................................................................... 81
Inter-Domain....................................................................................................................................................... 95
Peripheral Device .................................................................................................................................................... 98
Intra-Domain....................................................................................................................................................... 98
Inter-Domain..................................................................................................................................................... 106
TBT3-Compatibility Test Descriptions ..................................................................................................................... 107
Hub ........................................................................................................................................................................ 108
Intra-Domain..................................................................................................................................................... 108
Inter-Domain..................................................................................................................................................... 111

6
Introduction
The following tests check that a Router is compliant with Chapter 7 of the USB4 Base Specification.
System compliance purposes are:
• Test TMU standalone functionality:
o Statistics
o Time sync handshake
o Time accuracy
• Check compliance of time sensitive protocols: ITP, PTM and DisplayPort over challenging setups.

7
Terminology

The following table describes the terms used in this document.

Compliance Device A KG USB4 Device that is capable of performing Transport Layer Packet loopback.

DFP Downstream Facing Port

Exerciser The compliance test tool (hardware and software) that implements USB4 Port
functionality and the behavior required for compliance testing.

IOP Interop Testing. See USB4™ Interop Test Specification.

KG USB4 Device “Known Good” USB4 Device. A USB4 Device that is known to be compliant with the
USB4 Specification.

KG USB4 Host “Known Good” USB4 Host. A USB4 Host that is known to be compliant with the USB4
Specification.

KG TBT3 Device A Certified Thunderbolt 3 Device.

KG TBT3 Host A Certified Thunderbolt 3 Host.

PUT Port Under Test. The USB4 Port on a UUT that is the test point for compliance testing.

UFP Upstream Facing Port

USB4 CV USB4 Command Verifier software. The software that runs compliance tests and
analyzes the results.

USB4 Product Refers to a USB4 Host, USB4 Hub, and/or USB4 Peripheral Device. Includes silicon
and end product.

UUT Unit Under Test. The Router Assembly that is being tested for compliance.

VIF Vendor Information File. File provided by UUT vendor that provides information about
the characteristics and capabilities of the UUT.

8
Assertions
Compliance criteria are provided as a list of assertions that describe specific characteristics or behaviors that must be
met. Each assertion provides a reference to the USB4 specification or other documents from which the assertion
was derived. In addition, each assertion provides a reference to the specific test description(s) where the assertion is
tested.
Each test assertion is formatted as follows:

Assertion # Test # Assertion Description

Assertion#: Unique identifier for each spec requirement. The identifier is in the form
USB4_SPEC_SECTION_NUMBER#X, where X is a unique integer for a requirement in that section.
Assertion Description: Specific requirement from the specification
Test #: A label for a specific test description in this specification that tests this requirement. Test # can have one of
the following values:

NT This item is not explicitly tested in a test description. Items can be labeled NT for several reasons –
including items that are not testable, not important to test for interoperability, or are indirectly tested
by other operations performed by the compliance test.

X.X This item is covered by the test described in test description X.X in this specification.

IOP This assertion is verified by the USB4 Interoperability Test Suite.

Test descriptions provide a high level overview of the tests that are performed to check the compliance criteria. The
descriptions are provided with enough detail so that a reader can understand what the test does. The descriptions do
not describe the actual step-by-step procedure to perform the test.

9
Chapter 4
The following Table presents the USB4 Specification Chapter 4 asserts tested in this CTS.

Assertion # Test Assertion Description

4.2.1.6.3 Objections

A USB4 Port shall assert an objection to enter CL2 state if: Entry to CL2
4.2.1.6.3#1 NT
state would delay a pending Time Sync handshake.

4.2.1.6.3#2 NT This objection shall be asserted until the Time Sync handshake is complete.

A USB4 Port shall assert an objection to enter CL1 state if: Entry to CL1
4.2.1.6.3#3 NT
state would delay a pending Time Sync handshake.

4.2.1.6.3#4 NT The objection shall be asserted until the Time Sync handshake is complete.

10
Chapter 7
The following Table presents the USB4 Specification Chapter 7 asserts.

Assertion # Test Assertion Description

7 Time Synchronization

A Router with one or more DFP shall support the USB4 Time
7#1 NT Synchronization Protocol described in this chapter.

A Router shall implement the TMU Router Configuration Capability and

7#2 TBD the TMU Adapter Configuration Capability.

A Router that does not support the Time Synchronization Protocol shall
set the Time Synchronization Protocol Not Supported bit in the TMU
7#3 TBD Router Configuration Capability to 1b.

A Host Router that does not support Inter-Domain Time Synchronization

7#4 TBD shall set the IDNS bit in the TMU Router Configuration Capability to 1b.

7.1 Time Synchronization Architecture

7.1.1 Synchronization Hierarchy

7.1.1.1 Intra-Domain Hierarchy

7.1.1.2 Inter-Domain Hierarchy

7.1.2 Time Sync Parameters

7.1.2.1 Local Time

A Router shall provide a free-running clock for use in capturing the time
7.1.2.1#1 NT stamps needed for the Time Synchronization Protocol.

7.1.2.1#2 NT The Local Clock shall run at a frequency of 125 MHz or greater with an
accuracy of +/− 100ppm relative to the nominal Local Clock frequency

7.1.2.1#3 NT The Local Clock shall not be spread-spectrum.

7.1.2.1#4 A Router shall use an 80-bit Local Time counter with the format shown in
Stat Sub #1 Figure 7-2 to track Local Time.

7.1.2.1#5 Stat Sub #1 The Local Time counter shall be incremented up with the Local Clock.

7.1.2.2 Time Offset

The TimeOffsetFromHR register shall have the format shown in Figure 7-

7.1.2.2#1 NT 3.

The TimeOffsetFromHR register shall be updated at the conclusion of

7.1.2.2#2 Stat Sub #2 every Time Sync Handshake.

11
 7.1.2.3 Frequency Offset

7.1.2.3#1 NT The frequency offset shall be computed according to Equation 7-2.

The FreqOffsetFromHR register shall be updated at the conclusion of

7.1.2.3#2 Stat Sub #3 every Time Sync Handshake.

7.2 Time Stamp Measurement

USB4 Port shall generate a time stamp whenever it either sends or

7.2#1 Protocol Check #3 receives a Time Sync Notification Ordered Set (TSNOS).

7.2#2 A USB4 Port shall use the value in the Local Time counter to capture time
NT stamps.

7.2#3 NT A time stamp shall be taken at the Time Stamp Point of the First TSNOS.

7.2#4 If one or more back-to-back TSNOS are received immediately after the
Protocol Check #3 first TSNOS, they shall be ignored.

7.2#5 The same transmit reference pLane shall be used for all transmitted
TSNOS and the same receive reference pLane shall be used for all
NT received TSNOS.

7.2#6 The time stamp measurement shall have a resolution of at least 8 ns (i.e.
Protocol Check #3 the period of the Local Clock).

7.2#7 The time stamp in a Time Sync Packet shall have the format shown in
NT Figure 7-2.

7.2.1 Asymmetry Corrections

Time Calculation Time stamps shall be corrected for asymmetry between transmit and
7.2.1#1 #2 receive paths.

7.2.1#2 An Upstream Facing Port (UFP) shall correct for asymmetry by

performing the following computations: t1 = Delay Request Sent Time
Stamp + TxTimeToWire; t4 = Delay Response Received Time Stamp –
RxTimeToWire; where, TxTimeToWire is the value in the
TxTimeToWire field of the TMU_ADP_CS_1 register of the UFP and
Time Calculation RxTimeToWire is the value in the RxTimeToWire field of the
#2 TMU_ADP_CS_2 register of the UFP.

7.2.1#3 A Downstream Facing Port (DFP) shall correct for asymmetry by

performing the following computations: t2 = Delay Request Received
Time Stamp – RxTimeToWire; t3 = Delay Response Sent Time Stamp +
TxTimeToWire; where, TxTimeToWire is the value in the
TxTimeToWire field of the TMU_ADP_CS_1 register of the DFP and
Time Calculation RxTimeToWire is the value in the RxTimeToWire field of the
#2 TMU_ADP_CS_2 register of the DFP.

12
 7.2.1#4 The time duration between when a USB4 Port generates a time stamp and
Time Calculation when it transmits first bit of a TSNOS on the wire shall be equal to the
#2 value in the TxTimeToWire field of the TMU_ADP_CS_1 register.

7.2.1#5 The time duration between when a USB4 Port receives the first bit of a
Time Calculation TSNOS on the wire and when it generates a time stamp shall be equal to
#2 the value in the RxTimeToWire field of the TMU_ADP_CS_2 register.

7.3 Time Sync Protocol

7.3.1 Time Sync Handshake

A Router shall support Bi-Directional Time Sync Handshakes in HiFi

7.3.1#1 Protocol Check #1 Mode.

7.3.1#2 NT A Router shall support Uni-Directional Time Sync Handshakes in HiFi

Mode and LowRes Mode.

7.3.1#3 NT When the USB4 Ports are connected by a Single-Lane Link, a Time Sync
Handshake shall occur over that Link.

7.3.1#4 NT When the USB4 Ports are connected by a Dual-Lane Link, the Delay
Request and Delay Response Ordered Sets in the Time Sync Handshake
shall be sent on both the Lane 0 and Lane 1.

7.3.1#5 NT The Follow-Up Packet shall be sent using both Lanes (i.e. alternating
bytes across Lanes).

7.3.1#6 The timestamp shall be taken when the first Ordered Set from the Link
NT Partner is received.

7.3.1#7 A Receiver shall ignore a TSNOS that arrives back-to-back after another
NT TSNOS.

7.3.1.1 Bi-Directional Time Sync Handshake

7.3.1.1#1 Protocol Check #1 A DFP shall not initiate a Bi-Directional Time Sync Handshake

7.3.1.1#2 Protocol Check #1 A UFP shall send a Delay Request to the DFP at the interval specified in
the TSPacketInterval field in the TMU_RTR_CS_3 register in Router
Configuration space.

7.3.1.1#3 Protocol Check #1 A DFP shall transmit a Delay Response Packet within 1 µs of receiving a
Delay Request Packet.

7.3.1.1#4 A DFP shall transmit a Follow-Up Packet within SendTimeout of

Protocol Check #1 transmitting the associated Delay Response Packet.

7.3.1.1#5 A UFP shall generate time stamp t1 upon transmission of a Delay Request
Stat Sub #6 and shall generate time stamp t4 upon reception of a Delay Response.

7.3.1.1#6 A DFP shall generate time stamp t2 upon receipt of a Delay Request and
Protocol Check #2 shall generate time stamp t3 upon transmission of a Delay Response.

13
 7.3.1.1#7 If an error occurs during the transmission or reception of a Time Sync
Packet, the entire Time Sync Handshake shall be voided (i.e. neither time
NT stamps nor values from the Follow-Up Packet shall be used).

7.3.1.1#8 When using Bi-Directional Time Sync Handshake, a DFP shall do the
NT following upon receiving a Delay Request: 1. Take the t2 timestamp

7.3.1.1#9 NT When using Bi-Directional Time Sync Handshake, a DFP shall do the
following upon receiving a Delay Request: 2. Send a Delay Response.

7.3.1.1#10 NT Delay Response shall be sent within RespTimeout time or receiving the
Delay Request

7.3.1.1#11 NT The DFP shall take the t3 timestamp upon Delay Response transmission

7.3.1.1#12 NT When using Bi-Directional Time Sync Handshake, a DFP shall do the
following upon receiving a Delay Request: 3. Compute the updated
TimeOffsetFromHR parameter according to Equation 7-6 using the t3
timestamp from Step 2b

NT When using Bi-Directional Time Sync Handshake, a DFP shall do the

following upon receiving a Delay Request: 4. Send Follow-Up Packet
7.3.1.1#13 with the TimeOffsetFromHR calculated in Step 3

7.3.1.2 Uni-Directional Time Sync Handshake

Protocol Check #3 When using Uni-Directional Time Sync Handshake, only the DFP shall
7.3.1.2#1 initiate a Time Sync Handshake

7.3.1.2#2 Protocol Check #3 A DFP shall send a Delay Response to the UFP at the interval specified in
the TSPacketInterval field in the TMU_RTR_CS_3 register in Router
Configuration space.

7.3.1.2#3 Protocol Check #3 A DFP shall transmit a Follow-Up Packet within SendTimeout after
transmitting the associated Delay Response Packet

7.3.1.2#4 Protocol Check #3 Uni-Directional Time Sync Handshake shall be used when the following
conditions are true: Both Link Partners support Uni-Directional Time
Sync Handshake; Both Link Partners have the EnableUniDirectionalMode
field in the TMU_ADP_CS_3 register in Adapter Configuration Space set
to 1b.

7.3.2 Inter-Domain Time Sync

A USB4 Port shall perform Time Sync Handshakes as described in

Section 7.3.1 across the Inter-Domain Link when either the IDTR bit or
7.3.2#1 Protocol Check #1 IDTI bit is set to 1b.

7.3.2#2 Protocol Check #1 After completing a Time Sync Handshake across an Inter-Domain Link,
the IDTI Port shall calculate the following: The Inter-Domain time stamp
(see Section 7.4.2.1); The Inter-Domain frequency offset (see Section
7.4.2.2); The Inter-Domain time offset (see Section 7.4.2.3).

14
 7.3.2#3 Protocol Check #1 After calculating the Inter-Domain time offset, Inter-Domain frequency
offset and Inter-Domain time stamp, the IDTI Port shall update the
InterDomainTimeStamp, FreqOffsetFromInterDomainHR and
TimeOffsetFromInterDomainHR fields in Router Configuration Space.

7.3.2#4 Protocol Check #5 If the IDTI Port is part of a Device Router, it shall prepare an Inter-
Domain Time Stamp Packet as described in Section 7.3.3.3.

7.3.2#5 Protocol Check #5 If the TSInterDomainInterval field in Router Configuration Space is 0, the
IDTI Port shall send the Host Router an Inter-Domain Time Stamp Packet
after each Inter-Domain Time Sync Handshake.

7.3.2#6 Protocol Check #5 If the TSInterDomainInterval field in Router Configuration Space is not 0,
the IDTI Port shall send the Host Router an Inter-Domain Time Stamp
Packet at time intervals equal to (TSInterDomainInterval + 1) *
TSPacketInterval number of microseconds.

7.3.2#7 NT When a Host Router receives an Inter-Domain Time Stamp Packet: If the
IDE bit in the TMU_RTR_CS_0 register of the Host Router’s TMU
Router Configuration Capability is set to 1b, the Host Router shall update
its TimeOffsetFromInterDomainHR and FreqOffsetFromInterDomainHR
registers using the time offset and frequency offset respectively contained
in the Inter-Domain Time Stamp Packet.

7.3.2#8 NT When a Host Router receives an Inter-Domain Time Stamp Packet: If the
IDE bit in the Host Router is set to 0b, the Host Router shall drop the
Inter-Domain Time Stamp Packet and shall not update its
TimeOffsetFromInterDomainHR or FreqOffsetFromInterDomainHR
registers

7.3.3 Packet Formats

7.3.3.1 Time Sync Notification Ordered Set Format

Both a Delay Request and a Delay Response shall consist of the Time
7.3.3.1#1 Protocol Check #1 Sync Notification Ordered Set (TSNOS) defined in Section 4.4.7.

7.3.3.2 Follow-Up Packet Format

7.3.3.2#1 Protocol Check #2 A Follow-Up Packet shall have the format shown in Figure 7-13.

7.3.3.2#2 A Follow-Up Packet shall have the PDF field set to 1, the HopID set to 3,
Protocol Check #2 and the Length set to 60.

7.3.3.2#3 Protocol Check #2 The payload shall contain the fields in Table 7-3.

7.3.3.2#4 For Bi-Directional Time Sync Handshakes: The time stamp shall include
Time Calculation the asymmetry corrections performed at the DFP as specified in Section
#2 7.2.1.

7.3.3.2#5 For Bi-Directional Time Sync Handshakes: The RequestReceiptTS field

Protocol Check #2 shall have the format shown in Figure 7-2

15
 7.3.3.2#6 For Uni-Directional Time Sync Handshakes: The RequestReceiptTS field
Protocol Check #4 shall contain the same value as the ResponseOriginTS field.

7.3.3.2#7 Time Calculation The time stamp shall include the asymmetry corrections performed at the
#2 DFP as specified in Section 7.2.1.

7.3.3.2#8 Protocol Check #2 The ResponseOriginTS field shall have the format shown in Figure 7-2.

7.3.3.2#9 Protocol Check #2 The TimeOffsetFromHR field shall have the format shown in Figure 7-3.

7.3.3.2#10 Protocol Check #2 The FreqOffsetFromHR shall have the format shown in Figure 7-4.

7.3.3.2#11 Protocol Check #2 Bits 31:16 of DW8 are reserved and shall be set to 0.

7.3.3.2#12 Protocol Check #2 For a Host Router: If IDE bit is set to 0b, then the IDTimeStamp field
shall be set to 0.

7.3.3.2#13 Protocol Check #2 For a Device Router: The IDTimeStamp field shall contain the
IDTimeStamp value from the last Follow-Up Packet that the IDTI Port on
the Router Received.

7.3.3.2#14 Protocol Check #2 For a Host Router: If IDE bit is set to 0b, then the
FreqOffsetFromInterDomainHR field shall be set to 0.

7.3.3.2#15 Protocol Check #2 For a Device Router: The FreqOffsetFromInterDomainHR field shall
contain the FreqOffsetFromInterDomainHR value in the last Follow-Up
Packet that the IDTI Port on the Router Received.

7.3.3.2#16 The CRC32 computation shall be based on the following specification:

Width: 32; Poly: 1EDC 6F41h; Init: FFFF FFFFh; RefIn: True; RefOut:
NT True; XorOut: FFFF FFFFh;

7.3.3.3 Inter-Domain Time Stamp Packet

An Inter-Domain Time Stamp Packet shall have the format shown in

7.3.3.3#1 Protocol Check #5 Figure 7-14.

7.3.3.3#2 Protocol Check #5 An Inter-Domain Time Stamp Packet shall have the PDF set to 2, the
HopID set to 3, and the Length set to 28.

7.3.3.3#3 Protocol Check #5 The payload shall contain the fields in Table 7-4.

7.3.3.3#4 Protocol Check #5 The IDTimestamp field shall have the format shown in Figure 7-2.

7.3.3.3#5 Protocol Check #5 The TimeOffsetFromInterDomainHR field shall have the format shown in
Figure 7-3.

7.3.3.3#6 Protocol Check #5 The FreqOffsetFromInterDomainHR field shall have the format shown in
Figure 7-4.

7.3.3.3#7 The CRC32 computation shall be based on the following specification:

Width: 32; Poly: 1EDC 6F41h; Init: FFFF FFFFh; RefIn: True; RefOut:
NT True; XorOut: FFFF FFFFh;

16
 7.4 Time Computations

A Router shall be able to compute the Host Router Time at any instant in
7.4#1 NT time.

7.4.1 Intra-Domain Equations

A Router shall use the following series of computations to deduce the

current Host Router Time within a single Domain: The UFP uses Equation
7.4.1#1 Stat Sub #3 7-1 to compute the frequency ratio between itself and its DFP.

7.4.1#2 A Router shall use the following series of computations to deduce the
current Host Router Time within a single Domain: The UFP uses Equation
7-2 to compute the frequency offset. The UFP uses the frequency ratio
Stat Sub #3 obtained in Step 1 as input to the computation.

7.4.1#3 Stat Sub #3 A Router shall use the following series of computations to deduce the
current Host Router Time within a single Domain: The UFP uses Equation
7-3 to compute the frequency ratio between itself and the Host Router.
The UFP uses the FreqOffsetFromHR value in the last Follow-Up Packet
received from the DFP as input to the computation.

7.4.1#4 Stat Sub #3 A Router shall use the following series of computations to deduce the
current Host Router Time within a single Domain: The UFP uses Equation
7-4 to compute the frequency offset between itself and the Host Router.
The UFP uses the frequency ratio computed in Step 3 as input to the
computation.

7.4.1#5 A Router shall use the following series of computations to deduce the
current Host Router Time within a single Domain: The UFP uses Equation
7-5 to compute the propagation delay of the cable between the UFP and
Stat Sub #5 the DFP.

7.4.1#6 A Router shall use the following series of computations to deduce the
current Host Router Time within a single Domain: The Link Partner (i.e.
the DFP upstream of the UFP) uses Equation 7-6 to compute the most
updated time offset from the Domain Host Router. The Link Partner uses
Stat Sub #2 the most recent result from Equation 7-9, as input to the computation.

7.4.1#7 A Router shall use the following series of computations to deduce the
current Host Router Time within a single Domain: The UFP uses Equation
7-7 (Bi-Directional Time Sync Handshakes) or Equation 7-8 (Uni-
Directional Time Sync Handshakes) to compute the time offset from its
Stat Sub #2 DFP.

7.4.1#8 A Router shall use the following series of computations to deduce the
current Host Router Time within a single Domain: The UFP uses Equation
7-9 to compute the time offset from the Host Router. The UFP uses the
time offset from Equation 7-7 or Equation 7-8, and the value in the last
Stat Sub #4 received Follow-Up Packet as input to the computation.

17
 7.4.1#9 A Router shall use the following series of computations to deduce the
current Host Router Time within a single Domain: The UFP uses Equation
7-10 to compute the current time offset from the Host Router. The UFP
Time Calculation uses the time offset computed in Equation 7-9 and the frequency offset
#1 computed in Equation 7-3 as input to the computation.

7.4.2 Inter-Domain Equations

7.4.2.1 Inter-Domain Time Stamp Computation

7.4.2.1#1 NT Equation 7-11 is used to compute an Inter-Domain time stamp.

7.4.2.2 Inter-Domain Frequency Offset Computation

The frequency ratio between the Host Router in the Domain with the IDTI
7.4.2.2#1 NT Port and the Inter-Domain Time Source is computed using Equation 7-12.

7.4.2.3 Inter-Domain Time Offset Computation

The time offset of the IDTR Port that is sent in the Follow-Up Packet at
the end of an Inter-Domain Time Sync Handshake is computed using
7.4.2.3#1 Stat Sub #7 Equation 7-14

7.4.2.3#2 The time offset between the IDTI Port and the Inter-Domain Time Source
Stat Sub #9 is computed using Equation 7-15.

7.4.2.3#3 The time offset between the Host Router of the Domain with the IDTI Port
Stat Sub #9 and the Inter-Domain Time Source is computed using Equation 7-16.

7.4.2.4 Inter-Domain Host Router Time Computation

7.4.3 Filtering

7.5 Time Synchronization Accuracy Requirements

A Router shall reach the required time synchronization accuracy within

7.5#1 NT tConvergeTime after Time Sync Handshakes are enabled.

If Time Sync Handshakes are paused, a UFP shall reach the required time
synchronization accuracy within tConvergeTime after receiving a Delay
7.5#2 TBD Response Packet.

7.5.1 Paired Measurement

For Bi-Directional Time Sync Handshake, the Static Offset between two
7.5.1#1 NT Routers connected to one another shall not add more than 8 ns per Link.

In HiFi Mode, the Dynamic Noise between two Routers connected to one
7.5.1#2 NT another shall not add more than tHiAccuracy.

In LowRes Mode, the Dynamic Noise between two Routers connected to

7.5.1#3 NT one another shall not add more than tLowAccuracy.

18
 7.5.2 Standalone Measurement

NT In HiFi Mode, the noise between measurement points and the ideal line
7.5.2#1 shall not be more than tHiAccuracy.

NT In LowRes Mode, the noise between measurement points and the ideal
7.5.2#2 line shall not be more than tLowAccuracy.

7.5.2#3 NT In order to achieve the goal of 1 ns static noise, the budget for
TxTimeToWire uncertainty shall not be more than 6.4 ns dynamic noise
with no more than 6.4 ns static offset that changes after each power up.

7.5.2#4 NT RxTimeToWire shall not be more than 12.8 ns dynamic noise with no
more than 6.4 ns static offset that changes after each power up.

7.5.2#5 Dynamic uncertainty in TxTimeToWire and RxTimeToWire shall be

NT filtered out during calculations by IRR or other filtering.

7.5.3 Measuring Method

7.5.4 Accuracy Parameters

7.6 Software Configuration

7.6.1 Intra-Domain Time Synchronization Setup

A Router that is hot-plugged to a Domain shall only initiate the Time Sync
Handshake on its UFP when the following conditions are true: The
physical layer has established the Link between the hot-plugged Router
and the Domain; The TSPacketInterval field in the TMU_RTR_CS_3
7.6.1#1 NT register in Router Configuration space is greater than 0.

7.6.2 Inter-Domain Time Synchronization Setup

7.6.3 Post Time Mechanism

A Router shall update its local time when the Post Time is less than or
7.6.3#1 NT equal to the Nanoseconds field in the Host Router Time Register.

7.6.4 Time Disruption Bit

19
Chapter 8
The following Table presents the USB4 Specification Chapter 8 asserts tested in this CTS.

Assertion # Test Assertion Description

8.2.1.2 TMU Router Configuration Capability

A TMU Router Configuration Capability shall have the structure depicted

8.2.1.2#1
in Figure 8-3 and the fields defined in Table 8-4.

Any field that spans across multiple Doublewords (e.g. LocalTime Low,
LocalTime Middle, and LocalTime High) shall use the Register Locking
8.2.1.2#2
Mechanism defined in Section 8.2.1.2.1 and the Register Group Locking
Mechanism defined in Section 8.2.1.2.2.

8.2.1.2.1 Register Locking Mechanism

In order to keep consistent values in these fields, a Router shall update the
8.2.1.2.1#1 value in the entire field (i.e. Low, Middle, and High DWs) when the
Connection Manager reads the Low DW of the field.

A Router shall not change the value in the Middle and High DWs until the
8.2.1.2.1#2
next time the Low DW is read.

The Register Locking Mechanism shall be implemented for following

8.2.1.2.1#3 registers: LocalTime {Low, Middle, High}, TimeOffsetFromHR {Low,
Middle, High}, Inter-Domain Time Stamp {Low, Middle, High}

8.2.1.2.2 Register Group Locking Mechanism

The value of a locked register group shall change only when the Triggering
8.2.1.2.2#1
DW is accessed.

8.2.1.2.2#2 Table 8-5 lists the register groups that shall be locked

8.2.2.2 TMU Adapter Configuration Capability

A TMU Lane Adapter Configuration Capability shall have the structure

8.2.2.2#1
depicted in Figure 8-8 and shall contain the fields defined in Table 8-11.

For a USB4 Port with two enabled Adapters, the values in the TMU Lane
8.2.2.2#2
Adapter Configuration Capability of both Adapters shall be identical.

When a value in the TMU Lane Adapter Configuration Capability of one

8.2.2.2#3 Adapter is written to, the other Adapter in the USB4 Port shall update its
value to match.

The TMU Adapter shall set the EnableUniDirectionalMode bit to 0b when

8.2.2.2#4 TBD
its USB4 Port is disconnected.

20
Test Requirements
Testing Approach
The USB4 Time Synchronization Protocol is tested using the following methods:
• Indirect measurement by reading and analyzing statistics (TMU registers in Router and Adapter
Configuration Spaces)
• Direct measurement by letting KG USB4 Devices synchronize with the UUT and then extracting the
system time via Time Serial Interface from the KG USB4 Device
• Protocol testing with USB4 Protocol analyzer
• Functional compliance of time sensitive protocols: ITP, PTM and DisplayPort over different setups

Hardware
Testing TMU requires:
• KG USB4 Host
• KG USB4 Hub
• KG USB4 Device
• TMU CLK OUT Analyzer
• USB4 Link Analyzer
• USB4 CV SW

21
Measurement Methods
Direct Time Measurement Method
Standalone Time Stream
When applicable, time synchronization is measured via Time Serial Interface (TMU CLK OUT) of a KG USB4
Host, KG USB4 Hub or KG USB4 Device in the following manner:

UUT

USB4 Link

Time
KG USB4 Time Serial Interface
Measurement
Device
Equipment

The KG USB4 Device synchronizes to UUT and then extracts the computed Host Router time over Time Serial
interface, which in turn is fed to Serial Protocol Analyzer. After Host Router time is extracted, it is analyzed for
consistency.

22
Comparative Time Measurement

UUT

USB4 Link USB4 Link

Time
KG USB4 KG USB4 Time Serial Interface
A
Measurement
Device Device Equipment
B

23
Time Measurement Equipment
The TMU FPGA is used to capture the time stream on the Time Serial Interface. The FPGA is operated through
executable (outside the scope of this document).
The command format is:
1. To capture PA input in standalone mode
> TMU_FPGA.bat PA
2. To capture PA input in standalone mode
> TMU_FPGA.bat PB
3. To capture in comparative mode
> TMU_FPGA.bat TDIFF

The output will be in the file “dump.txt”

The file location shall be in folder "C:\Users\Public\Documents\TMU_FPGA\USB4_Compliance\"

The file format is list of timestamps in hexadecimal:

00000010001
00000050002
000000a0003
000000f0004
00000140005

The time format is as specified in Figure 7-2. Local Time Counter Format of the USB4 Specification and shall have
exactly 16 hexadecimal digits.

24
Indirect Measurement Method (SW)
This section describes the registers that participate in analyzing time sync using Indirect method.

\ Device Type Host Router Hub Endpoint

Variable

LocalTime ✔ ✔ ✔

TimeOffsetFromHR ✘ ✔ ✔

TimeOffsetFromDFP ✘ ✔ ✔

FreqOffsetFromHR ✘ ✔ ✔

FreqOffsetFromDFP ✘ ✔ ✔

Propagation Delay ✘ ✔ ✔

Computation Timestamp ✘ ✔ ✔

InterDomain Computation Timestamp ✔ ✔ ✔

TimeOffsetFromInterDomainHR ✔ ✔ ✔

FreqOffsetFromInterDomainHR ✔ ✔ ✔

\ Statistics RX TSNOS TX TSNOS RX Packet TX Packet

Counter Counter Counter Counter
Port Direction

Upstream Bidirectional ✔ ✔ ✔ ✘

Downstream Bidirectional ✔ ✔ ✘ ✔

Upstream Unidirectional ✔ ✘ ✔ ✘

Downstream Unidirectional ✘ ✔ ✘ ✔

Where:
✘ - Register is expected to remain 0
✔ - Register is expected to change

Reading and analyzing relevant registers in different setups gives basic insight into Time Sync functionality using
different setups. The exact function are described further.

25
Testing Subroutines
This section defines subroutines with the test steps that are repeated for multiple tests. The USB4 Test Descriptions
reference the subroutines defined in this section.

USB4 Link Configuration

Note: See the USB4 Connection Manager Guide for how to perform a DFP reset, initiate Lane Bonding, and
enumerate Routers.

Link Configuration #1 Dual-Lane Link

1. USB4 CV performs a Downstream Port Reset on the DFP of the Host Router
2. USB4 CV initiates Lane Bonding
3. USB4 CV enumerates all Routers in the topology
4. Execute Time Posting #5

Link Configuration #2 Two Single Lane Links

1. USB4 CV performs a Downstream Port Reset on the DFP of the Host Router
2. USB4 CV does not initiate Lane Bonding
3. USB4 CV enumerates all Routers in the topology
4. Execute Time Posting #5

Direct Time Measurement

The deviation noise from ideal line is expected to be less than 1 ns per hop in HiFi mode and less than 4 ns in
LowRes mode.
Time Calculation #1 System Time Consistency (Parameter N)
1. Parse Serial Time stream.
2. Capture each N-th Serial packet, extract system time.
3. Capture 32K samples of system time.
4. Create data regression on the time stream.
5. Measure system time deviation from average line.
6. Expected deviation is calculated by the following algorithm:
// TimeArr [0:L-1] is the array that contains all the values from the sample
// L is the length of the array

//Step#1: compute average step

AvStep=(TimeArr[L-1]-TimeArr[0])/(L-1);

//Step#2: build ideal array

IdealArr[0]=TimeArr[0];
for(i=1;i<L;i++) {
IdealArr[i]=IdealArr[i-1] + AvStep;
};

#Step#2: compute deviation from ideal

for(i=0;i<L;i++) {
Diff[i]=TimeArr[i]-IdealArr[i];
};

26
 //Step#3: find max and min of the Diff
TMin = min(Diff);
TMax = max(Diff);

//Step#4: compute absolute error

AbsError = Tmax – Tmin;

7. Verify that AbsError: (7.4.1#9)

a. In HiFi mode less than 1 ns per hop
b. In LowRes mode less than 4 ns per hop

Assertions checked:
• 7.4.1#9

27
Comparative Time Measurement
Time Calculation #2 System Time Diff (Parameter N)
1. Parse Serial Time stream from UUT A.
2. Parse Serial Time stream from UUT B.
3. Capture each N-th pair.
4. Capture 32K samples.
5. Calculate Time Diff according to the following method:

Time Diff = (TB-TA) – (TsB-TsA)

Where TsA and TsB are the timestamps of serial packets
6. The following method is used to calculate the average Time Diff:
//TimeDiff[0:L-1] is an array containing the samples
// L is the length of the array

for (i=0;i<L;i++) {
TimeSum = TimeSum + TimeDiff[i];
}
TimeAv = TimeSum/L;

7. Verify that TimeDiff doesn’t cross the expected amplitude: (7.2.1#1-#5, 7.3.3.2#4, 7.3.3.2#7)
a. In HiFi mode less than 2 ns per hop, TimePass = 2
b. In LowRes less than 10 ns per hop, TimePass = 10
The method:
for(i=0;i<L;i++) {
if (abs(TimeDiff[i] – TimeAV) > TimePass) {
error = 1;
}
if (abs(TimeDiff[i]) < 16 ns) {
error = 1;
}
}

Note: The TimeDiff value is represented as a 32-bit 2’s compliment signed integer.

Assertions checked:
• 7.2.1#1, 7.2.1#2, 7.2.1#3, 7.2.1#4, 7.2.1#5
• 7.3.3.2#4, 7.3.3.2#7

28
Protocol Validation
The steps in this section are performed by parsing a trace from the USB4 protocol analyzer.
Protocol Check #1: Bi-Directional
Verify that a Bi-Directional Time Sync Handshake is performed according to Figures 7-7 and 7-8 in USB4
specification:
1. Take sample of 250ms.
2. If the Link is Inter-Domain, then:
a. If IDTI bit in the Inter-Domain Time Initiator is not set and Bi-Directional mode is set, no
handshake should be initiated
3. UFP initiates handshake every TSPacketInterval (+/- 1%). (7.3.1.1.#2, 7.3.2#1)
4. DFP does not initiate any handshakes. (7.3.1.1.#1, 7.3.2#1)
5. DFP responds by TSNOS within RespTimeout. (7.3.1.1.#3, 7.3.2#1)
6. DFP sends Follow-Up Packet within FPTimeout after OS. (7.3.1.1.#4, 7.3.2#1)

Assertions checked:
• 7.3.1#1
• 7.3.1.1#1, 7.3.1.1#2, 7.3.1.1#3, 7.3.1.1#4
• 7.3.2#1, 7.3.2#2, 7.3.2#3
• 7.3.3.1#1

29
Protocol Check #2: Bi-Directional
Take sample of 250ms.
Check the contents of each Follow-Up Packet:
1. Verify that:
a. PDF field is set to 1. (7.3.3.2#2)
b. HopID is set to 3. (7.3.3.2#2)
c. Length is set to 60. (7.3.3.2#2)
2. Verify that T2 and T3 are consistently growing between every two consecutive packets by
TSPacketInterval. (7.3.1.1#6)
3. Verify that T2 and T3 variance is less than 32 ns. (7.3.1.1#6)
4. If a packet is sent by Hub Router on the downstream port, verify that:
a. TimeOffsetFromHR is consistently growing like in Stat Sub #2. (7.3.3.2#9)
b. FreqOffsetFromHR is constant like in Stat Sub #3. (7.3.3.2#10)
c. There is correlation between TimeOffsetFromHR and FreqOffsetFromHR same as in Stat Sub #4.
(TBD)
5. If a packet is sent by Inter-Domain Time Responder or any DFP in Inter-Domain Time Initiator’s Domain,
verify that the following fields are 0 when IDE bit is set to 0 in Host Router:
a. IDTimeStamp. (7.3.3.2#12)
b. TimeOffsetFromInterDomainHR. (TBD)
c. FreqOffsetFromInterDomainHR. (TBD)
d. FreqOffsetFromInterDomainHR. (7.3.3.2#14)
6. Otherwise (IDE bit is set to 1), verify that:
a. IDTimeStamp is constantly growing between every two consecutive packets. (7.3.3.2#13)
b. TimeOffsetFromInterDomain is consistently growing like in Stat Sub #8. (TBD)
c. FreqOffsetFromInterDomain is constant like in Stat Sub #9. (7.3.3.2#15)
d. There is correlation between TimeOffsetFromInterDomain and FreqOffsetFromInterDomain same
as in Stat Sub #10. (TBD)

Assertions checked:
• 7.3.1.1#6
• 7.3.3.2#1
• 7.3.3.2#2
• 7.3.3.2#3
• 7.3.3.2#5
• 7.3.3.2#8
• 7.3.3.2#9
• 7.3.3.2#10
• 7.3.3.2#11
• 7.3.3.2#12
• 7.3.3.2#13
• 7.3.3.2#14
• 7.3.3.2#15

30
Protocol Check #3: Uni-Directional
Verify that a Uni-Directional Time Sync Handshake is performed according to Figure 7-10 and 7-11 in the USB4
Specification:
1. Take sample of 250ms.
2. Verify that the DFP sends a TSNOS every TSPacketInterval (+/-1%). (7.3.1.2#2)
3. Verify that the DFP sends a Follow-Up Packet within SendTimeout time after sending the TSNOS.
(7.3.1.2#3)

Assertions checked:
• 7.2#1
• 7.2#4
• 7.2#6
• 7.3.1.2#1
• 7.3.1.2#2
• 7.3.1.2#3
• 7.3.1.2#4

31
Protocol Check #4: Uni-Directional
Check the contents of a Follow-Up Packet:
1. Verify that:
a. PDF field is set to 1. (7.3.3.2#2)
b. HopID is set to 3. (7.3.3.2#2)
c. Length is set to 60. (7.3.3.2#2)
2. Verify that T2 is equal to T3 and is consistently growing between every two consecutive packets by
TSPacketInterval. (TBD)
3. Verify that T2 is equal to T3 and variance is less than 32 ns.
4. If a packet is sent by Hub Router on the downstream port, verify that:
a. TimeOffsetFromHR is consistently growing like in Stat Sub #2.
b. FreqOffsetFromHR is constant like in Stat Sub #3.
c. There is correlation between TimeOffsetFromHR and FreqOffsetFromHR same as in Stat Sub #4.
5. If a packet is sent by Inter-Domain Time Responder or any DFP in Inter-Domain Time Initiator’s Domain,
verify that the following fields are 0 when IDE bit is set to 0 in Host Router:
a. IDTimeStamp. (TBD)
b. TimeOffsetFromInterDomain. (TBD)
c. FreqOffsetFromInterDomain. (TBD)
6. Otherwise (IDE bit is set to 1), verify that:
a. IDTimeStamp is constantly growing between every two consecutive packets. (TBD)
b. TimeOffsetFromInterDomain is consistently growing like in Stat Sub #8. (TBD)
c. FreqOffsetFromInterDomain is constant like in Stat Sub #9. (TBD)
d. There is correlation between TimeOffsetFromInterDomain and FreqOffsetFromInterDomain same
as in Stat Sub #10. (TBD)

Assertions checked:
• 7.3.3.2#2, 7.3.3.2#6

32
Protocol Check #5: Inter-Domain Timestamp Packet
1. Verify that Inter-Domain TimeStamp packet is sent every [(TSInterDomainInterval +1) *
TSPacketInterval)] µs. (7.3.2#6)
2. Verify that:
a. PDF is set to 2. (7.3.3.3#2)
b. HopID is set to 3. (7.3.3.3#2)
c. Length is set to 28. (7.3.3.3#2)
3. Verify that Bits 31:16 of DW 0 are set to 0 (reserved). (7.3.3.3#3)
4. Verify that the IDTimeStamp field (DW 2:0) has the format shown in Figure 7-6. (7.3.3.3#4)
5. Verify that:
a. IDTimeStamp is constantly growing between every two consecutive packets.
b. TimeOffsetFromInterDomain is consistently growing like in Stat Sub #8.
c. FreqOffsetFromInterDomain is constant like in Stat Sub #9.
d. There is correlation between TimeOffsetFromInterDomain and FreqOffsetFromInterDomain same
as in Stat Sub #10.

Assertions checked:
• 7.3.2#4
• 7.3.2#5
• 7.3.2#6
• 7.3.3.3#1
• 7.3.3.3#2
• 7.3.3.3#3
• 7.3.3.3#4
• 7.3.3.3#5
• 7.3.3.3#6

33
Statistics Functions
Stat Sub #1 LocalTime Consistency
1. Local Time is checked for consistency.
2. Read LocalTime in loop every second, 60 times.
3. Verify that the Average Time diff between the reads is 1 second (+/- 1%). (7.1.2.1#4, 7.1.2.1#5)

Assertions checked:
• 7.1.2.1#4
• 7.1.2.1#5

34
Stat Sub #2 Time Offset
1. Read in loop 60 times with 1 sec delay.
2. Average slope is calculated per read:

𝑇𝑜𝑓𝑓 [𝑁] − 𝑇𝑜𝑓𝑓 [1]

𝑇𝑎𝑣𝑔𝑁 =
𝑁−1

𝑇𝑜𝑓𝑓 [𝑁 + 1] − 𝑇𝑜𝑓𝑓 [1]

𝑇𝑎𝑣𝑔𝑁+1 =
𝑁

𝑇𝑎𝑣𝑔𝑁+1
𝑇𝑎𝑣𝑔𝑆𝑙𝑜𝑝𝑒𝐷𝑟𝑖𝑓𝑡 = −1
𝑇𝑎𝑣𝑔𝑁

3. Verify that:
a. Expected behavior is a consistent linear incline or decline (accuracy of 1%). (7.4.1#6, 7.4.1#7)

|𝑻𝒂𝒗𝒈𝑺𝒍𝒐𝒑𝒆𝑫𝒓𝒊𝒇𝒕 | ≤ 𝟎. 𝟎𝟏

b. For 1st hop, TimeOffsetFromHR is 0. (TBD)

c. For 2nd hop, TimeOffsetFromHR == TimeOffsetFromDFP. (7.1.2.2.#2)

Assertions checked:
• 7.1.2.2#1
• 7.1.2.2#2
• 7.1.2.2#3
• 7.4.1#6
• 7.4.1#7

35
Stat Sub #3 Frequency Offset
Repeat 60 times. For each step:
1. Read FreqOffsetFromHR. Save value to temporary variable FrequencyOffsetFromReg
2. To convert the value to ppm:
Polarity = FrequencyOffsetFromReg >> 31
If (Polarity == 1) { // negative value
FrequencyOffset = ConvertTwosCompliment(FrequencyOffsetFromReg)
}
Else {
FrequencyOffset = FrequencyOffsetFromReg
}
FrequencyOffsetPPM = FrequencyOffset * 106/241
3. Verify that:
a. Expected behavior is a constant FrequencyOffsetFromReg value with not more than 1 ppm
deviation from the average. (7.4.1#1-#4)
b. For 1st hop, FreqOffsetFromHR is 0. (TBD)
c. For 2nd hop, FreqOffsetFromHR == FreqOffsetFromDFP. (7.1.2.3#2)

Assertions checked:
• 7.4.1#1
• 7.4.1#2
• 7.4.1#3
• 7.4.1#4

36
Stat Sub #4 Correlation between Frequency and Time Offsets
For both OffsetFromDFP and OffsetFromHR, the following correlation is checked:
• The slope of TimeOffset is expected to be the equal to FreqOffset +/- 10%.
• TimeOffset is read 60 times once per second.
• Average slope is calculated:
o Toff[1] – time offset from first read.
o Toff[n] – time offset from last read.
o A = (Toff[n] – Toff[1])/((n-1)*1e9).
o Average Slope = A * 1e6 // the units are ppm.
• Compare Average Slope to Frequency Offset from Stat Sub #3 in ppm units.
• Verify the that correlation between the calculated and measured Frequency offset are less than 10.
(7.4.1#8):
o Abs( (Average Slope / Frequency Offset ) – 1) * 100 < 10.

Assertions checked:
• 7.4.1#8

37
Stat Sub #5 Propagation Delay

1. Read Propagation Delay 100 times. Compute average.

2. Verify that the Propagation Delay is constant (+/- 1%) (7.4.1#5).
3. Test with KG USB4 Host/Hub/Device.

Assertions checked:
• 7.4.1#5

38
Stat Sub #6 Computation Timestamp

1. Read 10 times with period of 1 sec between the reads.

2. Verify that the Computation Timestamp grows by approximately 1 sec relative to previous read value (+/-
5%). (7.3.1.1.#5)

Assertions checked:
• 7.3.1.1#5

39
Stat Sub #7 Inter-Domain Computation Timestamp

1. Read 10 times with period of 1 sec between the reads.

2. Verify that the Computation Timestamp grows by approximately 1 sec relative to previous read value (+/-
1%). (7.4.2.3#1)

Assertions checked:
• 7.4.2.3#1

40
Stat Sub #8 Inter-Domain Time Offset

1. Read in loop 60 times with 1 sec delay.

2. Average slope is calculated per read.
3. Verify that:
a. Expected behavior is a consistent linear incline or decline (accuracy of 1%). (TBD)
b. For 1st hop, TimeOffsetFromInterDomainHR is 0. (TBD)
c. For 2nd hop, TimeOffsetFromInterDomainHR == TimeOffsetFromInterDomainDFP. (TBD)

Assertions checked:
• TBD

41
Stat Sub #9 Inter-Domain Frequency Offset
Repeat 60 times. For each step:
1. Read FreqOffsetFromHR. Save value to temporary variable FrequencyOffsetFromReg.
2. To convert the value to ppm:
Polarity = FrequencyOffsetFromReg >> 31
If (Polarity == 1) { // negative value
FrequencyOffset = ConvertTwosCompliment(FrequencyOffsetFromReg)
}
Else {
FrequencyOffset = FrequencyOffsetFromReg
}
FrequencyOffsetPPM = FrequencyOffset * 106/241
3. Verify that:
a. Expected behavior is a constant FrequencyOffsetFromReg value with not more than 1 ppm
deviation from the average. (TBD)
b. For 1st hop, FreqOffsetFromInterDomainHR is 0. (TBD)
c. For 2nd hop, FreqOffsetFromInterDomainHR == FreqOffsetFromInterDomainDFP. (TBD)

Assertions checked:
• 7.4.2.3#2
• 7.4.2.3#3

42
Stat Sub #10 Correlation between Inter-Domain Frequency and Inter-Domain Time Offsets

For both OffsetFromInterDomainDFP and OffsetFromInterDomainHR, the following correlation is checked:

• The slope of TimeOffset is expected to be the equal to FreqOffset.

Test Example:
1. TimeOffset is read every second 60 times once every second.
2. If after averaging out the slope is ~100 ns per second, then the calculated Freq offset should be:
100
219902 = ∗ 241
109

3. FreqOffset is read and compared with calculated value.

4. Verify that the correlation between the calculated and measured Frequency offset are less than 1ppm.
(TBD)

Assertions checked:
• TBD

43
Stat Sub #11 Port Statistics for Bi-Directional DFP

1. Read first time to clear.

2. Read 10 times with period of less than 500ms between the reads.
3. If TMU mode is HiFi, verify that:
a. RX TSNOS counter changes.
b. TX TSNOS counter changes.
c. TX Packet counter changes.
4. Verify that the change of the three parameters is more than 20,000 counts per second in HiFi mode.
5. If TMU mode is OFF, verify that all four counters are 0 after 1st read.

Assertions checked:
• TBD

44
Stat Sub #12 Port Statistics for Bi-Directional UFP

1. Read first time to clear.

2. Read 10 times with period of less than 500ms between the reads.
3. If TMU mode is HiFi or LowRes, verify that:
a. RX TSNOS counter changes.
b. TX TSNOS counter changes.
c. RX Packet counter changes.
4. Verify that the change of the three parameters is more than 20,000 counts per second in HiFi mode.
5. Verify that the change of the three parameters is more than 250 counts per second in LowRes mode.
6. If TMU mode is OFF, verify that all four counters are 0 after 1 st read.

Assertions checked:
• TBD

45
Stat Sub #13 Port Statistics for Uni-Directional DFP

1. Read first time to clear.

2. Read 10 times with period of less than 500ms between the reads.
3. If TMU mode is HiFi or LowRes, verify that:
a. TX TSNOS counter changes.
b. TX Packet counter changes.
4. Verify that the change of the two parameters is more than 20,000 counts per second in HiFi mode.
5. Verify that the change of the two parameters is more than 250 counts per second in LowRes mode.
6. If TMU mode is OFF, verify that all four counters are 0 after 1 st read.

Assertions checked:
• TBD

46
Stat Sub #14 Port Statistics for Uni-Directional UFP

1. Read first time to clear.

2. Read 10 times with period of less than 500ms between the reads.
3. If TMU mode is HiFi or LowRes, verify that:
a. RX TSNOS counter changes.
b. TX TSNOS counter changes.
c. RX Packet counter changes.
4. Verify that the change of the two parameters is more than 20,000 counts per second in HiFi mode.
5. Verify that the change of the two parameters is more than 250 counts per second in LowRes mode.
6. If TMU mode is OFF, verify that all four counters are 0 after 1st read.

Assertions checked:
• TBD

47
Stat Sub #15 Port Statistics for Inter-Domain Timestamp Packets
Use Stat Sub #13 or Stat Sub #14 depending on TMU mode on inter-Domain Link.
Apply the Sub on the inter-Domain port.

Assertions checked:
• TBD

48
Time Posting Functions
Time Posting #1: Immediate Posting – 15 days

1. Read Local time in Host Router.

2. Write value of 15 days to Local time:
a. Value 0x83A10000 to Post Local Time Low.
b. Value 0x49AB4 to Post Local Time High.
c. Value 0xFFFFFFFF to Post Time High.
d. Value 0x1 to Post Time Low.
e. Value 0x0 to Post Time High.
3. Poll Post Time Low until it becomes 0x0.
4. Read Local time.
5. Verify that values are greater than:
a. LocalTime High[63:32] = 0x9AB483XX. (TBD)
b. LocalTime High[79:64] = 0x4. (TBD)

Note: LocalTime Low can be any value.

This function only used before enabling TMU in Hub and or Device.

Assertions checked:
• TBD

49
Time Posting #2: Immediate Posting – 1 hour

1. Read Local time in Host Router

2. Write value of 15 days to Local time:
a. Value 0xffff0000 to Post Local Time Low.
b. Value 0x0346 to Post Local Time High.
c. Value 0xFFFFFFFF to Post Time High.
d. Value 0x1 to Post Time Low.
e. Value 0x0 to Post Time High.
3. Poll Post Time Low until it becomes 0x0.
4. Read Local time.
5. Verify that values are greater than:
a. LocalTime High[63:44] = 0x03470. (TBD)
b. LocalTime High[79:64] = 0x0. (TBD)

Note: LocalTime Low can be any value.

This function only used before enabling TMU in Hub and or Device.

Assertions checked:
• TBD

50
Time Posting #3: Future Posting – 15 days
1. Read Local time in Host Router, Store it in LTH variable.
2. Add 10 sec to LTH.
3. Read current filters values: Freq Measurement Window , DelayAvgConst , OffsetAvgConst,
ErrorAvgConst.
4. Set All setup to LowRes Mode
5. Configure all the devices in the setup with following:
a. Write value of 15 days to Local time:
i. Value 0x83A10000 to Post Local Time Low.
ii. Value 0x49AB4 to Post Local Time High.
iii. Value 0xFFFFFFFF to Post Time High.
iv. Value LTH & 0xFFFFFFFF to Post Time Low.
v. Value (LTH >> 32) to Post Time High.
6. Poll Post Time Low in UUT until it becomes 0x0:
a. Timeout after 12 seconds (system time) if the posting hasn’t occurred. Report error.
b. Report error if time posting occurred earlier than 8 seconds (system time).
7. Read Local time in UUT and verify that values are greater than:
a. LocalTime High[63:32] = 0x9AB48XXX. (TBD)
b. LocalTime High[79:64] = 0x4. (TBD)
8. Restore filters to values from #3.

Note: LocalTime Low can be any value.

This function only used on the whole tree – Host, Hubs, and Peripheral Devices.

Assertions checked:
• TBD

51
Time Posting #4: Future Posting – 1 hour
1. Read Local time in Host Router, Store it in LTH variable.
2. Add 10 sec to LTH.
3. Read current filters values: Freq Measurement Window , DelayAvgConst , OffsetAvgConst,
ErrorAvgConst.
4. Set Filters to low level:
a. Freq Measurement Window = 30.
b. DelayAvgConst = 4.
c. OffsetAvgConst = 4.
d. ErrorAvgConst = 4.
5. Configure all the devices in the setup with following:
a. Write value of 15 days to Local time:
i. Value 0xffff0000 to Post Local Time Low.
ii. Value 0x00384 to Post Local Time High.
iii. Value 0xFFFFFFFF to Post Time High.
iv. Value LTH & 0xFFFFFFFF to Post Time Low.
v. Value (LTH >> 32) to Post Time High.
6. Read values of filters from TMU_RTR_CS_15 and store for future reference.
7. Write new filter value to TMU_RTR_CS_15.
8. Poll Post Time Low in UUT until it becomes 0x0.
a. Timeout after 12 seconds (system time) if the posting hasn’t occurred. Report error.
b. Report error if time posting occurred earlier than 8 seconds (system time).
9. Read Local time in UUT and verify that values are greater than:
a. LocalTime High[63:44] = 0x03470. (TBD)
b. LocalTime High[79:64] = 0x0. (TBD)
10. Restore filters to values from #3.

Note: LocalTime Low can be any value.

This function only used on the whole tree – Host, Hubs, and Peripheral Devices.

Assertions checked:
• TBD

52
Time Posting #5: Immediate Time Posting Upon Configuration
1. Read Local time in Host Router, Store it in LTH variable.
2. Configure all the devices in the setup with following:
a. Write following values to Local time:
i. Value LTH & 0xffffffff to Post Local Time Low.
ii. Value LTH >> 32 to Post Local Time High.
iii. Value 0xFFFFFFFF to Post Time High.
iv. Value 0x1 to Post Time Low.
v. Value 0x0 to Post Time High.
3. Poll Post Time Low in UUT until it becomes 0x0.
4. Read Local time in UUT.
5. Verify that LocalTime is within 100msec away from LTH

53
Test Setups
This section describes the test setups for USB4 Hosts, Hubs, and Peripheral Devices.

Single-Port Host
This section describes the test setups for a Host Router with one USB4 Port.
Single Domain (SD)

SD_HOST_DFP_TMU_01

Host System

USB4 CV

HI Adapter

UUT

USB4
USB4 Link Analyzer

Time
KG USB4 Time Serial Interface
Measurement
Device
Equipment

Inter-Domain (ID)

ID_HOST_DFP_TMU_02

Host System

USB4 CV

HI Adapter

UUT
IDTR

USB4
Inter-Domain
USB4 Link Analyzer

IDTI
Time Serial Interface
Time
KG USB4 Host Measurement
Equipment

54
 ID_HOST_DFP_TMU_03

Host System

USB4 CV

HI Adapter

UUT KG USB4
Host

USB4 Link USB4

USB4 Link
Analyzer

Time
KG USB4 KG USB4
Measurement Time Serial Device IDTI IDTRDevice
Equipment Interface Inter-Domain
USB4 Link

Time Serial Interface

ID_HOST_DFP_TMU_04

Host System

USB4 CV

HI Adapter
Inter-Domain
UUT KG USB4 USB4 Link KG USB4
UUT
Host IDTI IDTR Host
IDTI

USB4
Analyzer

KG USB4
Device
IDTR

Inter-Domain USB4 Link

55
Multi-Port Host
This section describes the test setups for a Host Router with more than one USB4 Port.
Single Domain (SD)

SD_HOST_DFP_TMU_05

Host System

USB4 CV

HI Adapter

UUT
UUT

USB4
USB4 Link USB4 Link Analyzer

Time
KG USB4 KG USB4 Time Serial Interface Measurement
Device Device Equipment

Time Serial Interface

Inter-Domain (ID)
ID_HOST_DFP_TMU_06

Host System
USB4
USB4 CV Analyzer

HI Adapter

Inter-Domain
UUT KG USB4 KG USB4
KG USB4 Host USB4 Link
Host IDTI IDTR Host
IDTR IDTI

USB4 Link

IDTR
KG USB4 KG USB4 KG USB4
Device Device Device
IDTI IDTR

Inter-Domain USB4 Link Inter-Domain USB4 Link Time Serial Interface

Time Serial Interface

Time
Measurement
Equipment

56
 ID_HOST_DFP_TMU_07

Host System

USB4 CV

HI Adapter

UUT KG USB4
UUT
Host

USB4 Link USB4 Analyzer

USB4 Link

KG USB4 KG USB4 KG USB4

Device Device Device
IDTI IDTR
Inter-Domain USB4 Link
Time Serial Interface

Time Serial Interface Time

Measurement
Equipment

57
Hub
This section describes the test setups for a USB4 Hub.
Single Domain (SD)

SD_HUB_UFP_TMU_08

SD_HUB_DFP_TMU_09

58
 SD_HUB_UFP_TMU_10

KG USB4
Host

USB4 Link

Time
KG USB4
Measurement
Device Time Serial Interface
Equipment

USB4 Link

USB4
UUT
Analyzer

USB4 Link

KG USB4 Time Serial Interface

Device

SD_HUB_DFP_TMU_11

KG USB4
Host

USB4 Link

Time
KG USB4
Measurement
Device Time Serial Interface
Equipment

USB4 Link

USB4
UUT
Analyzer

USB4 Link

KG USB4 Time Serial Interface

Device

59
Inter-Domain (ID)
ID_HUB_DFP_TMU_12

KG USB4
Host
Inter-Domain
KG USB4 KG USB4 USB4 Link
KG USB4
Host Host IDTI IDTR Host
IDTI KG USB4 IDTR
Device

KG USB4 KG USB4
UUT
Device Device
IDTR IDTI

Inter-Domain USB4 Link

Time Serial Interface
Inter-Domain USB4 Link

USB4
Analyzer

Time Serial Interface Time

Measurement
Equipment

ID_HUB_UFP_TMU_13

USB4
Analyzer
KG USB4
Host
Inter-Domain
KG USB4 KG USB4 KG USB4
USB4 Link
Host Host IDTI IDTR Host
IDTI KG USB4 IDTR
Device

KG USB4 KG USB4
UUT
Device Device
IDTR IDTI

Time Serial Interface

Inter-Domain USB4 Link Inter-Domain USB4 Link

Time Serial Interface

Time
Measurement
Equipment

60
 ID_HUB_DFP_TMU_14

KG USB4
Host

KG USB4
Device

USB4 Analyzer KG USB4

Host
IDTR
UUT

KG USB4 KG USB4
Device Device
IDTI

Time Serial Interface

Inter-Domain USB4 Link

Time Serial Interface Time

Measurement
Equipment

61
Peripheral Device
This section describes the test setups for a USB4 Peripheral Device.
Single Domain (SD)
SD_DEV_UFP_TMU_15

KG USB4 Host

USB4 Link
USB4
Analyzer

UUT

SD_DEV_UFP_TMU_16

KG USB4
Host

USB4 Link

KG USB4
Device

USB4 Link
USB4
Analyzer

UUT

62
Inter-Domain (ID)

ID_DEV_UFP_TMU_17

Inter-Domain
KG USB4 USB4 Link KG USB4
IDTI IDTR
Host Host

KG USB4
Device
USB4
Analyzer

UUT

63
USB4 Test Descriptions
Note: After each test, the TMU Mode is set to Off (i.e. the TMU is disabled) throughout the topology.

Single-Port Host
The tests in this section apply to a USB4 Host that has one USB4 Port.
Intra-Domain
TD 7.001 Bi-Directional HiFi Mode Test (Single-Port Host)
A. Purpose:
• Verify that the TMU in a USB4 Host behaves as expected in Bidirectional HiFi Mode
B. Repetitions:
• Repeat test with Single-Lane Link and Dual-Lane Link
• Repeat test at Gen 2 and Gen 3 speeds
C. Procedure:
1. Connect SD_HOST_DFP_TMU_01
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Bi-Directional HiFi mode in UUT
4. Configure TMU to Bi-Directional HiFi mode in KG USB4 Device
5. Run Time Calculation #1, N=1
6. Run Stat Sub #1 on Host Router
7. Run Stat Sub #2 on KG USB4 Device
8. Run Stat Sub #3 on KG USB4 Device
9. Run Stat Sub #4 on KG USB4 Device
10. Run Stat Sub #5 on KG USB4 Device
11. Run Stat Sub #6 on KG USB4 Device
12. Run Stat Sub #11 on Host Router
13. Run Stat Sub #12 on KG USB4 Device
14. Run Protocol Check #1
15. Run Protocol Check #2

64
 TD 7.002 Uni-Directional HiFi Mode Test (Single-Port Host)

A. Purpose:
• Verify that the TMU in a USB4 Host behaves as expected in Unidirectional HiFi Mode.
B. Procedure:
1. Connect SD_HOST_DFP_TMU_01
2. Configure USB4 Link according to Link Configuration #1
3. Configure KG USB4 Device to Unidirectional HiFi mode
4. Configure UUT to Unidirectional HiFi mode
5. Run Time Calculation #1, N=1
6. Run Stat Sub #1 on Host Router
7. Run Stat Sub #2 on KG USB4 Device
8. Run Stat Sub #3 on KG USB4 Device
9. Run Stat Sub #4 on KG USB4 Device
10. Run Stat Sub #6 on KG USB4 Device
11. Run Stat Sub #13 on Host Router
12. Run Stat Sub #14 on KG USB4 Device
13. Run Protocol Check #3
14. Run Protocol Check #4

65
 TD 7.003 Uni-Directional LowRes Mode Test (Single-Port Host)
A. Purpose:
• Verify that the TMU in a USB4 Host behaves as expected in LowRes Mode
B. Procedure:
1. Connect SD_HOST_DFP_TMU_01
2. Configure USB4 Link according to Link Configuration #1
3. Configure KG USB4 Device to Unidirectional LowRes mode
4. Configure UUT to Unidirectional LowRes mode
5. Proceed to the next steps as in TD 7.002 starting from step #5

66
 TD 7.004 TMU Mode Change Test (Single-Port Host)
A. Purpose:
• Verify that the TMU Mode change works properly in a USB4 Host
B. Procedure:
1. Connect SD_HOST_DFP_TMU_01
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Bi-Directional HiFi mode in UUT
4. Configure TMU to Bi-Directional HiFi mode in KG USB4 Device
5. Run Time Calculation #1, N=1
6. Run Stat Sub #1 on Host Router
7. Run Stat Sub #2 on KG USB4 Device
8. Run Stat Sub #3 on KG USB4 Device
9. Run Stat Sub #4 on KG USB4 Device
10. Run Stat Sub #5 on KG USB4 Device
11. Run Stat Sub #6 on KG USB4 Device
12. Run Stat Sub #11 on Host Router
13. Run Stat Sub #12 on KG USB4 Device
14. Run Protocol Check #1
15. Run Protocol Check #2
16. Change TMU mode to Uni-directional HiFi mode both in UUT and Device according to CM mode
change flow (see CM guide)
17. Wait 1 sec
18. Repeat steps #5 to #11
19. Run Stat Sub #13 on Host Router on both ports
20. Run Stat Sub #14 on KG USB4 Device on both ports
21. Run Protocol Check #3
22. Run Protocol Check #4
23. Change TMU mode to Uni-directional LowRes mode both in UUT and Device according to CM
mode change flow (see CM guide)
24. Wait 1 sec
25. Repeat steps #5 to #11
26. Run Stat Sub #13 on Host Router on both ports
27. Run Stat Sub #14 on KG USB4 Device on both ports
28. Run Protocol Check #3
29. Run Protocol Check #4
30. Change TMU mode to TMU OFF mode both in UUT and Device according to CM mode change
flow (see CM guide)
31. Run Stat Sub #11
32. Change TMU mode to Uni-directional LowRes mode both in UUT and Device according to CM
mode change flow (see CM guide)
33. Wait 1 sec
34. Repeat steps #5 to #11
35. Run Stat Sub #13 on Host Router on both ports
36. Run Stat Sub #14 on KG USB4 Device on both ports
37. Run Protocol Check #3
38. Run Protocol Check #4
39. Change TMU mode to Bi-Directional HiFi mode both in UUT and Device according to CM mode
change flow (see CM guide)
40. Wait 1 sec
41. Repeat steps #5 to #15

67
 TD 7.005 Future Time Posting Test – 15 days (Single-Port Host)
A. Purpose:
• Verify that Future Time posting works correctly in a USB4 Host
B. Procedure:
1. Connect SD_HOST_DFP_TMU_01
2. Configure USB4 Link according to Link Configuration #1
3. Configure UUT to Bi-Directional HiFi mode
4. Configure KG USB4 Device to Bi-Directional HiFi mode
5. Run Time Posting #3
6. Run Time Calculation #1, N=1
7. Run Stat Sub #1 on Host Router
8. Run Stat Sub #2 on KG USB4 Device
9. Run Stat Sub #3 on KG USB4 Device
10. Run Stat Sub #4 on KG USB4 Device
11. Run Stat Sub #6 on KG USB4 Device

68
 TD 7.006 Future Time Posting Test – 1 Hour (Single-Port Host)
A. Purpose:
• Verify that Future Time posting works correctly in a USB4 Host
B. Procedure:
12. Connect SD_HOST_DFP_TMU_01
13. Configure USB4 Link according to Link Configuration #1
14. Configure UUT to Bi-Directional HiFi mode
15. Configure KG USB4 Device to Bi-Directional HiFi mode
16. Run Time Posting #4
17. Run Time Calculation #1, N=1
18. Run Stat Sub #1 on Host Router
19. Run Stat Sub #2 on KG USB4 Device
20. Run Stat Sub #3 on KG USB4 Device
21. Run Stat Sub #4 on KG USB4 Device
22. Run Stat Sub #6 on KG USB4 Device

69
Inter-Domain

Note: The tests in this section are only run if the UUT supports Inter-Domain Time Synchronization.

TD 7.007 Inter-Domain Time Responder in Bi-Directional HiFi Mode Test (Single-Port Host)
A. Purpose:
• Verify that a USB4 Host behaves properly as Inter-Domain Time Responder
B. Repetitions:
• Repeat test with Single-Lane Link and Dual-Lane Link
C. Procedure:
1. Connect ID_HOST_DFP_TMU_02
2. Configure USB4 Link according to Link Configuration #1
3. Set KG Host Router as Inter-Domain Time Initiator by setting IDTI bit to 1
4. Set UUT as Inter-Domain Time Responder by setting IDTR bit to 1
5. Configure KG Host Router to Bi-Directional HiFi mode
6. Configure UUT to Bi-Directional HiFi mode
7. Run Time Calculation #1, N=1 on endpoint
8. Run Stat Sub #7 on KG USB4 Device
9. Run Stat Sub #8 on KG USB4 Device
10. Run Stat Sub #9 on KG USB4 Device
11. Run Stat Sub #10 on KG USB4 Device
12. Run Stat Sub #11 on Host Router
13. Run Stat Sub #12 on KG USB4 Device
14. Run Protocol Check #1
15. Run Protocol Check #2

70
 TD 7.008 Host Router in Inter-Domain Time Initiator Domain in Bi-Directional HiFi Mode Test
(Single-Port Host)

A. Purpose:
• Verify that a USB4 Host behaves properly in a time following Domain
B. Repetitions:
• Repeat test with Single-Lane Link and Dual-Lane Link
C. Procedure:
1. Connect ID_HOST_DFP_TMU_03
2. Configure USB4 Link according to Link Configuration #1
3. Set KG USB4 Device as Inter-Domain Time Initiator by setting IDTI bit to 1
4. Set KG Host Router as Inter-Domain Time Responder by setting IDTR bit to 1
5. Configure UUT to Bi-Directional HiFi mode
6. Configure KG USB4 Device to Bi-Directional HiFi mode
7. Configure KG Host Router to Bi-Directional HiFi mode
8. Set IDE bit to 1 in UUT
9. Run Time Calculation #2, N=1 on endpoints
10. Run Stat Sub #7 on KG USB4 Device
11. Run Stat Sub #8 on KG USB4 Device
12. Run Stat Sub #9 on KG USB4 Device
13. Run Stat Sub #10 on KG USB4 Device
14. Run Stat Sub #11 on Host Router
15. Run Stat Sub #12 on KG USB4 Device
16. Run Protocol Check #1
17. Run Protocol Check #2

71
 TD 7.009 Inter-Domain Time Initiator in Bi-Directional HiFi Mode Test (Single-Port Host)

A. Purpose:
• Verify that a USB4 Host behaves properly in a time Following Domain
B. Procedure:
1. Connect ID_HOST_DFP_TMU_04
2. Configure USB4 Link according to Link Configuration #1
3. Set KG USB4 Device as Inter-Domain Time Initiator by setting IDTI bit to 1
4. Set KG Host Router as Inter-Domain Time Responder by setting IDTR bit to 1
5. Configure UUT to Bi-Directional HiFi mode
6. Configure KG USB4 Device to Bi-Directional HiFi mode
7. Configure KG Host Router to Bi-Directional HiFi mode
8. Set IDE bit to 1 in UUT
9. Run Stat Sub #7 on KG USB4 Device
10. Run Stat Sub #8 on KG USB4 Device
11. Run Stat Sub #9 on KG USB4 Device
12. Run Stat Sub #10 on KG USB4 Device
13. Run Stat Sub #11 on Host Router
14. Run Stat Sub #12 on KG USB4 Device
15. Run Protocol Check #1
16. Run Protocol Check #2

72
 TD 7.010 Host Router in Inter-Domain Time Initiator Domain in Bi-Directional HiFi Mode Test
(Single-Port Host)

A. Purpose:
• Verify that a USB4 Host behaves properly as Inter-Domain Time Responder
B. Procedure:
1. Connect ID_HOST_DFP_TMU_06
2. Configure USB4 Link according to Link Configuration #1
3. Set KG USB4 Device as Inter-Domain Time Initiator by setting IDTI bit to 1
4. Set KG Host Router as Inter-Domain Time Responder by setting IDTR bit to 1
5. Configure UUT to Bi-Directional HiFi mode
6. Configure KG USB4 Device to Bi-Directional HiFi mode
7. Configure KG Host Router to Bi-Directional HiFi mode
8. Set IDE bit to 1 in UUT
9. Run Time Calculation #2, N=1 on devices
10. Run Stat Sub #7 on KG USB4 Device
11. Run Stat Sub #8 on KG USB4 Device
12. Run Stat Sub #9 on KG USB4 Device
13. Run Stat Sub #10 on KG USB4 Device
14. Run Stat Sub #11 on Host Router
15. Run Stat Sub #12 on KG USB4 Device
16. Run Protocol Check #1
17. Run Protocol Check #2

73
Multi-Port Host
The tests in this section apply to a USB4 Host that has more than one USB4 Port.
Intra-Domain

TD 7.011 Bi-Directional HiFi Mode Test (Multi-Port Host)

A. Purpose:
• Verify that the TMU in a USB4 Host behaves as expected in Bi-Directional HiFi Mode
B. Repetitions:
• Repeat test with Single-Lane Link and Dual-Lane Link
• Repeat test at Gen 2 and Gen 3 speeds
C. Procedure:
1. Connect SD_HOST_DFP_TMU_05
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Bi-Directional HiFi mode
4. Run Time Calculation #1, N=1 on both KG USB4 Devices
5. Run Time Calculation #2, N=1 between the KG USB4 Devices
6. Run Stat Sub #1 on Host Router
7. Run Stat Sub #2 on KG USB4 Device
8. Run Stat Sub #3 on KG USB4 Device
9. Run Stat Sub #4 on KG USB4 Device
10. Run Stat Sub #5 on KG USB4 Device
11. Run Stat Sub #6 on KG USB4 Device
12. Run Stat Sub #11 on Host Router on both ports
13. Run Stat Sub #12 on KG USB4 Device on both ports
14. Run Protocol Check #1
15. Run Protocol Check #2

74
 TD 7.012 Uni-Directional HiFi Mode Test (Multi-Port Host)

A. Purpose:
• Verify that the TMU in a USB4 Host behaves as expected in Uni-Directional HiFi Mode
B. Procedure:
1. Connect SD_HOST_DFP_TMU_05
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Bi-Directional HiFi mode
4. Run Time Calculation #1, N=1 on both KG USB4 Devices
5. Run Time Calculation #2, N=1 between the two KG USB4 Devices
6. Run Stat Sub #1 on Host Router
7. Run Stat Sub #2 on KG USB4 Device
8. Run Stat Sub #3 on KG USB4 Device
9. Run Stat Sub #4 on KG USB4 Device
10. Run Stat Sub #6 on KG USB4 Device
11. Run Stat Sub #13 on Host Router on both ports
12. Run Stat Sub #14 on KG USB4 Device on both ports
13. Run Protocol Check #3
14. Run Protocol Check #4

75
 TD 7.013 Uni-Directional LowRes Mode Test (Multi-Port Host)

A. Purpose:
• Verify that the TMU in a USB4 Host behaves as expected in LowRes Mode
B. Procedure:
1. Connect SD_HOST_DFP_TMU_05
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Unidirectional LowRes mode in UUT and KG USB4 Devices
4. Proceed the next steps as in TD 7.012 starting from step #4

76
 TD 7.014 TMU Mode Change Test (Multi-Port Host)

A. Purpose:
• Verify that the TMU in a USB4 Host behaves as expected in Bi-Directional HiFi Mode
B. Procedure:
1. Connect SD_HOST_DFP_TMU_05
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Bi-Directional HiFi mode
4. Run Time Calculation #1, N = 1 on both KG USB4 Devices
5. Run Time Calculation #2, N = 1 between the KG USB4 Devices
6. Run Stat Sub #1 on Host Router
7. Run Stat Sub #2 on KG USB4 Device
8. Run Stat Sub #3 on KG USB4 Device
9. Run Stat Sub #4 on KG USB4 Device
10. Run Stat Sub #5 on KG USB4 Device
11. Run Stat Sub #6 on KG USB4 Device
12. Run Stat Sub #11 on Host Router on both ports
13. Run Stat Sub #12 on KG USB4 Device on both ports
14. Run Protocol Check #1
15. Run Protocol Check #2
16. Change TMU mode to Uni-directional HiFi mode both in UUT and Device according to CM mode
change flow (see CM guide)
17. Wait 1 sec.
18. Repeat steps #5 to #11
19. Run Stat Sub #13 on Host Router on both ports
20. Run Stat Sub #14 on KG USB4 Device on both ports
21. Run Protocol Check #3
22. Run Protocol Check #4
23. Change TMU mode to Uni-directional LowRes mode both in UUT and Device according to CM
mode change flow (see CM guide)
24. Wait 1 sec
25. Repeat steps #5 to #11
26. Run Stat Sub #13 on Host Router on both ports
27. Run Stat Sub #14 on KG USB4 Device on both ports
28. Run Protocol Check #3
29. Run Protocol Check #4
30. Change TMU mode to TMU OFF mode both in UUT and Device according to CM mode change
flow (see CM guide)
31. Run Stat Sub #11
32. Change TMU mode to Uni-directional LowRes mode both in UUT and Device according to CM
mode change flow (see CM guide)
33. Wait 1 sec
34. Repeat steps #5 to #11
35. Run Stat Sub #13 on Host Router on both ports
36. Run Stat Sub #14 on KG USB4 Device on both ports
37. Run Protocol Check #3
38. Run Protocol Check #4
39. Change TMU mode to Bi-Directional HiFi mode both in UUT and Device according to CM mode
change flow (see CM guide)
40. Wait 1 sec
41. Repeat steps #5 to #15

77
 TD 7.015 Future Time Posting Test – 15 days (Multi-Port Host)
A. Purpose:
• Verify that Future Time posting is working as expected in a USB4 Host
B. Procedure:
1. Connect SD_HOST_DFP_TMU_05
2. Configure USB4 Link according to Link Configuration #1
3. Configure UUT to Bi-Directional HiFi mode
4. Configure KG USB4 Device to Bi-Directional HiFi mode
5. Run Time Posting #3
6. Run Time Calculation #1, N=1
7. Run Stat Sub #1 on Host Router
8. Run Stat Sub #2 on KG USB4 Device
9. Run Stat Sub #3 on KG USB4 Device
10. Run Stat Sub #4 on KG USB4 Device
11. Run Stat Sub #6 on KG USB4 Device

78
 TD 7.016 Future Time Posting Test – 1 hour (Multi-Port Host)
A. Purpose:
• Verify that Future Time posting is working as expected in a USB4 Host
B. Procedure:
1. Connect SD_HOST_DFP_TMU_05
2. Configure USB4 Link according to Link Configuration #1
3. Configure UUT to Bi-Directional HiFi mode
4. Configure KG USB4 Device to Bi-Directional HiFi mode
5. Run Time Posting #4
6. Run Time Calculation #1, N=1
7. Run Stat Sub #1 on Host Router
8. Run Stat Sub #2 on KG USB4 Device
9. Run Stat Sub #3 on KG USB4 Device
10. Run Stat Sub #4 on KG USB4 Device
11. Run Stat Sub #6 on KG USB4 Device

79
Inter-Domain

Note: The tests in this section are only run if the UUT supports Inter-Domain Time Synchronization.

TD 7.017 Inter-Domain Time Initiator and Time Responder in Bi-Directional HiFi Mode Test
A. Purpose:
• Verify that a USB4 Host behaves properly as Inter-Domain Time Responder
B. Repetitions:
• Repeat test with Single-Lane Link and Dual-Lane Link
C. Procedure:
1. Connect ID_HOST_DFP_TMU_06
2. Configure USB4 Link according to Link Configuration #1
3. Configure the topology to Bi-Directional HiFi mode
4. Run Time Calculation #1, N=1 on Inter-Domain Time Initiator (KG Host Router)
5. Run Time Calculation #2, N=1 between Inter-Domain Time Initiator (KG Host Router) and Inter-
Domain Host Router
6. Run Stat Sub #7 on UUT
7. Run Stat Sub #8 on UUT
8. Run Stat Sub #9 on UUT
9. Run Stat Sub #10 on UUT
10. Run Stat Sub #11 on UUT all ports
11. Run Stat Sub #12 on KG USB4 Device
12. Run Protocol Check #1 on UUT ports
13. Run Protocol Check #2 on UUT ports

80
Hub
The tests in this section apply to a USB4 Hub.
Intra-Domain

TD 7.018 Bi-Directional HiFi Mode as 2nd Hop Test (Hub UFP)

A. Purpose:
• Verify that the TMU in a USB4 Hub behaves as expected in Bi-Directional HiFi Mode
B. Repetitions:
• Repeat test with Single-Lane Link and Dual-Lane Link
• Repeat test at Gen 2 and Gen 3 speeds
C. Procedure:
1. Connect SD_HUB_UFP_TMU_08
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Bi-Directional HiFi mode
4. Run Time Calculation #1, N=1 on KG USB4 Device
5. Run Stat Sub #1 on UUT

Measurements on Hub as DFP:

6. Run Stat Sub #2 on UUT

7. Run Stat Sub #3 on UUT
8. Run Stat Sub #4 on UUT
9. Run Stat Sub #5 on UUT upstream port
10. Run Stat Sub #6 on UUT
11. Run:
• If mode is Bi-directional Stat Sub #11 on KG Router above UUT
• If mode is Uni-directional Stat Sub #13 on KG Router above UUT
12. Run:
• If mode is Bi-directional Stat Sub #12 on UUT on upstream port
• If mode is Uni-directional Stat Sub #14 on KG Router above UUT
13. Run:
• If mode is Bi-directional Protocol Check #1 on UUT upstream port
• If mode is Uni-directional Protocol Check #3 on UUT upstream port

14. Run:
• If mode is Bi-directional Protocol Check #2 on UUT upstream port
• If mode is Uni-directional Protocol Check #4 on UUT upstream port

81
 TD 7.019 Bi-Directional HiFi Mode as 2nd Hop Test (Hub DFP)
A. Purpose:
• Verify that the TMU in a USB4 Hub behaves as expected in Bi-Directional HiFi Mode
B. Repetitions:
• Repeat test with Single-Lane Link and Dual-Lane Link
• Repeat test at Gen 2 and Gen 3 speeds
C. Procedure:
1. Connect SD_HUB_DFP_TMU_09
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Bi-Directional HiFi mode
4. Run Time Calculation #1, N=1 on KG USB4 Device
5. Run Stat Sub #1 on UUT

Measurements of the effect of Hub as DFP:

6. Run Stat Sub #2 on KG USB4 Device

7. Run Stat Sub #3 on KG USB4 Device
8. Run Stat Sub #4 on KG USB4 Device
9. Run Stat Sub #5 on KG USB4 Device
10. Run Stat Sub #6 on KG USB4 Device
11. Run:
• If mode is Bi-directional Stat Sub #11 on UUT on downstream port
• If mode is Uni-directional Stat Sub #13 on UUT on downstream port
12. Run:
• If mode is Bi-directional Stat Sub #12 on UUT on upstream port
• If mode is Uni-directional Stat Sub #14 on KG USB4 Device
13. Run:
• If mode is Bi-directional Protocol Check #1 on KG USB4 Device
• If mode is Uni-directional Protocol Check #3 on KG USB4 Device
14. Run:
• If mode is Bi-directional Protocol Check #2 on KG USB4 Device
• If mode is Uni-directional Protocol Check #4 on KG USB4 Device

82
 TD 7.020 Uni-Directional HiFi Mode as 2nd Hop Test (Hub UFP)
A. Purpose:
• Verify that the TMU in a USB4 Hub behaves as expected in Uni-Directional HiFi Mode
B. Procedure:
1. Same as TD 7.018 only with UUT and Host configured to Uni-Directional HiFi mode
2. All the rest of the tree is configured to Bi-Directional HiFi mode

83
 TD 7.021 Uni-Directional HiFi Mode as 2nd Hop Test (Hub DFP)
A. Purpose:
• Verify that the TMU in a USB4 Hub behaves as expected in Uni-Directional HiFi Mode
B. Procedure:
1. Same as TD 7.019 only with UUT and Host configured to Uni-Directional HiFi mode
2. All the rest of the tree is configured to Bi-Directional HiFi mode

84
 TD 7.022 Uni-Directional LowRes Mode as 2nd Hop Test (Hub UFP)
A. Purpose:
• Verify that the TMU in a USB4 Hub behaves as expected in Uni-Directional LowRes Mode
B. Procedure:
1. Same as TD 7.018 only with UUT and Host configured to Uni-Directional LowRes mode
2. All the rest of the tree is configured to Bi-Directional HiFi mode

85
 TD 7.023 Uni-Directional LowRes Mode as 2nd Hop Test (Hub DFP)
A. Purpose:
• Verify that the TMU in a USB4 Hub behaves as expected in Uni-Directional LowRes Mode
B. Procedure:
1. Same as TD 7.019 only with UUT and Host configured to Uni-Directional LowRes mode
2. All the rest of the tree is configured to Bi-Directional HiFi mode

86
 TD 7.024 Bi-Directional HiFi Mode as 3rd Hop Test (Hub UFP)
A. Purpose:
• Verify that the TMU in a USB4 Hub behaves as expected in Bi-Directional HiFi Mode
B. Procedure:
1. Connect SD_HUB_UFP_TMU_10
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Bi-Directional HiFi mode
4. Run Time Calculation #1, N=1 on KG USB4 Device
5. Run Time Calculation #2, N=1 between the KG Router and KG USB4 Device
6. Run Stat Sub #1 on UUT
Measurements on Hub as DFP:
7. Run Stat Sub #2 on UUT
8. Run Stat Sub #3 on UUT
9. Run Stat Sub #4 on UUT
10. Run Stat Sub #6 on UUT
11. Run Stat Sub #11 on KG Router above UUT
12. Run Stat Sub #12 on UUT on upstream port
13. Run Protocol Check #1 on UUT upstream port
14. Run Protocol Check #2 on UUT upstream port

87
 TD 7.025 Bi-Directional HiFi Mode as 3rd Hop Test (Hub DFP)
A. Purpose:
• Verify that the TMU in a USB4 Hub behaves as expected in Bi-Directional HiFi Mode
B. Procedure:
1. Connect SD_HUB_DFP_TMU_11
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Bi-Directional HiFi mode
4. Run Time Calculation #1, N=1 on KG USB4 Device
5. Run Time Calculation #2, N=1 between the KG Router and KG USB4 Device
6. Run Stat Sub #1 on UUT
Measurements of the effect of Hub as DFP:
7. Run Stat Sub #2 on KG USB4 Device
8. Run Stat Sub #3 on KG USB4 Device
9. Run Stat Sub #4 on KG USB4 Device
10. Run Stat Sub #6 on KG USB4 Device
11. Run Stat Sub #11 on UUT on downstream port
12. Run Stat Sub #12 on KG USB4 Device
13. Run Protocol Check #1 on KG USB4 Device
14. Run Protocol Check #2 on KG USB4 Device

88
 TD 7.026 TMU Mode Change Test (Hub UFP)
A. Purpose:
• Verify that the TMU in a USB4 Hub behaves as expected in Bi-Directional HiFi Mode
B. Procedure:
1. Connect SD_HUB_UFP_TMU_08
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Bi-Directional HiFi mode
4. Run Time Calculation #1, N=1 on KG USB4 Device
5. Run Stat Sub #1 on UUT

Measurements on Hub as DFP:

6. Run Stat Sub #2 on UUT

7. Run Stat Sub #3 on UUT
8. Run Stat Sub #4 on UUT
9. Run Stat Sub #5 on UUT upstream port
10. Run Stat Sub #6 on UUT
11. Run:
• If in Bi-directional mode Stat Sub #11 on KG Router above UUT
• If in Uni-directional mode Stat Sub #13 on KG Router above UUT
12. Run:
• If in Bi-directional mode Stat Sub #12 on UUT on upstream port
• If in Uni-directional mode Stat Sub #14 on UUT on upstream port
13. Run:
• If in Bi-directional mode Protocol Check #1 on UUT upstream port
• If in Uni-directional mode Protocol Check #3 on UUT upstream port
14. Run:
• If in Bi-directional mode Protocol Check #2 on UUT upstream port
• If in Uni-directional mode Protocol Check #4 on UUT upstream port
15. Change TMU mode to Uni-Directional HiFi mode both in Host and UUT according to CM mode
change flow (see CM guide)
16. Wait 1 sec
17. Repeat steps #4 to #24
18. Change TMU mode to Uni-Directional LowRes mode both in Host and UUT according to CM
mode change flow (see CM guide)
19. Wait 1 sec
20. Repeat steps #4 to #24
21. Change TMU mode to OFF mode both in Host and UUT according to CM mode change flow (see
CM guide)
22. Wait 1 sec
23. Run Stat Sub #11
24. Change TMU mode to Uni-Directional LowRes mode both in Host and UUT according to CM
mode change flow (see CM guide)
25. Wait 1 sec
26. Repeat steps #4 to #24

89
 TD 7.027 TMU Mode Change Test (Hub DFP)
A. Purpose:
• Verify that the TMU in a USB4 Hub behaves as expected in Bi-Directional HiFi Mode
B. Procedure:
1. Connect SD_HUB_DFP_TMU_09
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Bi-Directional HiFi mode
4. Run Time Calculation #1, N=1 on KG USB4 Device
5. Run Stat Sub #1 on UUT

Measurements of the effect of Hub as DFP:

6. Run Stat Sub #2 on KG USB4 Device

7. Run Stat Sub #3 on KG USB4 Device
8. Run Stat Sub #4 on KG USB4 Device
9. Run Stat Sub #5 on KG USB4 Device
10. Run Stat Sub #6 on KG USB4 Device
11. Run:
• If in Bi-directional mode Stat Sub #11 on UUT on downstream port
• If in Uni-directional mode Stat Sub #13 on UUT on downstream port
12. Run:
• If in Bi-directional mode Stat Sub #12 on KG USB4 Device
• If in Uni-directional mode Stat Sub #14 on KG USB4 Device
13. Run:
• If in Bi-directional mode Protocol Check #1 on KG USB4 Device
• If in Uni-directional mode Protocol Check #3 on KG USB4 Device
14. Run:
• If in Bi-directional mode Protocol Check #2 on KG USB4 Device
• If in Uni-directional mode Protocol Check #4 on KG USB4 Device
15. Change TMU mode to Uni-Directional HiFi mode both in Host and UUT according to CM mode
change flow (see CM guide)
16. Wait 1 sec
17. Repeat steps #4 to #24
18. Change TMU mode to Uni-Directional LowRes mode both in Host and UUT according to CM
mode change flow (see CM guide)
19. Wait 1 sec
20. Repeat steps #4 to #24
21. Change TMU mode to OFF mode both in Host and UUT according to CM mode change flow (see
CM guide)
22. Wait 1 sec
23. Run Stat Sub #11
24. Change TMU mode to Uni-Directional LowRes mode both in Host and UUT according to CM
mode change flow (see CM guide)
25. Wait 1 sec
26. Repeat steps #4 to #24

90
 TD 7.028 Immediate Time Posting Test – 15 days (Hub)
A. Purpose:
• Verify that Immediate Time posting is working as expected in a in a USB4 Hub
B. Procedure:
1. Connect SD_HUB_UFP_TMU_08
2. Run Time Posting #1 on Host
3. Configure USB4 Link according to Link Configuration #1
4. Configure UUT to Bi-Directional HiFi mode
5. Configure KG USB4 Device to Bi-Directional HiFi mode
6. Run Time Calculation #1, N=1
7. Run Stat Sub #1 on Host Router
8. Run Stat Sub #2 on KG USB4 Device
9. Run Stat Sub #3 on KG USB4 Device
10. Run Stat Sub #4 on KG USB4 Device
11. Run Stat Sub #6 on KG USB4 Device

91
 TD 7.029 Immediate Time Posting – 1 hour (Hub)
A. Purpose:
• Verify that Immediate Time posting is working as expected in a USB4 Hub
B. Procedure:
1. Connect SD_HUB_UFP_TMU_08
2. Run Time Posting #2 on Host
3. Configure USB4 Link according to Link Configuration #1
4. Configure UUT to Bi-Directional HiFi mode
5. Configure KG USB4 Device to Bi-Directional HiFi mode
6. Run Time Calculation #1, N=1
7. Run Stat Sub #1 on Host Router
8. Run Stat Sub #2 on KG USB4 Device
9. Run Stat Sub #3 on KG USB4 Device
10. Run Stat Sub #4 on KG USB4 Device
11. Run Stat Sub #6 on KG USB4 Device

92
 TD 7.030 Future Time Posting Test – 15 days (Hub)
A. Purpose:
• Verify that Future Time posting is working as expected in a USB4 Hub
B. Procedure:
1. Connect SD_HUB_UFP_TMU_08
2. Configure USB4 Link according to Link Configuration #1
3. Configure UUT to Bi-Directional HiFi mode
4. Configure KG USB4 Device to Bi-Directional HiFi mode
5. Run Time Posting #3 on whole setup
6. Run Time Calculation #1, N=1
7. Run Stat Sub #1 on Host Router
8. Run Stat Sub #2 on KG USB4 Device
9. Run Stat Sub #3 on KG USB4 Device
10. Run Stat Sub #4 on KG USB4 Device
11. Run Stat Sub #6 on KG USB4 Device

93
 TD 7.031 Future Time Posting Test – 1 hour (Hub)
A. Purpose:
• Verify that Future Time posting is working as expected in a USB4 Hub
B. Procedure:
1. Connect SD_HUB_UFP_TMU_08
2. Configure USB4 Link according to Link Configuration #1
3. Configure UUT to Bi-Directional HiFi mode
4. Configure KG USB4 Device to Bi-Directional HiFi mode
5. Run Time Posting #4 on whole setup
6. Run Time Calculation #1, N=1
7. Run Stat Sub #1 on Host Router
8. Run Stat Sub #2 on KG USB4 Device
9. Run Stat Sub #3 on KG USB4 Device
10. Run Stat Sub #4 on KG USB4 Device
11. Run Stat Sub #6 on KG USB4 Device

94
Inter-Domain

TD 7.032 Inter-Domain Time Initiator and Time Responder in Bi-Directional HiFi Mode Test (Hub
DFP)

A. Purpose:
• Verify that a USB4 Hub DFP behaves properly as Inter-Domain Time Initiator and Time
Responder
B. Repetitions:
• Repeat test with Single-Lane Link and Dual-Lane Link
C. Procedure:
1. Connect ID_HUB_DFP_TMU_12
2. Configure USB4 Link according to Link Configuration #1
3. Configure the topology to Bi-Directional HiFi mode
4. Run Time Calculation #1, N=1 on Inter-Domain Time Initiator (KG Host Router)
5. Run Time Calculation #2, N=1 between Inter-Domain Time Initiator (KG Host Router) and Inter-
Domain Host Router
6. Run Stat Sub #7 on UUT
7. Run Stat Sub #8 on UUT
8. Run Stat Sub #9 on UUT
9. Run Stat Sub #10 on UUT
10. Run Stat Sub #15 on UUT IDTI port
11. Run Protocol Check #1 on UUT IDTI port
12. Run Protocol Check #2 on UUT IDTI port
13. Run Protocol Check #4 on UUT IDTI port

95
 TD 7.033 Inter-Domain Time Initiator and Time Responder in Bi-Directional HiFi Mode Test (Hub
UFP)

A. Purpose:
• Verify that a USB4 Hub UFP behaves properly as Inter-Domain Time Initiator and Time
Responder
B. Repetitions:
• Repeat test with Single-Lane Link and Dual-Lane Link
C. Procedure:
1. Connect ID_HUB_UFP_TMU_13
2. Configure USB4 Link according to Link Configuration #1
3. Configure the topology to Bi-Directional HiFi mode
4. Run Time Calculation #1, N=1 on Inter-Domain Time Initiator (KG Host Router)
5. Run Time Calculation #2, N=1 between Inter-Domain Time Initiator (KG Host Router) and Inter-
Domain Host Router
6. Run Stat Sub #7 on UUT
7. Run Stat Sub #8 on UUT
8. Run Stat Sub #9 on UUT
9. Run Stat Sub #10 on UUT
10. Run Stat Sub #15 on UUT IDTI port
11. Run Protocol Check #1 on UUT IDTI port
12. Run Protocol Check #2 on UUT IDTI port
13. Run Protocol Check #4 on UUT IDTI port
14. Run Protocol Check #5 on UUT upstream port

96
 TD 7.034 Hub in Inter-Domain Time Initiator Domain Forwarding Interdomain Timestamp Packets

A. Purpose:
• Verify that a USB4 Hub forwards Interdomain Timestamp packets properly
B. Repetitions:
• Repeat test with Single-Lane Link and Dual-Lane Link
C. Procedure:
1. Connect ID_HUB_DFP_TMU_14
2. Configure USB4 Link according to Link Configuration #1
3. Configure the topology to Bi-Directional HiFi mode
4. Run Time Calculation #1, N=1 on Inter-Domain Time Initiator (KG Host Router)
5. Run Time Calculation #2, N=1 between Inter-Domain Time Initiator (KG Host Router) and Inter-
Domain Host Router
6. Run Stat Sub #7 on the upstream KG USB4 Device
7. Run Stat Sub #8 on the upstream KG USB4 Device
8. Run Stat Sub #9 on the upstream KG USB4 Device
9. Run Stat Sub #10 on the upstream KG USB4 Device
10. Run Stat Sub #11 on the Host Router
11. Run Stat Sub #12 on the downstream KG USB4 Device
12. Run Stat Sub #15 on UUT IDTI port
13. Run Protocol Check #1 on UUT upstream port
14. Run Protocol Check #2 on UUT upstream port
15. Run Protocol Check #5 on UUT upstream port

97
Peripheral Device
The tests in this section apply to a USB4 Peripheral Device.
Intra-Domain

TD 7.035 Bi-Directional HiFi Mode as 2nd Hop Test (Peripheral Device)

A. Purpose:
• Verify that the TMU in a USB4 Peripheral Device behaves as expected in Bidirectional HiFi
Mode
B. Repetitions:
• Repeat test with Single-Lane Link and Dual-Lane Link
• Repeat test at Gen 2 and Gen 3 speeds
C. Procedure:
1. Connect SD_DEV_UFP_TMU_15
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Bi-Directional HiFi mode
4. Run Stat Sub #1 on UUT
5. Run Stat Sub #2 on UUT
6. Run Stat Sub #3 on UUT
7. Run Stat Sub #4 on UUT
8. Run Stat Sub #5 on UUT
9. Run Stat Sub #6 on UUT
10. Run Stat Sub #11 on KG upstream Router
11. Run Stat Sub #12 on UUT
12. Run Protocol Check #1 on UUT
13. Run Protocol Check #2 on UUT

98
 TD 7.036 Uni-Directional HiFi Mode as 2nd Hop Test (Peripheral Device)

A. Purpose:
• Verify that the TMU in a USB4 Peripheral Device behaves as expected in Uni-Directional HiFi
Mode
B. Procedure:
1. Connect SD_DEV_UFP_TMU_15
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Uni-Directional HiFi mode
4. Run Stat Sub #1 on UUT
5. Run Stat Sub #2 on UUT
6. Run Stat Sub #3 on UUT
7. Run Stat Sub #4 on UUT
8. Run Stat Sub #6 on UUT
9. Run Stat Sub #14 on UUT
10. Run Protocol Check #3 on UUT
11. Run Protocol Check #4 on UUT

99
 TD 7.037 Uni-Directional LowRes Mode as 2nd Hop Test (Peripheral Device)

A. Purpose:
• Verify that the TMU in a USB4 Peripheral Device behaves as expected in Uni-Directional
LowRes Mode
B. Procedure:
1. Connect SD_DEV_UFP_TMU_15
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Uni-Directional HiFi mode
4. Run Stat Sub #1 on UUT
5. Run Stat Sub #2 on UUT
6. Run Stat Sub #3 on UUT
7. Run Stat Sub #4 on UUT
8. Run Stat Sub #6 on UUT
9. Run Stat Sub #14 on UUT
10. Run Protocol Check #3 on UUT
11. Run Protocol Check #4 on UUT

100
 TD 7.038 Uni-Directional HiFi Mode as 3rd Hop Test (Peripheral Device)

A. Purpose:
• Verify that the TMU in a USB4 Peripheral Device behaves as expected in Uni-Directional
LowRes Mode
B. Procedure:
1. Connect SD_DEV_UFP_TMU_16
2. Configure USB4 Link according to Link Configuration #1
3. Configure TMU to Uni-Directional HiFi mode
4. Run Stat Sub #1 on UUT
5. Run Stat Sub #2 on UUT
6. Run Stat Sub #3 on UUT
7. Run Stat Sub #4 on UUT
8. Run Stat Sub #6 on UUT
9. Run Stat Sub #14 on UUT
10. Run Protocol Check #3 on UUT
11. Run Protocol Check #4 on UUT

101
 TD 7.039 Immediate Time Posting Test – 15 days (Peripheral Device)
A. Purpose:
• Verify that Immediate Time posting is working as expected in a USB4 Peripheral Device.
B. Procedure:
1. Connect SD_DEV_UFP_TMU_15
2. Run Time Posting #1 on Host
3. Configure USB4 Link according to Link Configuration #1
4. Configure UUT to Bi-Directional HiFi mode
5. Run Stat Sub #1 on UUT
6. Run Stat Sub #2 on UUT
7. Run Stat Sub #3 on UUT
8. Run Stat Sub #4 on UUT
9. Run Stat Sub #6 on UUT
10. Run Stat Sub #12 on UUT
11. Run Protocol Check #1 on UUT
12. Run Protocol Check #2 on UUT

102
 TD 7.040 Immediate Time Posting Test – 1 hour (Peripheral Device)
A. Purpose:
• Verify that Immediate Time posting is working as expected in a USB4 Peripheral Device
B. Procedure:
1. Connect SD_DEV_UFP_TMU_15
2. Run Time Posting #2 on Host
3. Configure USB4 Link according to Link Configuration #1
4. Configure UUT to Bi-Directional HiFi mode
5. Run Stat Sub #1 on UUT
6. Run Stat Sub #2 on UUT
7. Run Stat Sub #3 on UUT
8. Run Stat Sub #4 on UUT
9. Run Stat Sub #6 on UUT
10. Run Stat Sub #12 on UUT
11. Run Protocol Check #1 on UUT
12. Run Protocol Check #2 on UUT

103
 TD 7.041 Future Time Posting Test – 15 days (Peripheral Device)
A. Purpose:
• Verify that Immediate Time posting is working as expected in a USB4 Peripheral Device
B. Procedure:
1. Connect SD_DEV_UFP_TMU_15
2. Configure USB4 Link according to Link Configuration #1
3. Configure UUT to Bi-Directional HiFi mode
4. Run Time Posting #3 on whole setup
5. Run Stat Sub #1 on UUT
6. Run Stat Sub #2 on UUT
7. Run Stat Sub #3 on UUT
8. Run Stat Sub #4 on UUT
9. Run Stat Sub #6 on UUT
10. Run Stat Sub #12 on UUT
11. Run Protocol Check #1 on UUT
12. Run Protocol Check #2 on UUT

104
 TD 7.042 Future Time Posting Test – 1 hour (Peripheral Device)
A. Purpose:
• Verify that Immediate Time posting is working as expected in a USB4 Peripheral Device
B. Procedure:
1. Connect SD_DEV_UFP_TMU_15
2. Configure USB4 Link according to Link Configuration #1
3. Configure UUT to Bi-Directional HiFi mode
4. Run Time Posting #4 on whole setup
5. Run Stat Sub #1 on UUT
6. Run Stat Sub #2 on UUT
7. Run Stat Sub #3 on UUT
8. Run Stat Sub #4 on UUT
9. Run Stat Sub #6 on UUT
10. Run Stat Sub #12 on UUT
11. Run Protocol Check #1 on UUT
12. Run Protocol Check #2 on UUT

105
Inter-Domain

TD 7.043 Bi-Directional HiFi Mode Test (Peripheral Device) on Inter-Domain Link

A. Purpose:
• Verify that the TMU in a USB4 Peripheral Device behaves properly as Inter-Domain Time
Initiator
B. Repetitions:
• Repeat test with Single-Lane Link and Dual-Lane Link
C. Procedure:
1. Connect ID_DEV_UFP_TMU_17
2. Configure USB4 Link according to Link Configuration #1
3. Configure the topology to Bi-Directional HiFi mode
4. Run Stat Sub #7 on UUT
5. Run Stat Sub #8 on UUT
6. Run Stat Sub #9 on UUT
7. Run Stat Sub #10 on UUT
8. Run Stat Sub #12 on UUT

106
TBT3-Compatibility Test Descriptions
The tests in this section are only performed if the USB4 Product implements TBT3-Compatibility as defined in
Chapter 13 of the USB4 Specification. There are no TBT3-Compatibility tests for a USB4 Host.

Note: After each test, the TMU Mode is set to Off (i.e. the TMU is disabled) throughout the topology.

107
Hub
Intra-Domain
TD 7.044 Intra-Domain Two Single-Lane Links Test (Hub UFP)
A. Purpose:
• Verify that a USB4 Hub behaves properly with Two Single-Lane Links
B. Procedure:
1. Connect SD_HUB_UFP_TMU_08
2. Configure upstream USB4 Link according to Link Configuration #2
3. Configure downstream USB4 Link according to Link Configuration #2
4. Configure Lane 0 and Lane 1 to be active
5. Continue as in TD 7.018 from step #3

108
 TD 7.045 Intra-Domain Two Single-Lane Links Test (Hub DFP)
A. Purpose:
• Verify that a USB4 Hub behaves properly with Two Single-Lane Links
B. Procedure:
1. Connect SD_HUB_DFP_TMU_09
2. Configure upstream USB4 Link according to Link Configuration #2
3. Configure downstream USB4 Link according to Link Configuration #2
4. Configure Lane 0 and Lane 1 to be active
5. Continue as in TD 7.019 from step #3

109
 TD 7.046 Intra-Domain One Single-Lane Link Test (Hub)
Same as TD 7.044 only with Lane 1 active

110
Inter-Domain
TD 7.047 Inter-Domain Two Single-Lane Links Test (Hub)
A. Purpose:
• Verify that a USB4 Hub behaves properly with Two Single-Lane Links
B. Procedure:
1. Connect ID_HUB_DFP_TMU_12
2. Configure upstream USB4 Link according to Link Configuration #2
3. Configure inter-Domain USB4 Link according to Link Configuration #2
4. Configure Lane 0 and Lane 1 to be active
5. Configure Bi-Directional mode
6. Continue as in TD 7.032 from step #4

111
 TD 7.048 Inter-Domain One Single-Lane Link Test (Hub)
Same as TD 7.047 only with Lane 1 active

112