label information at LTP to be harmonized with Holder

[openBackhaul]

If it would be decided not to add an instance to the name attribute at the Holder class for documenting the external label in Equipment Issue#15, it would make sense documenting the external label at the ControlConstruct and the LogicalTerminationPoint also as a separate attribute.

In this case...

• §27, §28 of the TransmitterEquipment 1.0.0-tsp.200715.1225 would have to be deleted
• ControlConstruct_Pac :: externalLabel : String [1] = "External label not yet defined." has to be added to the EquipmentAugment (Equipment Issue#20)
• LtpAugmentConfiguration :: externalLabel : String [1] = "External label not yet defined." has to be added to the LtpAugment

[openBackhaul]

Decision during the 5G-xhaul call on 1st of February 2023: In contrary to former considerations, there shall be no additional instance in the LogicalTerminationPoint::name list-attribute, but an explicit externalLabel attribute.

The following changes shall be made to the LtpAugment modelling:

• A LtpAugmentSpec class shall be added.
• An abstraction of type Specify shall be added and connect the new LtpAugmentSpec class with the existing LogicalTerminationPoint and contain the target "/CoreModel:ControlConstruct:ControlConstruct/CoreModel:LogicalTerminationPoint:LogicalTerminationPoint".
• A LtpAugment_Pac class shall be added.
• A composite association [1/1] shall connect from LtpAugmentSpec to LtpAugment_Pac.
• A LtpAugment_Pac :: externalLabel[1] : String = "External label not yet defined." attribute with comment "The externalLabel attribute is for the operator to persistently store an identifier from his documentation inside the device." shall be added.
• §27, §28 of the TransmitterEquipment 1.0.0-tsp.200715.1225 shall be deleted

[openBackhaul]

The LtpAugmentConfiguration and LtpAugmentCapability classes and further standard structure has to be removed from the current intermediate version of the modelling of the LtpAugment.