Open openBackhaul opened 1 year ago
An RPC based solution has been defined in the SchedulerProfile. It covers
Would it make sense to replicate this solution here?
Decision at the 5G-xhaul call on 15th of March 2023: The following changes shall be made to the UML modelling of the QosProfile:
An Interface of name QosProfileOperations shall be created.
An Operation of name createQosProfile shall be created. It shall NOT be idempotent, but create a new instance of QosProfile with every call. It shall be atomic. It shall have the following optional input parameter:
It shall have the following output parameter:
An Operation of name modifyQosProfile shall be created. It shall be idempotent It shall be atomic It shall have the following mandatory input parameter:
It shall have the following optional input parameters (if not provided, the configured values shall not be touched):
An Operation of name deleteQosProfile shall be created. It shall be idempotent. It shall be atomic. It shall have the following input parameter:
The existing modelling shall be changed in the following aspects:
UML changed as described above.
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: