openbackhaul / cochannelprofile Goto Github PK

Decision during the 5G-xhaul call on 22nd of February 2023:

• The CoChannelProfileConfiguration::profileName : string attribute shall be renamed to CoChannelProfileConfiguration::externalLabel : string for avoiding confusing it with the existing Profile::profileName attribute, which is for indicating the type of Profile.
• In addition the following comment shall be added: "Identifier of the instance of CoChannelProfile. Could be a name, could be a number. Free text field to be filled by the operator."

Decision during the 5G-xhaul call on 22nd of February 2023:

• The CoChannelProfileConfiguration::kindOfCoChannelGroup : kindOfCoChannelGroupType attribute shall be renamed to CoChannelProfileConfiguration::kindOfCoChannelProfile : kindOfCoChannelGroupType for harmonizing naming.
• The kindOfCoChannelGroupType datatype shall be renamed to kindOfCoChannelProfileType.

The latest UML2YANG tool will include mandatory substatement to attributes that has "Multiplicity 1 + no default values defined".
The following attributes which are formerly optional will be changed to mandatory in the upcoming YANG.

Further , if an attribute is decided to be optional , we shall handle it in the UML modelling by either introducing a default value or by modifying the Multiplicity to 0..1.

Common decision on 21.11.2019:

All *Notification::objectIdRef attributes will become _objectIdRef attributes generated from shared associations to LTP class in UML. This applies on all notifications.

All *notification::object-id-ref leaf will become leafref to LTP.

Only object-deletion-notification::object-id-ref : leafref will be "require-instance false;"

There is a problem in instantiating a Profile, if no instance that could be cloned would already exist.
Particularly, since the capabilities are attached to the instances of Profile.

Potential Solution:

• If not assured that there is always at least one instance of Profile, an RPC shall be defined.
• This RPC shall
  • either generate a default Profile, which can serve as a prototype for clones,
  • or create and edit actual instances of Profile.

Either ImplementationCommonDatatypes or IetfYangTypes to be use in UML. Types not been translated into String during UML2YANG translation, but to maintained with the initial names. YANG representation of ImplementationCommonDatatypes or IetfYangTypes to be generated and to be imported into YANG file of tech.spec. Interface/Profile yang.