Closed openBackhaul closed 3 months ago
An RPC based solution has been defined in the SchedulerProfile. It covers
Would it make sense to replicate this solution here?
Decision during the 5G-xhaul call on 22nd of March 2023: [Proposal to the 5G-xhaul call on 15th of March 2023 has been rephrased in the section marked in bold and italic.].
The following changes shall be made to the UML modelling of the WredProfile:
An Interface of name WredProfileOperations shall be created.
An Operation of name createWredProfile shall be created. It shall NOT be idempotent, but create a new instance of WredProfile with every call. It shall be atomic. It shall have the following input parameters that must be provided with every call (attributes that are not supported by the device, will be ignored):
It shall have the following output parameter: _createdWredProfile :: Profile [1] with comment "UUID of the instance of WredProfile that has been newly created."
An Operation of name modifyWredProfile 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 deleteWredProfile 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.
Has been provided in WredProfile_1.0.0-tsi.240104.1945+yang
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: