Platform

Test Interface	・10GbE (SFP+) or 1GbE (SFP) x2 ports ・10/100/1000BASE-T (RJ-45) x2 ports ・T1/E1 (RJ-45) x1 port ・T1/E1 (BNC) x2 ports ・Female SMA for GNSS x1 port ・Female SMA for PPS input/output x3 ports
Clock Interface	Input Clock Interface ・GNSS (SMA) ・T1/E1 (BNC) ・1544 KHz / 2048 KHz (BNC) ・10 MHz (BNC) ・PPS (SMA) ・ToD (RJ45) Output Clock Interface ・2048 KHz (BNC) ・10 MHz (BNC) ・PPS (SMA) ・ToD (RJ45)
Operation / Result	・Graph display of wander analysis ・Touch screen operation ・Remote operation by VNC ・Export test results in PDF / TXT / CSV format to USB or SD port ・Transfer of test results via LAN
Fielding	・Rubber protection ・Lightweight carry bag ・Password Security
Battery Life	・~12 hours when performing T1/E1 tests ・~10 hours when performing GbE tests ・~6 hours when performing 10 GbE tests

Time / Clock

Built-in Clock Accuracy	・Standard clock ±2.0 ppm ・OCXO clock ±0.1 ppm ・Rubidium clock ±5.0e-11 (600s warm up is necessary for co-operation with GPS)
Built-in Rubidium Clock	Self (no GPS) ・Frequency accuracy (7.5 min warm-up): ±1.0e-9 ・Frequency accuracy (24 hours warm-up): ±5.0 e-11 ・Aging (24 hours warm-up): ±0.5e-11 ・Aging (1 year): ±1e-9 GPS Clock ・Time accuracy (after 24-hour locking): ±50 ns Holdover (after 24 hours locking) ・Frequency accuracy: 1.5e-11 / 24 hours ・Time accuracy: ±100 ns / 2 hours, ±1.0 μs / 24 hours
Input Clock Reference	・Rate: 1.544 Mb/s, 2.048 Mb/s, 1.544 MHz, 2.048 MHz, 10 MHz ・Built-in GPS receiver, 1 pps ・SyncE
Output Clock	・1.544 MHz, 2.048 MHz, 10 MHz ・1 pps

SyncE, PTP Test

・PTP profile: Telecom and Power ・Encapsulation: Ethernet, UDP ・Clock Emulation: master/slave, unicast/multicast, 128 packet/s ・PDV capture, protocol analysis, collection field support
Ethernet PTP Frequency Test	・Floor delay population (G.8260): FPC, FPR, FPP ・Wander: analysis and generation TIE, MTIE, TDEV (real time)
Ethernet PTP Phase Test	・Measurement with GbE, 1 pps interface ・Time error (TE): maximum (max | TE |), dynamic (dTE), constance (cTE)
1 PPS Test	・1 pps test ・Wander: TIE, MTIE, TDEV ・Time error (TE): maximum (max |TE|)
Synchronous Ethernet (SyncE)	・ESMC/SSM: Generate, Decode, Transparent Transfer ・Wonder: analysis and generation: TIE, MTIE, TDEV (Real Time)

Delay Measurement

E1, T1, 1 GbE, 10 GbE Interface	・Round-trip delay (RTD) ・One-way delay (OWD) (GNSS function is required)
Ethernet PTP (1 GbE, 10 GbE)	・Floor delay packet population, ratio / percentage / number ・Asymmetric path delay ・End-to-end / peer-to-peer path delay mechanism ・Master-slave to slave-to-master latency ・PTP packet delay variation ・Time error (TE) : Maximum (max | TE |), Dynamic (dTE), Constant (cTE)

Ethernet / IP Test

8 Stream Generation	・Stream: send/receive address and bandwidth can be set individually ・Protocol: IPv4, IPv6 ・Frame: DIX, VLAN, multistage VLAN, CoS (DSCP/PCP), MPLS, jumbo frame, UDP/IP, DHCP, ARP
Statistics Display	・Number of frames, IP traffic, bit rate ・Top 10 VLAN, MAC, IPv4/IPv6 addresses ・QoS: latency, delay variation, loss ratio, SES, availability, out-of-sequence, duplication
BER Test, Pattern	・Traffic generation: continuation, burst, lamp, random ・PHY layer: RPAT, JPAT, SPAT, HFPAT, LFPAT, MFPAT, LCRPAT, SCRPAT ・Layer 2/4 PRBS: 2e11-1, 2e15-1, 2e20-1, 2e23-1, 2e31-1 ・Layer 2/4 PRBS: all inverted versions
Symmetric / Asymmetric RFC-2544	・Throughput ・Latency ・Loss ・Back-to-back ・System recovery
Symmetric / Asymmetric eSAM (Y.1564)	・Latency, delay variation, loss, availability ・8/4 service judgment (color display) ・CIR, EIR, max, throughput
Loopback	・L1 - L4 loopback mode ・Transmit/receive MAC / IP / Port ・VLAN, CoS (DSCP/PCP) ・Protocol

PDH / T. Carrier test

Interface	・T1 (ANSI T1.102) ・E1 (ITU-T G.703) ・E0/Co-Directional (ITU-T G.703)
Mode	・Terminal ・Monitor ・High Impedence ・Pass-through ・T1: Framed SF and ESF and unframed Generation/Analysis ・E1: Framed PCM-30 / 31 with/without CRC and Unframed signals ・T1/E1: Display and Edition: all fields, CAS, Pulse Masks, Events ・Channel map: Busy/Free, External Drop/Insert of 64 kb/s co-dir or datacom
Measurement	・BER ・Line / Freq ・Errors / Alarms ・G.821, G.826, M.2100 ・VF: tone generation / analysis ・Attenuation, Freq, Freq. deviation, Level, Peak codes
Synchronization	・Jitter analysis: Peak to peak, RMS, hits, count (0.1 to 100 kHz range) ・Wander analysis / generation, mask (1 μHz to 10 Hz range) ・Wander analysis / generation 10 MHz, 2048 kHz, 1544 kHz, 1 pps

xGenius is a portable tester with a variety of frequency and phase clock reference outputs for versatile testing.

• 1PPS / ToD outputs, balanced or unbalanced: These outputs meet the ITU-T G.8271 specifications and may provide a performance level equivalent to a Primary Reference Time Clock (PRTC) as defined in ITU-T G.8272 when the test unit is properly configured.
• Frequency outputs, including 2048 kHz and 10 MHz interfaces. These outputs provide the same performance than a Primary Reference Clock as defined in ITU-T G.811 when the unit is properly configured.

Due to the high performance level provided by xGenius clock reference outputs, they are suitable to synchronize virtually any network. They have the advantage of being portable and battery operated. When the built in Rubidium oscillator is used they also provide good holdover performance. This function makes xGenius independent of GNSS when used as a portable synchronization source.

A typical application of clock reference outputs is to generate a stimulus to the device or network to be tested. This stimulus is propagated through the network and the result is analyzed in a second remote unit. Typical performance metrics are the Time Error (TE), Time Interval Error (TIE), Maximum TIE (MTIE) and Time DEViation (TDEV).

Clock reference outputs could also be used as a synchronization source for a second test equipment. This setup is typical of self-synchronized tests required for Boundary Clock (BC) or Transparent Clock (TC) benchmarking. The advantage of this setup is a very high accuracy level independent of any external element to the test system.

This document is mainly focused on phase and time applications delivered over packet switched networks and for this reason, only 1PPS / ToD and PTP tests are described in detail. However, frequency output clocks are still important in TDM applications and also in packet applications where only frequency distribution is relevant.

1. 1PPS Tests

This section deals about two basic test setups related with 1PPS interface tests. In one of them, 1PPS is used as a stimulus and GNSS provides time / phase reference. In the second configuration, 1PPS is used as a clock reference. The GNSS-synchronized test is suitable when the excitation signal is to be transmitted to a location far from the analysis interface. The self-synchronized test is very accurate but it requires the generator and the analyzer to be physically connected by a short patch cable.

There is actually a third basic setup that is not described here but it also has several important applications. It is a configuration in which a single unit generates a 1PPS / ToD output and at the same time runs 1PPS / ToD analysis test. This test has the same accuracy level than the dual-unit self-synchronized test.

Test Case I: GNSS-synchronized Test

Two xGenius units are required for this test. It is assumed that these units are configured to the factory defaults. The units may be installed in different locations potentially a long distance away one each other. Unit #1 generates a 1PPS stimulus signal that is transferred through a packet switched network. A second tester (unit #2) runs a TE / MTIE / TDEV test in some BC 1PPS monitoring output or at the 1PPS output provided by a PTP Slave Clock (SC).

Setting up the Reference

xGenius units may be equipped with a built-in GNSS receiver. These units have an SMA female connector suitable for connecting an antenna. Units with the built in GNSS receiver are also supplied with a compact antenna with 5 m of coaxial cable plus a 10m extension cable. Using a different antenna is possible as long as the specifications of the GNSS module are taken into account.

To use the built in GNSS module follow these steps in test unit #1 (generator) and #2 (analyzer) separately:

1. Attach the antenna to the unit. Make sure that the antenna sees as much of the sky as possible. The unit may fail to achieve synchronization if there are not enough satellites in range. Some tests may lose accuracy if the number of satellites in range is reduced.
2. From the Home panel, go to Config. The port setup panel is displayed.
3. Go to Reference clock.
4. Set Input clock to GNSS.
5. Press LEDS to display the test status.
6. Wait for the REF and LOCK LEDs to turn green.

Configuring GNSS Properties

1. From the Home panel, go to Config. The port setup panel is displayed.
2. Go to Reference clock.
3. Go to GNSS receiver.
4. Configure a compensation for the antenna cable through the Antenna delay correction field.
5. Enable or disable any of the GPS, GLONASS, Beidou or Galileo constellations through the Active GNSS setting.
6. Go to Fixed-position mode.
7. Adjust the Position averaging time and enable position averaging by configuring Fixed-position mode to Auto-average. The Fixed-position status field now displays Averaging.

8. Wait for the fixed position status to become Active. The unit is now ready for testing.

Connecting the Units

It is assumed that the input and output physical network interfaces are 1PPS unbalanced as defined in ITU-T Recommendations G.703 and G.8271.

For unit #1 the following configuration is required:

1. Connect the xGenius REF OUT port to the network input interface using a 50Ω coaxial cable.
2. From the Home panel, go to Config. The port configuration panel is displayed.
3. Go to Reference clock. The clock reference input and output configuration panel is displayed
4. Select PPS (REF SMB) in Output clock to start generating a 1 PPS output synchronized with the GNSS reference.

The configuration required in unit #2 is as follows:

1. Connect the xGenius PPS RX port to the network output interface using a 50 Ω coaxial cable.
2. From the Home panel, go to Config. The port configuration panel is displayed.
3. Select Mode to proceed to the mode selection menu.
4. Select the clock monitor.

Configuring the Test Port

Follow these steps for test unit #2:

1. Navigate to Config from the Home panel. The Port setting screen is displayed.
2. Select Port C to proceed to the mode selection menu.
3. Set Clock frequency to PPS (Port C).
4. Set the connector to Unbalanced and select 1PP1S (Port C) for Clock frequency.

Configuring the Test

Once the 1PPS clock interface is configured in unit #2, the user will need to select the tests to be performed. In this setup, TE / MTIE / TDEV are tested. The procedure to perform the test is as follows:

1. From the Home panel, go to Test. The test configuration panel is displayed.
2. Go to Wander test.
3. Enable the MTIE / TDEV test by setting the Enable control to On.
4. When testing with the output a PTP SC (Slave Clock), set Standard mask to PTP G.8271.1 Reference Point C. Use other suitable masks for different test requirements.

Running the Test

To start the test, press RUN on each test unit. The TE / MTIE / TDEV results are computed by test unit #2 in real time and can be checked at any point during the test using the following method:

1. From the Home panel, go to Results. The test port results panel is displayed.
2. Select Port C for port specific results.
3. Go to Wander test.
4. Choose between Wander analysis, MTIE or TDEV
5. Check results on their respective panels:
   • Wander analysis results: TE, Max. TE, Offset, Max. offset, Drift, Max. Drift
   • MTIE results: Time, TIE, MTIE and Mask results
   • TDEV results: Time, TDEV and Mask results

The test can be stopped at any point in time by pressing RUN again.

 

Test Case II: Self-synchronized Test

This test also uses two units. This time, the test signal is the PTP data flow transmitted via the Ethernet interface. The analytic signal is 1PPS as in Test Case I.

A simple configuration for PTP (1000BASE-T interface, no VLANs) is assumed. The PTP profile is assumed to be ITU-T G.8275.1 (L2 payload, multicast transmission...). The analysis interface is 1PPS/ToD balanced as defined in ITU-T Recommendations G.703 and G.8271. The initial state for both test units is the factory default configuration.

This test could be used to verify the performance of a PTP slave clock with a 1PPS/ToD output.

Setting up the Reference

1. Connect the unit #1 REF IN/OUT port to the REF IN/OUT port in unit #2 using a straight RJ-45 to RJ-45 cable.

2. In unit #1, from the Home panel, go to Config. The port configuration panel is displayed.
3. Select ToD (Port Ref. In/Out) in Output clock to start generating a 1PPS/ToD output synchronized to unit #2 local oscillator.
4. Go to PPS / ToD output interfaces.
5. Configure Output ToD protocol to ITU-T G.8271.
6. In unit #2, from the Home panel, go to Config. The port configuration panel is displayed.
7. Select ToD (Port Ref. In/Out) in Input clock to lock unit #2 with the 1PPS/ToD output generated by unit #1.
8. Go to PPS / ToD input interfaces.
9. Configure Input reference delay to compensate for the 1PPS cable delay. You should add 5 ns per meter of coaxial cable.
10. Press LEDS to display the test unit status.
11. Wait for the REF and LOCK LEDs to turn green.

Connecting the Units

For unit #1 the following configuration is required:

1. Connect the xGenius RJ-45 Port A to the network input interface using an Ethernet patch cable.
2. From the Home panel, go to Config. The port configuration panel is displayed.
3. Select mode to proceed to the mode selection menu.
4. Choose ethernet endpoint and confirm by pressing ENTER.

Follow the same procedure to connect unit #2 to the output interface.

Configuring PTP Master Emulation Mode

The following sequence is required for unit #1 to generate the PTP stimulus signal.

1. From the Home panel, go to Test. The test configuration panel is displayed.
2. Go to PTP (IEEE 1588).
3. Enable the PTP protocol in the unit by setting PTP mode to Emulation. A label indicating ‘PTP’ is displayed in the top notification area.
4. Configure the equipment to become an IEEE 1588 master by setting clock emulation to Master.
5. Configure the timing of the different messages associated with PTP from the Message timing menu.
6. Configure the Domain, Priority 1 and Priority 2 to the right values for your network.

If the previous settings are correct, an ‘M’ (Master) will be displayed near the “PTP” label.

Configuring the Test

Follow the procedure used in test case I to configure the test.

Running the Test

Follow the procedure used in test case I to run the test.

2. IEEE 1588 / PTP TESTS

This section describes three more test cases where generation of an output reference or test signal is necessary. Test case III describes a test that is closely related to test case I but both the 1PPS / ToD excitation and result signals are replaced by PTP flows transmitted over Ethernet interfaces.

Test case IV describes a self-synchronized test where the reference signal is transmitted over the same physical interface as the signal under test using Synchronous Ethernet. The advantage of this configuration is that the clock reference is readily available even if GNSS cannot be used and if the test units are far apart. The drawback is that it requires support of Synchronous Ethernet in the test network. Moreover, Synchronous Ethernet is a frequency technology. It is not designed to distribute time and phase information. As a result, the analysis unit cannot calculate the same result as when using a time clock reference (1PPS / ToD).

Test case V, a PTP self-synchronized test with 1PPS / ToD reference, has much in common with test case II but it replaces the 1PPS analysis interface with PTP. This configuration is ideal for BC and TC testing because it combines the high accuracy provided by the ToD reference with a packet test interface. While there is some inconvenience due to the requirement for a 1PSS / ToD link between test units #1 and #2, the test is able to measure all the available performance parameters, including TE.

In all three cases units are restored to the factory defaults before starting configuration. PTP profile is assumed to be ITU-T G.8275.1 (L2 payload, multicast transmission...). A simple configuration for all Ethernet test ports is also assumed (1000BASE-T, no VLANs).

 

Test Case III: Externally Synchronized Test

In this test case, unit #1 is configured to emulate a PTP master clock. The test signal is transmitted through a chain of network elements such as BCs or TCs. The output is the PTP data flow resulting from transmission of the original sequence over the test network. This is therefore a pure PTP test. Clock references are GNSS both in unit #1 and #2.

Setting up the Reference

Configure the GNSS references in unit #1 and #2 in the same way as described in test case I.

Configuring GNSS Properties

Configure the GNSS properties in unit #1 and #2 in the same way as described in test case I.

Connecting the Unit

Connect unit #1 and unit #2 to the input and output interfaces in the test network as follows:

1. Connect the xGenius RJ-45 Port A to the network input interface using an Ethernet patch cable.
2. From the Home panel, go to Config. The port configuration panel is displayed.
3. Select Mode to enter in the mode selection menu.
4. Choose Ethernet endpoint and confirm by pressing ENTER.

Configuring PTP Master Emulation Mode

Configure PTP master emulation mode for unit #1 in the same way as described in test case II.

Configuring the PTP Pseudo-slave Mode

In pseudo-slave emulation mode, unit #2 behaves as a PTP slave while keeping an independent synchronization source (GNSS, in this setup) that enables the unit to compute MTIE, TDEV, TE and other performance metrics based on the comparison of the test signal phase and frequency with the clock reference input (GNSS):

1. From the Home panel, go to Test. The test configuration panel is displayed.
2. Go to PTP (IEEE 1588).
3. Configure the unit to become an IEEE 1588 pseudo-slave by configuring PTP mode to Test. A label with the text PTP is displayed in the top notification area.
4. Configure the timing of the different messages associated to PTP from the Message timing menu.
5. Configure the Domain to the right value for your network.

If the previous settings are correct, the PTP indication in the top of the screen will change from yellow to green and the “S” indication will be displayed close to the “PTP” label.

Configuring the Test

Once the PTP is active the user still has to configure the tests to be run. In this setup these are the TE and MTIE / TDEV tests. No specific action is required to enable the TE test. To enable the MTIE and TDEV test follow these steps:

1. From the Home panel, go to Test. The test configuration panel is displayed.
2. Go to PTP wander test.
3. Enable the MTIE / TDEV test by setting Enable control to On.
4. Configure standard mask to a mask suitable for your test requirements.

Running the Test

The test is now ready to start. Press RUN in the test unit to begin. Now the TE and MTIE / TDEV are computed in real time. Follow these steps to check the TE results:

1. From the Home panel, go to Results. The test port results panel is displayed.
2. Select Port A to enter in the port specific results.
3. Enter in PTP to display results about the PTP protocol.
4. Go to Time Error statistics to get the TE results.
5. Check the maximum and minimum values of Total, Constant and Dynamic TE and check that these are under the limits defined in ITU-T G.8271.1.

The MTIE / TDEV test is executed at the same time as the TE test. Real time results can be checked as follows:

1. From the Home panel, go to Results. The test port results panel is displayed.
2. Select Port A to enter in the port specific results.
3. Enter in PTP to display results about the PTP protocol.
4. Go to PTP wander test.
5. Choose between MTIE or TDEV.
6. Check the Time, TIE, MTIE and Mask results (MTIE results panel) or Time, TDEV and Mask results (TDEV results panel).

The TE and MTIE / TDEV tests can be stopped at any point in time by pressing RUN.

 

Case IV: SyncE Self-synchronized Test

Test case IV describes a test where the reference shares the same interface as the test signal. This reference travels from a unit configured in PTP master emulation mode to a unit configured in pseudo-slave mode. Propagating the reference in the opposite direction is also possible as long as the network supports this setup.

The test itself is similar to the test described in case III. The difference in this setup is the way the clock reference is generated and distributed.

Connecting the Unit

Connect units #1 and #2 to the test network in the same way as described in test case III.

Setting up the Reference

Configure test unit #1 as a Synchronous Ethernet master using the following procedure:

1. From the Home panel, go to Config. The port setup panel is displayed.
2. Enter in Port A to display this port specific settings.
3. Go to Physical layer.
4. Go to Autonegotiation.
5. Configure clock role to Master.

Configure unit #2 to use the Synchronous Ethernet network clock as a reference clock with the following procedure:

1. From the Home panel, go to Config. The port setup panel is displayed.
2. Enter Port A to display the port specific settings.
3. Go to Physical layer.
4. Go to Autonegotiation.
5. Configure clock role to Slave.
6. Go back to the main Config menu.
7. Go to Reference clock.
8. Configure Input clock to Ethernet (Port A).
9. Press LEDS to display the test unit status.
10. Wait for REF and LOCK LEDs to turn green.

Configuring PTP Master Emulation Mode

Configure PTP master emulation mode for unit #1 in the same way as described in test case II.

Configuring the PTP Pseudo-slave Mode

Configure PTP slave emulation mode for unit #2 in the same way as described in test case III.

Configuring the Test

Configure unit #2 in the same way as described in test case III (configuring a MTIE / TDEV test).

Running the Test

The test is now ready to start. Press RUN in the test unit to begin. Now the TE and MTIE / TDEV are computed in real time. Follow these steps to check the results:

1. From the Home panel, go to Results. The test port results panel is displayed.
2. Select Port A to enter in the port specific results.
3. Enter in PTP to display results about the PTP protocol.
4. Go to PTP wander test.
5. Choose between MTIE or TDEV.
6. Check the Time, TIE, MTIE and Mask results (MTIE results panel) or Time, TDEV and Mask results (TDEV results panel).

The TE and MTIE / TDEV tests can be stopped at any point in time by pressing RUN.

 

Case V: ToD Self-synchronized Test

In this test case, there are two xGenius units running in master emulation mode and in pseudo-slave mode, just as in test cases III and IV. Again, the difference in this setup is the way the clock reference is generated and distributed. Specifically, this test case adopts the same mechanism used in test case II: one unit is locked to the ToD reference generated from the second unit.

Connecting the Unit

Connect units #1 and #2 to the test network in the same way as described in test case III.

Setting up the Reference

Configure ToD clock reference input and output for unit #1 and #2 in the same way as described in test case II.

Configuring PTP Master Emulation Mode

Configure PTP master emulation mode for unit #1 in the same way as described in test case II.

Configuring the PTP Pseudo-slave Mode

Configure PTP slave emulation mode for unit #2 in the same way as described in test case III.

Configuring the Test

Configure unit #2 in the same way as described in test case III (configuring a MTIE / TDEV test).

Running the Test

Follow the procedure for running tests as described in test case I.

Although xGenius can support various clock tests, this section focuses on PTP measurement for G.8272/Y.1367 and G.8273.2/Y.1368.2.

A．G.8272/Y.1367：PTP Grandmaster Conformance Test

In this test, a conformance test (MTIE/TDEV) of PRTC (Primary Reference Clock ≒ PTP Grandmaster) is performed using xGenius.

Test target (DUT): Grandmaster Qg2 OCXO built-in oscillator PRTC-A *

* PRTC currently has two grades, PRTC-A/B. Verification is performed with a PRTC-A standard DUT. PRTC-B requires higher precision specifications than PRTC-A (see Figure 1 and Figure 2).

Figure 1	Figure 2

Overview

Directly connect xGenius to the grandmaster, and measure the MTIE (Maximum Time Interval Error) and TDEV (Time Deviation) between them. xGenius is set to PTP Slave Test mode at this point.

As shown in the figure below, there are three connections for the grand master and two for xGenius.

The following verification parameters are selected for the PTP system.

Profile	IEEE 1588v2
Frame Composition	UDP
Addressing Mode	Unicast
Path Delay	End to End
ToD Format	NEMA
PTP Media Interface	1000Base-T

Results

As values are within the standard range shown in Fig. 1 and Fig. 2 above, the test confirms that the grandmaster (Qg2) satisfies this specification. (The graphs shown below were created by processing a file generated from xGenius’s report/log function using an Excel macro designed by our company. This macro is freely distributed upon request to customers who purchase the xGenius.)

B．G.8273.2/Y.1368.2：Boundary Clock Conformance Test

The following ITU-T G.8273.2 T-BC (Telecom Boundary Clock) conformance tests were performed using xGenius. Certification was conducted at constant temperature, which requires an ambient temperature deviation of ±1K.

Test Items

7.1 Maximum absolute time error	7.1.1 T-BC permissible range of constant time error
7.1.2 Dynamic time error low-pass filtered noise generation(MTIE) for T-BC(Constant Temperature)	7.1.2 Dynamic time error low-pass filtered noise generation(TDEV) for T-BC(Constant Temperature)
7.1.3 Dynamic time error high-pass filtered noise generation(dTEh)
Peak to Peak ±70ns

Test target (DUT): Quarra 10G PTP Ethernet Switch

* T-BC currently has four grades, T-BC Class A/B/C/D. This verification is performed using a T-BC Class A standard DUT.

Verification 1

The Quarra PTP Switch is connected to two xGenius units. xGenius unit A is equipped with a Rubidium oscillator and synchronizes with GNSS to emulate a PRTC-A standard PTP grandmaster.

xGenius unit B acts as a PTP slave and performs the above tests.

As shown in the figure below, xGenius A has 3 connections, the PTP Switch has 2 connections, and xGenius B has 2 connections.

The following verification parameters are selected for the PTP system.

Profile	IEEE 1588v2
Frame Composition	UDP
Addressing Mode	Multicast
Path Delay	End to End
ToD Format	NEMA
PTP Media Interface	10GBase-SR
Ambient Temperature	25.5 ~ 26.5 °C
PTP Message Timing	Announce TX interval : 1 Packet per Second Announce RX message time out: 3 second

Results (Verification 1)

As values obtained lie within the standard ranges across all categories, the test confirms that the target T-BC (Quarra Switch) satisfies this specification. (The graphs shown below were created by processing a file generated from xGenius’s report/log function using an Excel macro designed by our company. This macro is freely distributed upon request to customers who purchase the xGenius.)

---

Verification 2

The Quarra 10G PTP Switch is connected to two xGenius units. xGenius unit A has an OCXO oscillator and emulates a PRTC-A standard PTP grand master. However, unlike in Verification 1, the internal oscillator does not synchronize with GNSS.

xGenius unit B acts as a PTP slave and performs the same tests as in Verification 1.

As shown in the figure below, xGenius A has 2 connections, the PTP Switch has 2 connections, and xGenius B has 2 connections.

The following verification parameters were selected for the PTP system.。

Profile	IEEE 1588v2
Frame Composition	UDP
Addressing Mode	Unicast
Path Delay	End to End
ToD Interface	ITU G.8271 (xGenius間)
ToD Format	NEMA
PTP Media Interface	10GBase-SR
Ambient Temperature	25.4 ~ 26.4 °C
PTP Message Timing	Announce TX interval: Unicast Sync interval: Unicast Delay interval: Unicast Dlay Request interval: all 1 Packet per Second Announce RX message time out: 3 second

Results (Verification 2)

As shown below, all the criteria were satisfied as in Verification 1. Hence, the test confirms that using only the internal oscillator (OCXO) for self-synchronization is also effective. (The graphs shown below were created by processing a file generated from xGenius’s report/log function using an Excel macro designed by our company. This macro is freely distributed upon request to customers who purchase the xGenius.)