For the purposes of this document, the terms and definitions given in OPC 100004, OPC 10000-80, OPC 10000-100, IEEE Std 8022014, IEEE Std 802.1AS2020, IEEE Std 802.1AB2016, IEEE Std 802.1Q2022, IEEE Std 1588, as well as the following apply.

All used terms are italicised in this document as described in OPC 100001.

system that includes Media Access Control (MAC) Bridge or Virtual Local Area Network(VLAN) Bridge component functionality.

[SOURCE: IEEE Std 802.1Q2022, 3.24]

set of Bridge functionalities necessary for acting as a traffic relay station in a network

A functional unit in an IEEE 802® network that acts as a source of, and/or destination for, link layer data traffic carried on the network

[SOURCE: IEEE Std 8022014, 3.1]

implementation of an end station

synchronised time in a network clock derived from a gPTP domain that is traceable to International Atomic Time

in the context of a single PTP domain, the synchronized time of a PTP Instance that is the source of time to which all other PTP Instances in the domain are synchronized

[SOURCE] IEEE Std 802.1AS2020, 3.14

PTP Instance containing the Grandmaster Clock[SOURCE IEEE Std 802.1AS2020, 3.14]

material element or assembly composed of one or more End Station Components and zero or more Bridge Components

PTP Instance that has exactly one PTP Port

[SOURCE: IEEE Std 802.1AS 2020, 3.21]

instance of the IEEE 802.1AS protocol, operating in a single time-aware system within exactly one domain.

Note 1 to entry: A PTP Instance implements the portions of IEEE Std 802.1AS indicated as applicable to either a PTP Relay Instance or a PTP End Instance.

[SOURCE: IEEE Std 802.1AS2020, 3.22]

PTP Instance that is capable of communicating synchronized time received on one PTP Port to other PTP Ports, using the IEEE 802.1AS protocol

[SOURCE: IEEE Std 802.1AS2020, 3.24]

OPC UA Application that includes UAFX functionality

IAstation supporting the OPC UA FX communication and application layer

synchronised time in a network clock derived from a gPTP domain that is traceable to an arbitrary timescale or to the PTP timescale

Note 1 to entry In general, the Working Clock time is traceable to an arbitrary timescale; however, the Working Clock time can be correlated to a recognised timing standard.

BMCABest Master Clock Algorithm

CMConnection Manager

DHCPDynamic Host Configuration Protocol

DNSDomain Name System

DSCPDifferentiated Services Code Point

gPTPGeneralised Precision Time Protocol

IETFInternet Engineering Task Force

LLDPLink Layer Discovery Protocol


MACMedia Access Control

mDNSMulticast DNS

NTPNetwork Timing Protocol

PCPPriority Code Point

PTPPrecision Time Protocol

QoSQuality of Service

RFCRequest for Comments

TCTraffic Class

TDETopology Discovery Entity

TE-MSTIDTraffic Engineering Multiple Spanning Tree Instance Identifier

TLSTransport Layer Security


TSNTime-Sensitive Networking


VLANVirtual Local Area Network

WLANWireless Local Area Network

Block diagrams are used in figures throughout this document to illustrate groupings of functionality. The blocks in these diagrams represent abstract concepts and are not meant to imply a particular implementation.

In this document, the name of a type without the inclusion of “Type” indicates an instance of the type. For example, the following phrase, “an instance of ConnectionConfigurationSetType,” can be replaced with “a ConnectionConfigurationSet”. The phrase “instances of ConnectionEndpointType” can be replaced with “ConnectionEndpoints”.