Open openBackhaul opened 2 years ago
An RPC based solution has been defined in the SchedulerProfile. It covers
Would it make sense to replicate this solution here?
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:
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:
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:
Changed as described above in the UML.
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: