Uploaded image for project: 'transportpce'
  1. transportpce
  2. TRNSPRTPCE-93

End-to-end path OSNR

    XMLWordPrintable

Details

    • Improvement
    • Status: Verified
    • Medium
    • Resolution: Done
    • None
    • None
    • None
    • None

    Description

      Currently, the OSNR contribution per (ROADM-to-ROADM) link is calculated in PceLink.java. But as far as I can see there is no summing up of link OSNR contributions in order to calculate the OSNR for an end-to-end path. Is this something that is planned for implementation? Calculating path OSNR and comparing with some threshold for path validation (similar to what is currently done for max latency) seems to me like the main point of having OSNR "awareness".

      There is a confusingly named parameter, maxOSNR, in PceConstraints.java but this parameter does not seem to be used anywhere. It is a bit confusing that both the maxOSNR parameter and the linkOsnrLu parameter returned by retrieveOSNR() actually seem to be inverse OSNRs (especially confusing is the debug message, "In retrieveOSNR: link OSNR is {} dB", when what is reported is not the OSNR in dB but the inverse OSNR in linear units).

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            atriki Ahmed Triki
            ojnas Jonas Mårtensson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 weeks
                2w