The CLAMP Control Loop Participant protocol is an asynchronous protocol that is used by the CLAMP runtime to coordinate life cycle management of Control Loop instances. The protocol supports the functions described in the sections below.

Protocol Dialogues

The protocol supports the dialogues described below.

Participant Registration and De-Registration

Registration when a participant comes up and update of participant with control loop type information and common parameter values for its control loop types.

...

@startuml
Participant -> CLAMP_Runtime: Participant Deregistration
Participant <- CLAMP_Runtime: Participant Deregistration Ack

Control Loop Commissioning and Decommissioning

When a control loop is commissioned, the portion of the Control Loop Type Definition and Common Property values for the participants of each participant type mentioned in the Control Loop Definition are sent to the participants.

...

@startuml
Commissioning_REST -> CLAMP_Runtime: Commission Control Loop
loop over Participant Types in Control Loop Type Definition
	CLAMP_Runtime -> CLAMP_Runtime: Collect Control Loop Element Type Definitions and\nCommon Property Values for\nParticipant Type
end
Participant <- CLAMP_Runtime: Participant Update [Remove Control Loop Element Type Definitions and Common Property Values for Participant Types]
Participant -> CLAMP_Runtime: Participant Update Ack [from each Participant mentioned in Participant Update message]

Control Loop Update

Update of control loops on participants (create/upgrade/downgrade/delete) following semantic versioning approach following these semantics: TOSCA Defined Control Loop: Architecture and Design

Control Loop State Change

UNINITIALIZED<->PASSIVE<->ACTIVE

Control Loop Monitoring and Reporting

Monitoring and statistics reported regularly by participants for their control loops.

Messages

Participant Registration

Participant Registration Ack

Participant Update

Participant Update Ack

Participant Deregistration

Participant Deregistration Ack

...