AI/HPC Data Center & Cloud

Where the OCS lives — the data-center fabric. Large AI/HPC clusters still stitch thousands of GPUs together with electrical switch fabrics, doing an optical-to-electrical-to-optical conversion at every hop — power-hungry, and impossible to scale. A MEMS-based OCS from Triple-Stone replaces part of that electrical spine with a transparent optical layer: micro-mirrors steer each incoming fiber straight to an outgoing fiber, creating a direct end-to-end optical path with no OEO conversion and no store-and-forward.

In a Dragonfly topology the OCS sits at the spine, forming a full mesh with N+1 redundancy so pods join or leave the fabric on demand. Because the path is transparent to protocol and data rate, one physical fabric serves today's 400G/800G transceivers and tomorrow's upgrades — and re-provisions in milliseconds, controlled remotely via NETCONF, SNMPv3, TL1, Web GUI and REST API instead of re-patching fiber in the colo.

One fiber, both directions — circulator pairs. An OCS link should spend as little fiber as possible. Our planar and arrayed circulators let a single fiber carry both directions: the transmit and receive paths are split by port inside the circulator, and with high isolation plus low insertion loss, TX and RX share one fiber — saving fiber and patch-cord cost in a high-radix data-center fabric.

From discrete 3-port devices to arrayed integration, we cover the full circulator range an OCS link needs. The 8-in-1 arrayed circulator packs eight bidirectional paths into one high-density package — the standard companion for OCS ports. At the far end, a 2D optical fiber collimator array couples a high-port OCS into a compact grid, while fiber shuffle chassis re-map high-count links between the OCS and its line cards — all with batch-stable insertion loss and return loss.

OCS as test equipment — one switch, shared by every instrument. In a lab or on a production line, devices under test (DUT) and the instruments that measure them — light source, BERT, power meter, any instrument — are normally re-cabled by hand every time the test plan changes. Put a non-blocking OCS in between, and any instrument can be software-routed to any DUT on the opposite side: one OCS shared by every test station.

Instrument ports and DUT ports line up one to one, and the crossing paths are built and torn down in software, so the test topology is configured once and re-used across many devices. It is the same optical-switching core that drives a data-center fabric — here it switches test resources instead. Our OCS is developed fully in-house, including the core 2D FAU collimator arrays, so the any-to-any paths hold stable insertion loss and stay reliable as long-term test equipment.