Documenting the Polarization

[openBackhaul]

Problem:
Formerly, there was one IF connector at the ODU.
Now, there might be two.
The virtual holder, which is defined in TR-532 as a workaround for documenting the connection to the ODU, references just Equipment (the ODU), but cannot distinguish the connectors at the ODU.
During discussions it has been found that the polarization of the transmitted signal is the actually important information.
The polarization is determined by the orientation of the ODU and the applied connector (if there is more than one).
Both can neither be configured at the device nor be reported at its management interface.
This lead to the idea of just documenting the polarization of the AirInterface and leave it to the field force technician to apply the correct combination of orientation of the ODU and connector.

Decision during the LF ONMI x-haul call on 4th of March 2026:
[Remark: This issue has been decided together with ltpAugment issue #10 and airInterface issue #68.]

• A PolarizationType enumeration shall be added to the AirInterface modelling.
  It shall define the following values:
  • HORIZONTAL
  • VERTICAL
  • NOT_YET_DEFINED
• An AirInterfaceConfiguration::polarization : PolarizationType = "NOT_YET_DEFINED" read/write attribute shall be added.
  It shall be equipped with the following comment: "Allows the operator to document the polarization of the AirInterface."