qalgora-Q Docs Hub量子文档 ✦ Ask AI✦ 问问文档
/

Real-Time Messaging Protocol Overview

○ Planned · Not yet implemented
The capabilities described on this page are planned and not yet implemented or released. They explain future design directions and should not be interpreted as delivered features.

The real-time stack speaks a compact RPC protocol so a classical controller can dispatch kernels and read results within the qubits' coherence window.

Overview only
This page is only a protocol-design overview; it is not a stable binary ABI specification.

RPC message layout

FieldMeaning
Request IDCorrelates a response with its request
Function IDSelects the device-side handler to run
PTP timestampPrecision-time-protocol stamp for latency accounting
Schema + payloadTyped arguments, bit-packed for the wire
Not yet fixed
The following are left unspecified and are not fixed by this overview: byte order (endianness), Request ID bit width, Function ID registration, Schema encoding, payload alignment, error codes, protocol version negotiation, security/authentication, and PTP timestamp units.

Payload encoding

  • Single-argument — the value is packed directly after the header.
  • Multi-argument — a schema descriptor lists field types and offsets.
  • Bit-packed measurements — multi-bit results are encoded compactly for QEC.

A QEC decode round

# device-side handler receives syndrome bits, returns a correction
def decode_handler(syndrome_bits):
    correction = decoder.decode(syndrome_bits)
    return correction            # sent back in the RPC response
Pauli frame
Real-time systems typically update a Pauli frame rather than physically applying every correction gate each round.
Why a wire protocol
Real-time QEC needs decode-and-correct to finish before decoherence. A lean, schema-driven binary protocol keeps the round-trip inside the latency budget.

实时消息协议概览

○ 规划中
本页所述能力属于规划功能，当前尚未发布或尚未实现。相关内容仅用于说明未来设计方向，不应理解为已交付能力。

实时栈采用紧凑 RPC 协议，使经典控制器能在量子比特相干窗口内完成内核调度与结果读取。

仅为概览
本页仅为协议设计概览，不是稳定的二进制 ABI 规范。

RPC 消息结构

字段含义
Request ID将响应与对应请求关联
Function ID选择设备侧待执行的处理函数
PTP timestamp精确时间协议时间戳，用于延迟统计
Schema + payload带类型的参数，按线缆格式进行位压缩
尚未固定
本概览未固定以下内容：字节序、Request ID 位宽、Function ID 注册、Schema 编码、payload 对齐、错误码、协议 version 协商、安全认证，以及 PTP timestamp 单位。

载荷编码

  • 单参数——数值直接紧跟在头部之后打包。
  • 多参数——由模式描述符列出各字段类型与偏移量。
  • 位压缩测量值——多比特结果紧凑编码，专为 QEC 设计。

一轮 QEC 解码

# device-side handler receives syndrome bits, returns a correction
def decode_handler(syndrome_bits):
    correction = decoder.decode(syndrome_bits)
    return correction            # sent back in the RPC response
Pauli frame
实时系统通常更新 Pauli frame，而非每轮物理施加所有纠正门。
为何需要线缆协议
实时 QEC 要求解码与纠错必须在退相干发生前完成。精简的模式驱动二进制协议能将往返延迟控制在预算之内。