tx_power for per service path requests introduced in Rel 2.10 does not currently have a convenient solution to be used on individual requests. I would like to propose a feature to add tx-min and tx-max values to the equip_config transceiver blocks.
path-request/request-id/tx_power should default to new tx-max value when present. (Note: There is no current use for tx-min but this is standard info that may be useful in the future?)
Below are Transceiver and path-request/request-id blocks with new values bolded:
"Transceiver":[
{
"type_variety": "Voyager",
"frequency":{
"min": 191.35e12,
"max": 196.1e12
},
"tx_power_dbm":{
"min": -9,
"max": 1
},
"mode":[
{
"format": "mode 1",
"baud_rate": 32e9,
"OSNR": 11,
"bit_rate": 100e9,
"roll_off": 0.15,
"tx_osnr": 40,
"min_spacing": 50e9,
"cost":1
},
{
"format": "mode 2",
"baud_rate": 66e9,
"OSNR": 15,
"bit_rate": 200e9,
"roll_off": 0.15,
"tx_osnr": 40,
"min_spacing": 75e9,
"cost":1
}
]
}
]
When the Transceiver tx_power_dbm-max is present the value should override the SI default then be converted to watts and placed in the existing tx_power field of the services path-request json as shown below:
"request-id": "0 with tx_power",
"source": "trx SITE1",
"destination": "trx SITE2",
"src-tp-id": "trx SITE1",
"dst-tp-id": "trx SITE2",
"bidirectional": false,
"path-constraints": {
"te-bandwidth": {
"technology": "flexi-grid",
"trx_type": "Voyager",
"trx_mode": "mode 1",
"tx_power": 0.00126,
"spacing": 50000000000.0,
"path_bandwidth": 100000000000.0
tx_power for per service path requests introduced in Rel 2.10 does not currently have a convenient solution to be used on individual requests. I would like to propose a feature to add tx-min and tx-max values to the equip_config transceiver blocks.
path-request/request-id/tx_power should default to new tx-max value when present. (Note: There is no current use for tx-min but this is standard info that may be useful in the future?)
Below are Transceiver and path-request/request-id blocks with new values bolded:
"Transceiver":[
{
"type_variety": "Voyager",
"frequency":{
"min": 191.35e12,
"max": 196.1e12
},
"tx_power_dbm":{
"min": -9,
"max": 1
},
"mode":[
{
"format": "mode 1",
"baud_rate": 32e9,
"OSNR": 11,
"bit_rate": 100e9,
"roll_off": 0.15,
"tx_osnr": 40,
"min_spacing": 50e9,
"cost":1
},
{
"format": "mode 2",
"baud_rate": 66e9,
"OSNR": 15,
"bit_rate": 200e9,
"roll_off": 0.15,
"tx_osnr": 40,
"min_spacing": 75e9,
"cost":1
}
]
}
]
When the Transceiver tx_power_dbm-max is present the value should override the SI default then be converted to watts and placed in the existing tx_power field of the services path-request json as shown below: