A Controller is Client software that interacts with the NMOS APIs to discover, connect and manage resources (Nodes, Devices, Senders and Receivers) within a networked media system.
- This document includes normative references to be followed when implementing a Controller.
- This document covers how the Controller interacts with the NMOS APIs only. It does not cover other features of the Controller software, such as presentation.
- This document does not cover any requirements relating to where a Controller is additionally acting as a Node (e.g. receiving monitoring information via IS-07).
Where this document refers to a User, this can include both human operators who drive a Controller manually and automation systems that drive a Controller programmatically.
Controllers appending paths to
href type attributes MUST support URLs both with and without a trailing slash, to avoid doubled or missing slashes.
Controllers performing requests other than
OPTIONS etc.) MUST use URLs with no trailing slash present.
The versioning format is
MINORincrements will be performed for non-breaking changes (such as the addition of attributes in a response)
MAJORincrements will be performed for breaking changes (such as the renaming of a resource or attribute)
Versions MUST be represented as complete strings. Parsing MUST proceed as follows: separate into two strings, using the point (
.) as a delimiter. Compare integer representations of
MINOR version (such that v1.12 is greater than v1.5).
Implementers of Controllers are RECOMMENDED to support multiple versions of the NMOS APIs simultaneously in order to ease the upgrade process in live facilities.
API Common Keys
Error Codes & Responses
The NMOS APIs use HTTP status codes to indicate success, failure and other cases to Controllers as per RFC 7231 and related standards.
As explicit handling of every possible HTTP response code is not expected, Controllers MUST implement generic handling for ranges of response codes (
However, where the API specifies explicit response codes the Controller SHOULD handle these cases explicitly.
When a Controller performs
HEAD requests, it MUST correctly handle a
301 (Moved Permanently) redirect to accommodate the API implementations permitted in the APIs: URLs: Approach to Trailing Slashes section of this specification.
If a Controller receives an HTTP
4xx response code from the API, a failure has occurred.
The Controller SHOULD display the content of the response’s
error field to the User if possible.
Query API Discovery
In order to locate the Query API, the Controller SHOULD support all of the following:
- Unicast DNS
- Multicast DNS (mDNS)
- Direct configuration with the location of a preferred Query API
The Controller SHOULD offer unicast DNS-SD as the default mechanism.
Controllers MUST observe and interpret all of the TXT records returned with the DNS Service Discovery responses according to the requirements for Query API Clients specified in the APIs: API Paths section of this specification.
The Controller MUST be capable of using the Query API to discover any registered resource, including Node, Device, Source, Flow, Sender, and Receiver, as described in the APIs section of this specification.
When using the Query API, query filters SHOULD be used (and advanced query language where available) to cut down on the volume of resources returned to the Controller, as specified in the APIs: Query Parameters document.
Controllers MUST adhere to the Requirements for Query API Clients found in this specification.
If using the HTTP API rather than WebSocket subscriptions, pagination requirements MUST be implemented as specified in the APIs: Query Parameters: Pagination section of this specification.
In order to avoid polling of the HTTP API, it is RECOMMENDED that Controllers use the WebSocket subscription mechanism.
Dynamic Update of Resources
The Controller MUST be capable of using the Query API to discover and dynamically report the state of any registered resource, including Node, Device, Source, Flow, Sender, and Receiver.
- The Controller MUST indicate available Senders to the user.
- The Controller MUST reflect changes in presence/absence of Senders to the user after a maximum of 30 seconds.
- The Controller MUST indicate available Receivers to the user which have an IS-05 Connection API. However, the Controller MAY choose to omit discovered Receivers without an IS-05 Connection API.