Architecture for Control Networks

Last updated
Architecture for Control Networks
International standard ANSI Standard E1.17-2006

Architecture for Control Networks (ACN) is a suite of network protocols for control of entertainment technology equipment, particularly as used in live performance or large-scale installations. For example, lighting, audio or special effects equipment. ACN is maintained by Entertainment Services and Technology Association and its first official release was ANSI Standard E1.17-2006 - Entertainment Technology - Architecture for Control Networks. The standard was subsequently revised and released as ANSI E1.17-2010.

Contents

ACN was initially designed to be layered on top of UDP/IP and therefore will run over most IP transports including standard, inexpensive Ethernet and 802.11 (Wi-Fi) networks.

Protocol architecture

ACN defines a common protocol architecture, two major network protocols (SDT, DMP), a device description language (DDL) and a number of ‘E1.17 Profiles for Interoperability’ (known as EPIs or interoperability profiles ) which define how elements of the ACN architecture must be used in a particular context to achieve interoperability. For example, by providing specific values or ranges for timing parameters to be used in a particular network environment.

The breakdown of ACN into sub-protocols, interoperability profiles and other small pieces has been criticized[ by whom? ] 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 (ANSI E1.31/Streaming ACN), and several interoperability profiles have seen major revision or replacement without disturbing the other parts of the standard.

Common Architecture

The common architecture specification defines a format of nested protocol data units (PDUs), rather similar to 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 UDP/IP.

Session Data Transport

Session Data Transport (SDT) is a reliable multicast transport protocol which operates over UDP/IP which can be used to group peers within a network into sessions and deliver messages to them individually or as a group. Message delivery is ordered and messages may be selectively sent 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 reliability mechanism is beneficial for others). The reliability 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, reliability 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.

Device Management Protocol

Device Management Protocol (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 using 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.

Device Description Language

Device Description Language (DDL) allows a machine parsable description of the interface and capabilities of any device to be defined. [1] 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. [2]

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 itself. 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 (EPIs) are provided in ANSI E1.17 for initial service discovery in a system; for allocation of multicast addresses when used on UDP and IPv4; for 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

An early open-source implementation of ACN was released as OpenACN [3] and is available on SourceForge. This has been ported to a wide range of platforms, but it is limited in its scope and does not implement any DDL support.

There is another open source ACN project [4] which is implemented in C#. This aims to provide a full managed code implementation and includes code for several other related protocols.

An full implementation entitled Acacian [5] in C, which includes parsing of DDL descriptions to generate DMP structures was released under the Mozilla Public Licence in 2014

E1.31 (Streaming DMX over ACN) is supported on Linux (ARM, i386, x86-64) and Macintosh (PowerPC; i386, x86-64) by the Open Lighting Architecture. [6]

A Rust implementation of E1.31 can be found on GitHub. [7]

ACN has been deployed in proprietary implementations by a number of companies, including its use by Electronic Theatre Controls (ETC) as the basis of their 'NET3' branded networked control infrastructure and by Shure Inc. in control of wireless microphones.

See also

Related Research Articles

The Internet protocol suite, commonly known as TCP/IP, is the set of communications protocols used in the Internet and similar computer networks. The current foundational protocols in the suite are the Transmission Control Protocol (TCP) and the Internet Protocol (IP), as well as the User Datagram Protocol (UDP).

OSI model Model of communication of seven abstraction layers

The Open Systems Interconnection model is a conceptual model that describes the universal standard of communication functions of a telecommunication system or computing system, without any regard to the system's underlying internal technology and specific protocol suites. Therefore, the objective is the interoperability of all diverse communication systems containing standard communication protocols, through the encapsulation and de-encapsulation of data, for all networked communication. In the OSI reference model, the communications between a computing system are split into seven different abstraction layers: Physical, Data Link, Network, Transport, Session, Presentation, and Application.

The Session Initiation Protocol (SIP) is a signaling protocol used for initiating, maintaining, and terminating real-time sessions that include voice, video and messaging applications. SIP is used for signaling and controlling multimedia communication sessions in applications of Internet telephony for voice and video calls, in private IP telephone systems, in instant messaging over Internet Protocol (IP) networks as well as mobile phone calling over LTE (VoLTE).

Simple Network Management Protocol (SNMP) is an Internet Standard protocol for collecting and organizing information about managed devices on IP networks and for modifying that information to change device behaviour. Devices that typically support SNMP include cable modems, routers, switches, servers, workstations, printers, and more.

Universal Plug and Play (UPnP) is a set of networking protocols that permits networked devices, such as personal computers, printers, Internet gateways, Wi-Fi access points and mobile devices to seamlessly discover each other's presence on the network and establish functional network services. UPnP is intended primarily for residential networks without enterprise-class devices.

DMX512 Digital communication network standard for controlling stage lighting and effects

DMX512 is a standard for digital communication networks that are commonly used to control lighting and effects. It was originally intended as a standardized method for controlling stage lighting dimmers, which, prior to DMX512, had employed various incompatible proprietary protocols. It quickly became the primary method for linking controllers to dimmers and special effects devices such as fog machines and intelligent lights.

LonWorks or Local Operating Network is an open standard for networking platforms specifically created to address the needs of control applications. The platform is built on a protocol created by Echelon Corporation for networking devices over media such as twisted pair, powerlines, fibre optics, and RF. It is used for the automation of various functions within buildings such as lighting and HVAC; see building automation.

Modbus is a data communications protocol originally published by Modicon in 1979 for use with its programmable logic controllers (PLCs). Modbus has become a de facto standard communication protocol and is now a commonly available means of connecting industrial electronic devices.

BACnet is a communication protocol for Building Automation and Control (BAC) networks that leverage the ASHRAE, ANSI, and ISO 16484-5 standard protocol.

Lighting control console

A lighting control console is an electronic device used in theatrical lighting design to control multiple stage lights at once. They are used throughout the entertainment industry and are normally placed at the front of house (FOH) position or in a control booth.

Show control

Show control is the use of automation technology to link together and operate multiple entertainment control systems in a coordinated manner. It is distinguished from an entertainment control system, which is specific to a single theatrical department, system or effect, one which coordinates elements within a single entertainment discipline such as lighting, sound, video, rigging, or pyrotechnics. A typical entertainment control system would be a lighting control console. An example of show control would be linking a video segment with a number of lighting cues, or having a sound cue trigger animatronic movements, or all of these combined. Shows with or without live actors can almost invariably incorporate entertainment control technology and usually benefit from show control to operate these subsystems independently, simultaneously, or in rapid succession.

The EntertainmentServices &TechnologyAssociation (ESTA) is an American non-profit trade association that represents the entertainment technology industry and is dedicated to promoting professionalism and growth within it. It also provides a forum where interested parties can exchange ideas and information, create standards and recommend certain practices, and face problems in terms of training and certification.

Profinet

Profinet is an industry technical standard for data communication over Industrial Ethernet, designed for collecting data from, and controlling equipment in industrial systems, with a particular strength in delivering data under tight time constraints. The standard is maintained and supported by Profibus and Profinet International, an umbrella organization headquartered in Karlsruhe, Germany.

Remote Device Management (RDM) is a protocol enhancement to USITT DMX512 that allows bi-directional communication between a lighting or system controller and attached RDM compliant devices over a standard DMX line. This protocol will allow configuration, status monitoring, and management of these devices in such a way that does not disturb the normal operation of standard DMX512 devices that do not recognize the RDM protocol.

Digital Serial Interface (DSI) is a protocol for the controlling of lighting in buildings. It was created in 1991 by Austrian company Tridonic and is based on Manchester-coded 8-bit protocol, data rate of 1200 baud, 1 start bit, 8 data bits, 4 stop bits, and is the basis of the more sophisticated protocol Digital Addressable Lighting Interface (DALI).

The Media Gateway Control Protocol (MGCP) is a signaling and call control communications protocol used in voice over IP (VoIP) telecommunication systems. It implements the media gateway control protocol architecture for controlling media gateways connected to the public switched telephone network (PSTN). The media gateways provide conversion of traditional electronic media to the Internet Protocol (IP) network. The protocol is a successor to the Simple Gateway Control Protocol (SGCP), which was developed by Bellcore and Cisco, and the Internet Protocol Device Control (IPDC).

Art-Net is a royalty-free communications protocol for transmitting the DMX512-A lighting control protocol and Remote Device management (RDM) protocol over the User Datagram Protocol (UDP) of the Internet protocol suite. It is used to communicate between "nodes" and a "server".

The Standard Interface for Multiple Platform Link Evaluation (SIMPLE) is a military communications protocol defined in NATO's Standardization Agreement STANAG 5602.

The Open Control Architecture (OCA) is a communications protocol architecture for control, monitoring, and connection management of networked audio and video devices. Such networks are referred to as "media networks".

Storage security is a specialty area of security that is concerned with securing data storage systems and ecosystems and the data that resides on these systems.

References

  1. "Device Description Language".
  2. "ANSI E1.17-2006 Architecture for Control Networks - Device Description Language (DDL)" (PDF). Archived from the original (PDF) on 2014-11-29.
  3. "OpenACN" . Retrieved 2011-08-25.
  4. "Architecture for Control Networks project home page" . Retrieved 2022-03-09.
  5. "Acacian project on GitHub" . Retrieved 2022-05-05.
  6. "Open Lighting Architecture" . Retrieved 2012-01-05.
  7. "RUST Sacn". GitHub . Retrieved 2022-03-09.