Architecture for Control Networks: Difference between revisions

Revision as of 12:51, 17 August 2014

Revision as of 12:09, 30 August 2014

Line 13:

===Common Architecture===

The common architecture specifcationspecification defines a format of nested ''Protocol Data Units'' (''PDU''s), rather similar to [[Type-length-value|TLV]] encoding, which are used in the main protocols. It then defines how a minimal Root Layer Protocol is used to splice the higher level protocols into a lower level transport and defines such a Root Layer Protocol using the PDU format for use on [[User Datagram Protocol|UDP/IP]].

===SDT (Session Data Transport)===

SDT is a [[reliable multicast]] transport protocol which operates over [[User Datagram Protocol|UDP/IP]] which can be used to group peers within a network into ''sessions'' and deliver messages to them individually or as a group. Messages delivery is ordered and messages may be selectively sent [[Reliability (computer networking)|reliably or unreliably]] on a message-by-message basis (reliability is very important for some data while avoiding the time and resource overhead of the reliabiltyreliability mechanism is beneficial for others). The reliabiltyreliability mechanism also provides online status so a component will detect when a connection is broken. SDT provides a high degree of fine tuning over the trade-off between latency, reiability levels and resource requirements and availability of large numbers of concurrent sessions means they are a powerful tool for grouping and managing components whose functions are related or whose communication requirements are similar.

===DMP (Device Management Protocol)===