Precheck of links to be turned off (criteria)

[openBackhaul]

Before a link is turned off, it needs to be checked, whether it is in a “good state”

• Good state:
  • both polarizations (RX, TX modulations) are working as planned
  • current and maximum modulation must match (planned values see APT/lifenetview)
  • turn off only if both are running at max modulation
• if one polarization is turned off and the other is already down or fails afterwards the link is not reachable remotely anymore, i.e.: cannot be turned on anymore!

[kmohr-soprasteria]

• RedundantTransmittersOff module needs to perform this check
• BasisLinkAnalysis module will try to collect necessary data for this check when called by RedundantTransmittersOff module for a given link

See description of BasisLinkAnalysis:

BasicLinkAnalysis • While activating the BasicLinkAnalysis module, the RedundantTransmittersOff or the AllTransmittersOn has to pass a Link-ID • BasicLinkAnalysis translates this link-ID into the uuid of an AirLayer connection; determines mount names, UUIDs, local IDs of the AirInterface that terminate the AirLayer connection • Analyzes if there is a parallel AirLayer connection; determines this one’s IDs as well (mount-names, uuids, local-IDS (of AirIf)) • Reads transmittersIsOn, transmissionModeMax, transmissionModeCur for parallel AirLayer connection • Returns info in responseBody; if data incomplete returns error instead

[openBackhaul]

The following proposals to be checked and potentially be confirmed by BackOffice:

Both polarizations:

• both polarizations (RX, TX modulations) are working as planned
• turn off only if both are running at max modulation

Proposal 1: We are checking just the polarization that has to transport the traffic during power saving. The to be switched-off polarization shall not be checked. (Reduces number of requests.)

As planned:

• both polarizations (RX, TX modulations) are working as planned

Proposal 2: We are not comparing against planning data, because this would require an interface towards and at the planning tool. Instead we are just checking whether the polarization that has to transport the traffic is operating at the maximum (configuration, not hardware capability) modulation.

As planned:

• both polarizations (RX, TX modulations) are working as planned

Proposal 3: RX level and TX power could only be compared against planning data, which would be difficult to obtain. Instead we are focusing on the modulation.

Modulations:

• current and maximum modulation must match (planned values see APT/lifenetview)

This would be covered.

Danger of switching both polarizations off:

• if one polarization is turned off and the other is already down or fails afterwards the link is not reachable remotely anmore, i.e.: cannot be turned on anymore!

Proposal 4: Ignore ideas of Master and Slave just follow a list an check whether there is a parallel link that is operating at its maximum modulation. If this condition is given, switch the link (not the parallel link) off.