Instantiation

[openBackhaul]

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.

[openBackhaul]

An RPC based solution has been defined in the SchedulerProfile. It covers

• creating an instance
• modifying an existing instance
• deleting an instance

Would it make sense to replicate this solution here?

[demx8as6]

Decided during the 5G-xhaul call on 1st of March 2023: The following changes shall be made to the UML modelling of the PolicingProfile:

An Interface of name PolicingProfileOperations shall be created.

An Operation of name createPolicingProfile shall be created It shall NOT be idempotent, but create a new instance of PolicingProfile with every call. It shall be atomic. It shall base on the individual attributes as input (referencing an existing instance has been considered, but dropped). It shall have the following input parameters:

• externalLabel [0..1] with comment "Identifier of the instance of PolicingProfile. Could be a name, could be a number. Free text field to be filled by the operator."
• markerMode [1] with comment "Defines, whether potentially existing colloring shall be regarded, or not."
• policerKind [1] with comment "Defines the characteristics, which are used for determining the coloring of the packet."
• committedInformationRate [1] with comment "Committed Information Rate (CIR) in unit of kbit/s including IP but not Ethernet header information."
• committedBurstSize [1] with comment "Committed Burst Size (CBS) in unit of kByte."
• excessBurstSize [0..1] with comment "Only relevant if (policerKind==SINGLE_RATE_THREE_COLOR). Excess Burst Size (EBS) in unit of kByte."
• peakInformationRate [0..1] with comment "Only relevant if (policerKind==TWO_RATE_THREE_COLOR). Peak Information Rate (PIR) in unit of kbit/s."
• peakBurstSize [0..1] with comment "Only relevant if (policerKind==TWO_RATE_THREE_COLOR). Peak Burst Size (PBS) in unit of kByte."

It shall have the following output parameter: _createdPolicingProfile :: Profile [1] with comment "UUID of the instance of PolicingProfile that has been newly created."

An Operation of name modifyPolicingProfile shall be created It shall be idempotent. It shall be atomic. It shall have the following input parameters:

• externalLabel [0..1] with comment "Identifier of the instance of PolicingProfile. Could be a name, could be a number. Free text field to be filled by the operator."
• markerMode [0..1] with comment "Defines, whether potentially existing colloring shall be regarded, or not."
• policerKind [0..1] with comment "Defines the characteristics, which are used for determining the coloring of the packet."
• committedInformationRate [0..1] with comment "Committed Information Rate (CIR) in unit of kbit/s including IP but not Ethernet header information."
• committedBurstSize [0..1] with comment "Committed Burst Size (CBS) in unit of kByte."
• excessBurstSize [0..1] with comment "Only relevant if (policerKind==SINGLE_RATE_THREE_COLOR). Excess Burst Size (EBS) in unit of kByte."
• peakInformationRate [0..1] with comment "Only relevant if (policerKind==TWO_RATE_THREE_COLOR). Peak Information Rate (PIR) in unit of kbit/s."
• peakBurstSize [0..1] with comment "Only relevant if (policerKind==TWO_RATE_THREE_COLOR). Peak Burst Size (PBS) in unit of kByte."

An Operation of name deletePolicingProfile shall be created. It shall be idempotent It shall be atomic It shall have the following input parameter: _obsoletePolicingProfile :: Profile [1] with comment "UUID of the instance of PolicingProfile that shall be deleted."

The existing modelling shall be changed in the following aspects:

• PolicingProfile_Pac::_PolicingConfiguration shall change from read/write to read-only
• PolicingProfileConfiguration::externalLabel and all other attributes of the PolicingConfiguration class shall change from read/write to read-only

[openBackhaul]

Changed as described above in the UML.