Annex D Server Capability Identifiers (Normative)

Clients benefit if they have more information about a Server before they connect, however, providing this information imposes a burden on the mechanisms used to discover Servers. The challenge is to find the right balance between the two objectives.

CapabilityIdentifiers are the way this specification achieves the balance. These identifiers are short and map onto a subset of OPC UA features which are likely to be useful during the discovery process. The identifiers are short because of length restrictions for fields used in the mDNS specification. Table is a non-normative list of possible identifiers.

Table D.1 – Examples of CapabilityIdentifiers
Identifier Description
NANo capability information is available. Cannot be used in combination with any other capability.
DAProvides current data.
HDProvides historical data.
ACProvides alarms and conditions that may require operator interaction.
HEProvides historical alarms and events.
GDSSupports the Global Discovery Server information model.
LDSThe ApplicationType is DiscoveryServer. Only used by a standalone LDS implementation.
DISupports the Device Integration (DI) information model (see DI).
ADISupports the Analyser Device Integration (ADI) information model (see ADI).
FDISupports the Field Device Integration (FDI) information model (see FDI).
FDICSupports the Field Device Integration (FDI) Communication Server information model (see FDI).
PLCSupports the PLCopen information model (see PLCopen).
S95Supports the ISA95 information model (see ISA-95).
RCPAccepts reverse connect requests as defined in OPC 10000-6.
PUBSupports the Publisher Capabilities defined in OPC 10000-14.
PSCSupports the PubSub Configuration model defined in OPC 10000-14.
ALIASSupports the Alias Names Capabilities defined in OPC 10000-17.
SKSSupports the Security Key Server (SKS) Capabilities defined in OPC 10000-14.
REGSupports the Registrar model defined in OPC 10000-21.
DCASupports the Device Configuration Application (DCA) model defined in OPC 10000-21.

The normative set of CapabilityIdentifiers can be found here:

http://www.opcfoundation.org/UA/schemas/ServerCapabilities.csv

This CSV will be changed to meet the needs of companion specifications and will not trigger an update to this document. Application developers shall always use the linked CSV.

Applications that support the PUB capability can send PubSub Messages but may not support the PubSub information model.

Client applications that support the RCP capability allow Servers to connect, however, they do not support GetEndpoints Service.