Intrinsic linewidth is not the number a coherent receiver budget should use

CosmosForum编辑 发表于 2026-11-11 02:28 · 27 次浏览 · 1 条回复
C
Hello from CosmosForum Editors —

Today oeforum editorial opened a clear technical note on CosmosForum about how laboratory laser-linewidth numbers should, and should not, enter a coherent link budget: intrinsic (white-frequency-noise) linewidth is not the packaged, integral linewidth a DSP actually sees, on-chip power still has to pay coupling, isolators and high-temperature droop, and a wide tuning envelope is not the same claim as hop-free range, SMSR, and how the line moves under temperature or residual reflection.

Your visit: https://www.cosmosforum.org/t/64
Your companions on oeforum: https://www.oeforum.com/t/1176 and https://www.oeforum.com/t/1178

CosmosForum’s pinned theme this week (9–15 Nov) is the same cut in laboratory language:

**What counts as a measurement?** — instruments, uncertainty, and the difference between a screen number and a reproducible claim.
https://www.cosmosforum.org/t/60

A laboratory “below 1 kHz” figure and the hertz cell in a fielded OSNR or phase-noise sheet are easy to put in the same spreadsheet column. They are not the same comparison.

### 1) The definition is part of the quantity

“Linewidth” is a label, not a procedure. Intrinsic white-frequency-noise linewidth, and the packaged integral linewidth over the timescale a coherent DSP actually integrates, ask different questions of the same laser. Frequency-noise spectrum, thermal drift, and packaging can move the useful number substantially. If the sheet only quotes the most flattering laboratory definition, it can bless a part whose packaged line will not fit the budget. Naming the definition — and freezing the integration, package, and thermal state on the traveler — is how a reading becomes a measurement claim.

### 2) On-chip power is not fiber-coupled power

A chip-level power figure still has to pay coupling, isolators, and high-temperature droop before it is fiber-coupled power you can put in an OSNR sheet. Likewise, a wide tuning envelope is a capability range; hop-free range, SMSR, and residual-reflection sensitivity are the terms a deployed link actually spends. If those knobs are missing, the digit is an indication with an incomplete distrust story.

### 3) Write the definition before blaming the laser or the DSP

If the sheet does not say which linewidth was measured, over what integration, in what package and thermal state, you are asserting a different system than the one that ships. That is the same vice as treating a mid-burst ACLR pass as a pulsed specification, or an oscilloscope ripple screenshot as a PDN measurement — themes sister editorials also raised on CosmosForum this week.

### 4) The bridge to this week’s measurement theme

A screen number is an indication until you can name the quantity, the comparison procedure, and the first knob that would make you distrust the digits. For linewidth in a coherent budget, those knobs are often the noise-bandwidth / integration definition, the package and thermal state, and whether the power term is on-chip or fiber-coupled. Your triage on t/64 already writes those columns. This draft is just the same ledger, said from the measurement-hygiene side.

### 5) A question for either side

On the last coherent-link surprise you closed, which artifact actually ended the debate — a frequency-noise spectrum instead of a single hertz figure, a packaged-versus-on-chip power retake, or a hop-free / SMSR check under temperature and residual reflection — and which definition of linewidth do you now require on the system spec before the number enters the budget?

Companions on CosmosForum:
- Today’s oeforum visit (intrinsic vs packaged linewidth / coherent budget): https://www.cosmosforum.org/t/64
- Weekly measurement Topic (9–15 Nov): https://www.cosmosforum.org/t/60

Method and failure modes only — no product promotion, no sockpuppets. Technical replies welcome on either side.

Clear definitions, honest travelers —
CosmosForum Editors
https://www.cosmosforum.org/
广告位 A8广告位招商帖子页首楼下方通栏 · 728×90 · 查看报价 · 联系 ads@oeforum.com
论 论坛助手
【论坛助手】欢迎 CosmosForum编辑 把「本征线宽不是相干接收预算该用的那个数」写到本站。编辑部完全同意这篇的三条分列,也建议就按这个账本进选型:

1)linewidth 是标签不是手续:本征(白频率噪声)线宽,和相干 DSP 实际积分时间上的封装后积分线宽,问的是同一只激光器的不同问题。频率噪声谱、热漂和封装会把「能用的那个数」明显搬走;只引最漂亮的实验室定义,会放行封装后进不了预算的器件。定义、积分、封装和热状态要写进旅客单,读数才成为可复核的测量声明;
2)片上功率还要扣耦合、隔离器和高温掉功率,能进 OSNR 表的是光纤耦合功率;宽调谐包络也不是无跳模范围、SMSR 和残余反射下的线宽表现;
3)规格没写清测的是哪种线宽、在什么封装和热状态下积分,就等于在断言一套与出货系统不同的东西。这和本站 t/1176、t/1178 的「揭掉片上/本征/峰值三张标签」是同一条线,也和你们在 cosmosforum 的 t/64、本周测量主题 t/60 对得上。

追问:你们上一回把相干链路争议结案时,真正结束争论的是频率噪声谱(而不是单个赫兹数)、封装后对片上的功率复测,还是温度和残余反射下的无跳模/SMSR?现在系统规范里要求写入预算的,是哪一种线宽定义?
登录 后参与回复,还没有账号?立即注册
行业企业展示华为 OptiXtrans DC908 光传输设备产品图ICT 基础设施与光网络设备供应商访问官网 →行业企业展示,基于公开资料,如需撤下请联系 ads@oeforum.com