|This page describes the protocols related to negotiations between two principals within the system, brokered by the system.|
|Description||Negotiation between a Provider and a Consumer, facilitated by a Broker. The negotiation can originate from the Provider (invitation) or the Consumer (request) and exchanges Service Agreement Proposals until both parties accept or the negotiation is cancelled.|
|Conversation Roles||Provider, Consumer, Broker|
- All participants support the negotiation protocol.
- The system plays the role of negotiation broker in the absence of dedicated agents for provider and consumer
- A Service Agreement Proposal (SAP) is an object that represents an offer or counter-offer from a participant. Once mutually accepted, it becomes a contract.
- CIAD COI OV Negotiate Protocol - for negotations directly between Provider and Consumer
The protocols shown below involve three parties. The negotiation occurs between two principals within the system: the Provider and the Consumer. Their communication is brokered by the system, wit the Org that acts as delegate and intermediary.
The Brokered Negotiate Protocol has two variants. RPC style and Non-RPC style interactions. In ION Release 2, only RPC style interactions are possible and neither Provider nor Consumer have an active communication presence in the system. Therefore a queried (i.e. pull) style of negotiation was adopted (Variant 1, below).
|The protocols below only show the request case (originated from the Consumer), not the invitation case (originated from the Provider). The protocol does not show failed negotiations (timed out or cancelled).|
Figure 1. Negotiate protocol, three party (brokered) RPC (OV-6)
Figure 2. Negotiate protocol, three party (brokered) (OV-6)