PDF 原檔：報告_OCP2026_Google_OCS介面標準化_20261015_original.pdf
講者公開簡報（OCP 官方 Recorded Content 頁提供下載）。文字以 PyMuPDF 逐頁抽取，
### p<n>為頁碼；圖表內容見原檔。
圖片清單（已驗證 2026-10-19）
| 檔名 | 頁 | 分類 | 親眼所見內容 |
|---|---|---|---|
報告_OCP2026_Google_OCS介面標準化_20261015_p2.png |
p2 | 真資料圖 | OCS 定義與賣點：光輸入／輸出埠間可配置的純光路徑；技術含 Robotic、Beam Steering、Silicon Photonic；流量無關、免 OEO、低延遲、無收發器、耗電低於傳統電封包交換器 5%；右為四光纖經鏡面交叉的示意 |
報告_OCP2026_Google_OCS介面標準化_20261015_p4.png |
p4 | 真資料圖 | Building Common Interfaces：OCS 周圍六項管理面功能，藍色（為 OCS 修改）＝Forwarding Control、Configuration、Monitoring；灰色（原樣沿用）＝Installation、Security Management、Maintenance |
報告_OCP2026_Google_OCS介面標準化_20261015_p9.png |
p9 | 真資料圖 | OCS 基本操作的變體：Any-Any vs Some-Some 連線；快切（beam steering、SiPh）vs 慢（robotic）；主動維持 vs 被動維持鏈路；重開機後 Break／Recover／Maintain；未涵蓋 Multicast、Unidirectional；附 OCS 與機械手臂式交換示意 |
報告_OCP2026_Google_OCS介面標準化_20261015_p11.png |
p11 | 真資料圖 | 新增 ocs-port 元件 YANG 樹：enabled／alias／description／group／index、status（OFF、BLOCKED、FAILED、TUNING、TUNED、UNKNOWN）、input／output-optical-power-dbm、connection（peer、connected）、counters（correctable／total error count） |
報告_OCP2026_Google_OCS介面標準化_20261015_p14.png |
p14 | 真資料圖 | OCS Interface Spec v0.8：2026 年 9 月初向 OCS 工作組提出草案，GitHub 倉庫 ocp-net-optical-circuit-switching；核心貢獻者列 iPronics、Google、Lumentum、Huber+Suhner、Telescent 共 8 人 |
原始內容
p1
NETWORKING Richard Yu Staff Software Engineer - Google Brian O’Connor Staff Software Engineer - Google Developed in collaboration with the OCP OCS Working Group Standardizing OCS Interfaces for Seamless Integration
p2
Optical Circuit Switching (OCS) What is an OCS? Optical switch that provides configurable pure optical paths between optical input and output ports. Multiple technologies available: Robotic, Beam Steering, Silicon Photonic Why use OCS? Traffic-agnostic ● Compatible with current and future link speeds ● Compatible with any current and future protocols ● No Optical-Electrical-Optical Conversions ○ No choke points, queues, or buffers to overflow ○ Security: No traffic snooping Low latency ● Speed of light vs. ASIC switching latency Cost-effective ● No transceivers ● Lower power consumption (less than 5% compared to traditional electric packet switches) Fiber Fiber Fiber Fiber
p3
Building Common Interfaces Network Device Forwarding Control Configuration Monitoring Maintenance Security Management Installation
p4
Building Common Interfaces OCS Forwarding Control Configuration Monitoring Maintenance Security Management Installation Modified for OCS Reused As-Is
p5
Building Common Interfaces Forwarding Control Configuration Monitoring OpenConfig YANG Model components/ component/ state/ oper-status empty interfaces/ interface/ state/ qos/ state/ system/ state/ OCS
p6
Why OpenConfig YANG? OpenConfig YANG Model components/ component/ state/ oper-status empty interfaces/ interface/ state/ qos/ state/ system/ state/ ●Leverage existing support for non-OCS- specific telemetry and configuration ●Easier onboarding for operators ●Existing tools and support for vendors ●Established rules and guidelines ●Supports configuration and streaming telemetry
p7
Execution: gNMI
gNMI Operations
components/
component[
p8
Forwarding Control • Establish port-port connections Configuration • Configure connection restoration behavior • Discover device capabilities Monitoring • Monitor connection status • Monitor port health OCS Basic Operations Fiber Fiber Fiber Fiber
p9
• Establish port-port connections • Any-Any vs. Some-Some (E.g. A-B) • Monitor connection status • Fast switching (Beam steering, Si Photonics) • Slow technologies (Robotic) • Monitor port health • Actively maintained links (Beam steering, Si Photonics) • Passively maintained links (Robotic) • Configure connection restoration behavior • After reboot: Break, Recover, Maintain OCS Basic Operations - Variations Fiber Fiber Fiber Fiber Niche Features (Not fully covered) ● Multicast ● Unidirectional
p10
• New Top-Level Module for OCS configuration and advertisement Module: ocp-oc-optical-switch +--rw oc-optical-switch +--rw config | +-- rw bidirectional boolean | +-- rw cold-boot-recovery enumeration {MAINTAIN, REMAKE, REMOVE} +--ro state +-- ro bidirectional boolean +-- ro cold-boot-recovery enumeration {MAINTAIN, REMAKE, REMOVE} +-- ro cold-boot-recovery-capability enumeration {MAINTAIN, REMAKE, REMOVE} +-- ro port-groups [name] +-- ro name string +-- ro direction enumeration {INPUT, OUTPUT, ANY} +-- ro connection-groups* [peer-name] +-- ro peer-name string What’s New
p11
• New ocs-port component augment .../oc-platform:component: +--rw ocp-ocs-port +--rw config | +--rw enabled boolean | +--rw alias string | +--rw description string +--ro state +--ro enabled boolean +--ro alias string +--ro description string +--ro group leafref -> /ocp-oc-optical-switch:optical-switch/state/port-groups/name +--ro index uint32 +--ro status enumeration {OFF, BLOCKED, FAILED, TUNING, TUNED, UNKNOWN} +--ro input-optical-power-dbm uint32 +--ro output-optical-power-dbm uint32 +--ro connection [see callout] +--ro counters [see callout] What’s New +--ro connection +--ro peer leafref +--ro connected boolean +--ro counters +--ro correctable-error-count counter64 +--ro total-error-count counter64 +--ro counters +--ro correctable-error-count counter64 +--ro total-error-count counter64
p12
• Connection Management Module: oc-optical-switch-connections +--rw connections +--ro last-change-time yang:date-and-time +--rw port-connection* [name] +--ro name leafref -> ../config/name +--rw config | +--rw name string // arbitrary name selected by controller | +--rw input-port-name leafref -> /oc-platform:components/component/name | +--rw output-port-name leafref -> /oc-platform:components/component/name +--ro state +--ro name string +--ro input-port-name leafref -> /oc-platform:components/component/name +--ro output-port-name leafref -> /oc-platform:components/component/name +--ro status {CONNECTED, CONNECTING, DELETING, FAILED, INVALID} +--ro status-reason string +--ro last-updated yang:date-and-time What’s New
p13
• Free integration with extendable component hierarchies • Simultaneous visibility to: • Current active status [ocp-ocs-port] and • Intent [optical-switch-connections] • Leverage YANG modeling language constraints to enforce valid connection sets from gNMI front-end • Under investigation Schema Benefits chassis driver port port port sensor A
p14
OCS Interface Spec v0.8 https://github.com/opencomputeproject/ocp-net-optical-circuit-switching • Draft presented to OCS working group in early September • Spec is available on GitHub Core Contributors • Alvaro Tellez (iPronics) • Brian O'Connor (Google) • Iwan Kartawira (iPronics) • Marwan Abdul-Nour (Lumentum) • Michael DeMerchant (Lumentum) • Michael Enrico (Huber+Suhner) • Ramiro Voicu (Telescent) • Richard Yu (Google) Thanks for your contributions!
p15
• Establish a common API that covers most OCS capabilities • Join the OCP OCS working group • Project Site: https://www.opencompute.org/projects/optical-circuit-switching • Project Wiki: https://www.opencompute.org/wiki/Networking/Optical-Circuit-Switching • Project Mailing List: https://ocp-all.groups.io/g/ocp-optical-circuit-switching • Project Meetings: Wednesday, 9am PT • OCS Software Models: https://github.com/opencomputeproject/ocp-net-optical-circuit-switching • YANG / OpenConfig experts wanted! Call to Action
p16
Thank You!