uaCap:Discovery Core

From UaCapabilities
Jump to: navigation, search

Client
Clients may be pre-configured by some out-of-band mechanism. Without pre-configuration, Clients have to support the following discovery mechanisms:

  • Allow manual entry of a DiscoveryUrl.
  • Use FindServers Service to obtain the DiscoveryUrls of Servers on the local or a remote host.
  • Use FindServersOnNetwork to obtain the DiscoveryUrls of Servers on the same multicast Subnet.
  • Discover a Server's Endpoint using the Server's DiscoveryUrl.

Server
All Servers have to support a discovery endpoint that provides Clients the following usages:

  • Locate Servers on the local host (Local Discovery): Clients can detect and choose end points of OPC UA servers located on the local host.
  • Locate Servers on a known remote host (Remote Discovery): This is for clients that know the name of the remote target host. Clients can use the host address to discover the Servers on this remote host.

Local Discovery Server

The OPC Foundation delivers a Local Discovery Server (LDS) which provides the necessary infrastructure to publicly expose multiple OPC UA Servers available on a given host system. It listens on the OPC UA port 4840. If only a single OPC UA Servers is installed on a host, an LDS is not needed and the OPC UA Server itself will listen on port 4840. The existence of an LDS is transparent for Clients that use the Discovery Services. They always connect to port 4840 and have to be prepared to find more than one Server on a single host.