Skip to end of metadata
Go to start of metadata
This page describes the protocols related to negotiations between two principals within the system, brokered by the system.
Protocol Brokered Negotiate
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

Prerequisites

  • 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.

See Also:

Protocol

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).

Variant 1: Brokered Three-Party Negotiate, RPC Style

Figure 1. Negotiate protocol, three party (brokered) RPC (OV-6)

Variant 2: Brokered Three-Party Negotiate

Figure 2. Negotiate protocol, three party (brokered) (OV-6)

Labels

interaction-protocol interaction-protocol Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.