Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Absolute path in grouping power-param #155

Closed
Tracked by #144
italobusi opened this issue Oct 4, 2023 · 4 comments · Fixed by #160
Closed
Tracked by #144

Absolute path in grouping power-param #155

italobusi opened this issue Oct 4, 2023 · 4 comments · Fixed by #160

Comments

@italobusi
Copy link
Member

The absolute path in the grouping power-param are incorrect since there is no indication of which network instance to check

However, the grouping is used in difference places and the relative paths to reach the equalization-mode in the OMS-attributes are different ...

  grouping power-param {
    description
      "optical power or PSD after the ROADM or after the out-voa";
    choice power-param {
      description
        "select the mode: channel power or power spectral density";
      case channel-power {
        when "/nw:networks/nw:network/nt:link/tet:te
            /tet:te-link-attributes/OMS-attributes
            /equalization-mode='carrier-power'";
        leaf nominal-carrier-power{
          type l0-types:power-in-dbm-or-null;
          description
            " Reference channel power. Same grouping is used for the
            OMS power after the ROADM (input of the OMS) or after the
            out-voa of each amplifier. ";
        }
      }
      case power-spectral-density{
        when "/nw:networks/nw:network/nt:link/tet:te
            /tet:te-link-attributes/OMS-attributes
            /equalization-mode='power-spectral-density'";
        leaf nominal-power-spectral-density{
          type l0-types:decimal-16-digits-or-null;
          units W/Hz ;
          description
            " Reference power spectral density after 
              the ROADM or after the out-voa.
              Typical value : 3.9 E-14, resolution 0.1nW/MHz";
        }
      }
    }
  }

@italobusi
Copy link
Member Author

italobusi commented Oct 12, 2023

Italo/Sergio

This is our understand of where/how the powar-param choice is used at the output of the ROADM or at the output of the out-voa:

    +--ro OMS-attributes
       +--ro generalized-snr?                        l0-types:snr
       +--ro equalization-mode?                      identityref
       +--ro (power-param)?      // power-param after the ROADM
       ..................................................................
       +--ro OMS-elements!
          +--ro OMS-element* [elt-index]
             +--ro elt-index                 uint16
             ............................................................
             +--ro (element)
                +--:(amplifier)
                |  ......................................................
                |  +--ro amplifier
                |     ...................................................
                |     +--ro operational
                |        +--ro amplifier-element* []
                |           .............................................
                |           +--ro (power-param)?      // power-param after the out-voa
                |           .............................................

In the current YANG model, the equalization-mode is defined under the OMS-attributes and therefore the powar-param choices at the output of the ROADM and at the output of all out-voas within the same OMS MCG (reported as amplifiers within the OMS-element list) must be consistent

Is this correct?

@EstherLerouzic
Copy link
Collaborator

The power-param grouping used in the amplifier is not meant to have an equalization purpose: it is just a target power information for the amplifier instance (complementary to the gain target). The fact that it is reused from equalization leads to the confusion, and my suggestion would be to have two different grouping for these powers then:
one for and equalization targets, one for the target powers of amplifier. (and maybe change the naming to avoid any confusion ?)

italobusi added a commit that referenced this issue Nov 14, 2023
- Removed grouping power-param and copied attributes when used: fix #155
- Updated data type for delta-power attribute: fix #158
- Removed grouping sliceable-transponder-attributes: fix #159

---

Co-authored-by: sergio belotti <sergio.belotti@nokia.com>
@italobusi
Copy link
Member Author

@EstherLerouzic : is reporting the power-param optional or mandatory for optical impairments applications?

In the current YANG model it is optional: if needed, we can update the proposal in draft PR #160

Co-authored-by: sergio belotti sergio.belotti@nokia.com

@EstherLerouzic
Copy link
Collaborator

I think that power-params in amplifiers should be mandatory. Indeed if we only rely on an input power at the OMS and successive gain and loss along the elements, we may have a larger error at the end of propagation than having the power at each amplifiers (error is not propagated).

sergiobelotti added a commit that referenced this issue Nov 23, 2023
Related to issue#134 and #155 , power-params in amplifiers should be mandatory, and shorten power-spectral-density in power-psd
italobusi added a commit that referenced this issue Jan 23, 2024
* YANG updates for WG LC preparation:

- Removed grouping power-param and copied attributes when used: fix #155
- Updated data type for delta-power attribute: fix #158
- Removed grouping sliceable-transponder-attributes: fix #159
- Shortened powtypes and attribute names: fix #134 
  - power-spectral-density -> psd
  - power-spectral-density-or-null -> psd-or-null
  - power-in-dbm -> power-dbm
  - power-in-dbm-or-null -> power-dbm-or-null
  - decimal-2-digits -> decimal-2
  - decimal-2-digits-or-null -> decimal-2-or-null
  - decimal-5-digits -> decimal-5
  - decimal-5-digits-or-null -> decimal-5-or-null
  - ratio-in-db -> power-ratio
  - ratio-in-db-or-null -> power-ratio-or-null
  - gain-in-db -> power-gain
  - gain-in-db-or-null -> power-gain-or-null
  - loss-in-db -> power-loss
  - loss-in-db-or-null -> power-loss-or-null

- Added YANG model for DGE: see #153
  - added new stage-order attribute to amplifier-element
  - added new type-variety attribute to amplifier-element 
  - added amplifier-element-type choice ot amplifier-element
  - moved actual-gain, in-voa, out-voa, tilt-target, total-output-power, raman-direction and raman-pump under the optical-amplifier container
  - marked in-voa and out-voa as optional
  - moved media-channel-groups under the dynamic-gain-equalyzer container

---

Co-authored-by: sergio belotti <sergio.belotti@nokia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants