top of page

Ucie Spec Jun 2026

UCIe leverages established standards such as PCI Express (PCIe) and Compute Express Link (CXL). It also supports "Streaming Protocols" for proprietary or specialized data types. Key Iterations of the UCIe Spec

This layer manages the link, ensuring reliable bit delivery via CRC (Cyclic Redundancy Check) and retry mechanisms.

| Standard | Max Rate | Range | Protocol | Open? | |----------|----------|-------|----------|-------| | | 64 GT/s | ≤25 mm | PCIe/CXL/Streaming | Yes (Royalty-free) | | BoW (Open Compute) | 16 GT/s | ≤10 mm | Raw | Yes | | AIB (Intel, deprecated) | 8 GT/s | ≤10 mm | Raw | Yes (but obsolete) | | XSR (Cadence) | 32 GT/s | ≤5 mm | Custom | No | | SerDes D2D | 56 GT/s (NRZ) | Long | Proprietary | No |

The UCIe specifications have evolved rapidly to meet massive data demands: Introduction to UCIe™ ucie spec

| Protocol | Use Case | |----------|-----------| | | Legacy I/O, GPUs, accelerators, SSDs | | CXL (v2.0/v3.0) | Cache-coherent memory expansion, memory pooling, accelerators | | Streaming | Raw data streams, non-coherent custom IP, streaming interfaces |

As Moore’s Law slows, chiplet-based disaggregated System-on-Chips (SoCs) offer the path to higher performance, yield, and reusability. UCIe provides the "glue" to mix compute, memory, I/O, and analog chiplets from multiple sources.

The story of is a tale of the semiconductor industry’s shift from massive, "monolithic" chips to a modular world of chiplets . The Problem: The "Reticle Limit" UCIe leverages established standards such as PCI Express

Documents available:

If you're looking for information on a specific musical piece, could you provide more details or clarify the title? That way, I can offer a more accurate and helpful response.

UCIe defines three (pinouts) for interoperability: | Standard | Max Rate | Range | Protocol | Open

UCIe Consortium (founded by AMD, Arm, Google, Intel, Meta, Microsoft, Qualcomm, Samsung, TSMC).

is an open industry standard for die-to-die (D2D) interconnect and serial bus. It defines the physical layer, protocol stack, and compliance rules to enable heterogeneous chiplets (from different vendors, fabs, and process nodes) to interoperate seamlessly within a single advanced package.

bottom of page