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]

Decision during the 5G-xhaul call on 11th of January 2023: The following changes shall be made to the UML modelling of the SchedulerProfile:

• An Interface of name SchedulerProfileOperations shall be created

.

• An Operation of name createSchedulerProfile shall be created
• It shall NOT be idempotent, but create a new instance of SchedulerProfile with every call
• It shall be atomic
• It shall have the following optional input parameter:
  • _baseSchedulerProfile :: Profile [0..1] with comment "If filled with an UUID of an existing instance of SchedulerProfile, the RPC shall create a duplicate of the existing instance."
• It shall have the following output parameter:
  • _createdSchedulerProfile :: Profile [1] with comment "UUID of the instance of SchedulerProfile that has been newly created."

.

• An Operation of name modifySchedulerProfile shall be created
• It shall be idempotent
• It shall be atomic
• It shall have the following input parameters:
  • _existingSchedulerProfile :: Profile [1] with comment "UUID of the instance of SchedulerProfile that shall be modified."
  • affectedQueueList :: QueueBehaviorType [1..8] with comment "List of queues that shall be subject to modifications. queueName to be used as key attribute for identifying the queue that shall be modified."

.

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

[openBackhaul]

UPDATE on an Additional Change: In accordance with the modelling in all other Profile definitions, the following changes have been made on the existing modelling:

• SchedulerProfile_Pac::_schedulerProfileConfiguration has been changed from read/write to read-only.
• SchedulerProfileConfiguration::queueBehaviorList has been changed from read/write to read-only.

[openBackhaul]

UML changed as described.