Connecting ODUs at Ethernet Interface

[openBackhaul]

As a part of the harmonization of an Ethernet based connection between IDU and ODU, the current practice of connecting IDU and ODU by IF cable shall be expanded on the Ethernet based interface.

Proposal to the LF ONMI x-haul call on 16th of October 2024:
(objected during call at 16th of October 2024)

• A new chapter 6.6 Connecting ODUs shall be added to the existing chapter 6 Special elements of the ONF TR-532 document.
• A new chapter 6.6.2 Ethernet Interface shall be added to the new chapter 6.6 Connecting ODUs .
• The following text shall be added to chapter 6.6.2 Ethernet Interface :
  "In case of a split-mount device that is applying Ethernet for connecting IDU and ODU, the relationship between IDU and ODU is documented according to the same concept.
  All Ethernet connectors at both the IDU and the ODUs need to be documented as instances of Connector.
  “Virtual” Holders are to be instantiated at the instance of Equipment, which is representing the switch board. Every existing Ethernet connector, which can connect an ODU, is to be represented by a “virtual” Holder. The values of the Holder::localId and the Connector::localId attributes must be identical for those instances of Holder.
  The connected ODU is to be referenced in the containedHolder::occupyingFru attribute of the instance of Holder, which is representing the Ethernet connector that is actually connecting the ODU.
  In addition to the LogicalTerminationPoints representing the radio connection, there are instances of LogicalTerminationPoint (WireInterface and PureEthernetStructure) for making the Ethernet PHY between IDU and ODU manageable.
  
  Figure 5: Simple (no 1+1 or 2+0) interface stack in case of Ethernet connection
  "

[openBackhaul]

Updated Proposal to the LF ONMI x-haul call on 23rd of October 2024:
(objected during call at 22th of October 2024)

• Please regard the dependency on EquipmentAugment issue#55 for creating an new Connector::vendorLabel attribute.
• A new chapter 6.6 Connecting ODUs shall be added to the existing chapter 6 Special elements of the ONF TR-532 document.
• A new chapter 6.6.2 Ethernet Interface shall be added to the new chapter 6.6 Connecting ODUs .
• The following text shall be added to chapter 6.6.2 Ethernet Interface :
  "In case of a split-mount device that is applying Ethernet for connecting IDU and ODU, the relationship between IDU and ODU is documented according to the same concept.
  All Ethernet connectors at both the IDU and the ODUs need to be documented as instances of Connector.
  “Virtual” Holders are to be instantiated at the instance of Equipment, which is representing the switch board. Every existing Ethernet connector, which can connect an ODU, is to be represented by a “virtual” Holder.
  The values of the Holder::vendorLabel and the Connector::vendorLabel attributes must be identical for those instances of Holder.
  The connected ODU is to be referenced in the containedHolder::occupyingFru attribute of the instance of Holder, which is representing the Ethernet connector that is actually connecting the ODU.
  In addition to the LogicalTerminationPoints representing the radio connection, there are instances of LogicalTerminationPoint (WireInterface and PureEthernetStructure) for making the Ethernet PHY between IDU and ODU manageable.
  
  Figure 5: Simple (no 1+1 or 2+0) interface stack in case of Ethernet connection
  "

[openBackhaul]

Decision at the LF ONMI x-haul call on 20th of November 2024:

• Please regard the dependencies on EquipmentAugment issue#56 and EquipmentAugment issue#57.
• A new chapter 6.6 Connecting ODUs shall be added to the existing chapter 6 Special elements of the ONF TR-532 document.
• A new chapter 6.6.2 Ethernet Interface shall be added to the new chapter 6.6 Connecting ODUs .
• The following text shall be added to chapter 6.6.2 Ethernet Interface :
  "In case of a split-mount device that is applying Ethernet for connecting IDU and ODU, the relationship between IDU and ODU is documented according to the same concept.
  All Ethernet connectors at both the IDU and the ODUs need to be documented as instances of Connector.
  “Virtual” Holders are to be instantiated at the instance of Equipment, which is able to connect ODUs (could be the IDU or the switch board in case of electrical, but could also be the SFP in case of optical interfaces). Every existing Ethernet connector, which can connect an ODU, is to be represented by an instance of “virtual” Holder beneath the same instance of Equipment. Such an instance of “virtual” Holder has to reference the instance of Connector that is representing the Ethernet connector able to connect the ODU in its _oduConnector attribute and the instance of Equipment representing the connected ODU in its _occupyingFru attribute.
  The _connectedOdu attribute at the instance of Connector representing the Ethernet connector, which is able to connect an ODU, has to reference the instance of “virtual” Holder that might reference an instance of Equipment representing a connected ODU in its _occupyingFru attribute.
  
  Figure 5: Simple example for connecting an ODU by SFP
  In addition to the LogicalTerminationPoints representing the radio connection, there are instances of LogicalTerminationPoint (WireInterface, PureEthernetStructure and EthernetContainer) for making the Ethernet connection between IDU and ODU manageable.
  
  Figure 6: Simple (no 1+1 or 2+0 configuration) interface stack in case of Ethernet connection
  "