Content deleted Content added
m Remove erroneous reference to seventeen protocols |
Rearrange for better flow, update links and references and add newer developments. |
||
Line 1:
{{Refimprove|date=January 2012}}
'''Architecture for Control Networks''' ('''ACN''') is a suite of [[network protocol]]s for
ACN was
==Protocol architecture==▼
The breakdown of ACN into sub-protocols, Interoperability Profiles and other small pieces has been criticized as making ACN hard to read and understand but it makes the architecture highly modular and cleanly layered and this has allowed many of the pieces to be operated in other contexts or replaced or revised without changing the other pieces. For example, DMP has been operated over TCP as well as over SDT as defined in the initial standard, DDL has been adapted with little change to describe devices accessed by DMX512 or ANSI E1.31, and several Interoprability Profiles have seen major revision or replacement without disturbing the other parts of the standard.
▲==Protocol architecture==
===Common Architecture===
The common architecture specifcation 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]].
* Session Data Transport Protocol (SDT)▼
* Device Management Protocol (DMP)▼
* Device Description Language (DDL)▼
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 reliabilty mechanism is beneficial for others). The reliabilty 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.
==Interoperability profiles==▼
▲The ACN protocol may be further defined via interoperability profiles which will extend various layers of the ACN stack, or define how elements of the ACN architecture must be used in a particular situation to achieve interoperability. For example, by providing specific values for timing parameters to be used in a particular network environment.
DMP represents any device as a set of addressable properties which represent its current or desired state. Monitoring or control by a controller is achieved by setting or examining the values of those properties. To avoid the inefficiencies of polling, in addition to simply reading property values (using a ''Get-Property'' message) DMP provides a subscription mechanism whereby a device will asynchronously send event messages to all subscribed controllers when the value of a property changes.
DMP expects that its connections can provide reliability so that ''Set-Property'' and ''Event'' messages which form a large part of the operational bandwidth in a show situation do not require explicit acknowledgement at the DMP level. In the E1.17 standard and the majority of systems SDT provides this reliability but DMP has also been operated usng TCP to provide its reliable connections.
The size in bits, representation, read/write accessibility and function of each property in a DMP device is not determined by the protocol which only defines the mechanism to read and/or write the property value. Instead, that information must either be provided externally by a device description written in DDL or in limited cases may be pre-programmed by fore-knowledge of specific device types.
DDL allows a machine parseable description of the interface and capabilities of any device to be defined. This description can be interpreted by a controller which may then automatically configure itself for controlling that device. The description not only provides the address and property mapping information which is necessary for DMP to operate but it can also contain a huge amount of information on the functionality, capabilities and semantics of the device in an extensible format which allows a controller to extract the features it needs for its specific context while skipping over information which is not relevant to its needs.
DDL is an [[XML]] based language and descriptions are contained in a small number of [[XML]] documents. In normal ACN systems the description for a device may be downloaded from the device itelf. However, descriptions may also be distributed in other ways (such as internet download) and since a description is valid for all devices of the same type, controllers can typically maintain a cache of descriptions for devices they commonly encounter.
▲===Interoperability profiles===
'''Interoperability Profiles''' ('''EPI'''s) are provided in ANSI E1.17 for initial [[service discovery]] in a system; for allocation of [[multicast address]]es when used on UDP and [[IPv4]]; for [[Port_(computer_networking)|UDP port]] allocation when multicasting, for [[IP address]] assignment in conformant systems, for protocol timeouts in specific environments and so on. Other EPIs which conform to the ACN Architecture have been developed outside the ANSI E1.17 standard (see below).
==External Extensions==
Due to its modular nature ACN has been easy to extend.
A major protocol '''ANSI E1.31''' known as '''Streaming ACN''' or '''sACN''' was developed by the same organization and uses the Root Layer and PDU format of ACN to transport the data of [[DMX512]] data over IP networks (or any other ACN compatible transport).
A number of further Interoperability Profiles have been developed and standardized by PLASA. These include:
ANSI E1.30-3-2009 ''Time Reference in ACN Systems Using SNTP and NTP''
ANSI E1.30-4-2010 which defines how to use DDL to describe devices controlled using DMX512 or Streaming ACN
==Implementations==
E1.31 (Streaming DMX over ACN) is supported on [[Linux]] ([[ARM architecture|ARM]]; [[Intel 80386|i386]], [[x86-64]]), and [[Macintosh]] ([[PowerPC]]; i386, x86-64) by the Open Lighting Architecture.<ref>{{cite web |url=http://opendmx.net/index.php/OLA |title=Open Lighting Architecture |accessdate=2012-01-05}}</ref>▼
A more recent and much more complete implementation in C is 'Acacian'<ref>{{cite web |url=http://WWW.ACACIAN.ORG/ |title=Acacian |accessdate=2014-08-10}}</ref>, which includes more features and DDL support.
There is yet another open source ACN project<ref>{{cite web|url=http://acn.codeplex.com/|title=Architecture for Control Networks project home page|accessdate=5 October 2011}}</ref> on [[Codeplex]] which is implemented in C#. This aims to provide a full managed code implementation and includes code for several other related protocols.
▲E1.31 (Streaming DMX over ACN) is supported on [[Linux]] ([[ARM architecture|ARM]]; [[Intel 80386|i386]], [[x86-64]]), and [[Macintosh]] ([[PowerPC]]; i386, x86-64) by the Open Lighting Architecture.<ref>{{cite web |url=http://opendmx.net/index.php/OLA |title=Open Lighting Architecture |accessdate=2012-01-05}}</ref>
ACN has been implemented and deployed in proprietary implementations by a number of companies. Among others it is used by [[Electronic Theatre Controls]] as the basis of their networked control infrastructure branded as 'NET3' and is used by [[Shure]] Inc. in control of wireless microphones.
== See also ==
Line 45 ⟶ 70:
==External links==
* [http://www.esta.org/tsp/working_groups/CP/projs.html ESTA's Technical Standards Program]
| |||