Share via

3.2.2.1 Abstract Data Model

  • Article

This section describes a conceptual model of a possible data organization that an implementation might maintain to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this document.

A client maintains 3 sets of protocol variables:

  • A Client Virtual Connection: A Virtual Connection as described in the common protocol variables section 3.2.1.1.3.

  • A Client Out Channel: An out channel consisting of the data elements described in the Receiving Channel data elements, as described in the common protocol variables section 3.2.1.1.5.

  • A Client In Channel: An in channel consisting of the data elements described in the Sending Channel and Ping Originator in the common protocol variable section 3.2.1.1.4.

The client also maintains a set of client-specific ADM elements as described in the following section.