Add Tx and Rx power range, and Rx power OSNR penalty

[EstherLerouzic]

(priority for ZR management)
Target:

• Account for tx_power range and tune tx power according to roadm constraints auomatically
• Account for Rx-power range: verifies that received power is within the range, if not apply a penalty (if defined) or unfeasible (infinite penalty)
• Manually forced tx_power still possible

Today:

• Currently possibility to manually tune this power (tx_power_dbm), but no automatic setting based on capability
• Currently no verification of receiver power

Use IETF data model naming

"mode": [{
"format": "100G", "baud_rate": 32.32e9, "OSNR": 13, … ,
"tx-channel-power-min": -3,
"tx-channel-power-max": 0,
"rx-channel-power-min": - 25, The minimum input power of this interface (not working at all below this)
"rx-channel-power-max": -10, (not working at all above this)
"rx-ref-channel-power": - 20.0, ( ref power used for all other penalties and min required OSNR) -> included in the penalty list
"penalties": [{« rx-channel-power-value": -21,0, "penalty_value": 0.5}, "Optional penalty associated with a received power lower than rx-ref-channel-power” can not contain power below rx-channel-power-min.

[EstherLerouzic]

Slides shared on the 26/11.

penalties.pdf

It was agreed that the penalties should rather been calculated as a SNR contribution rather than a addition on required OSNR, because of its dependency to received SNR.