System items interaction

Within the UBIQUITY system architecture, both hardware and software system components interact with each other, by means of a server infrastructure connection between UBIQUITY Manager and the remote devices.

The system components are split in three main groups:

  1. UBIQUITY Manager: Web interface through which a support technician can connect to a remote device to provide assistance from their local computer.
  2. UBIQUITY Network Infrastructure: Connection hosting the user domains.
    • Access Servers: They consist of a distributed redundant set of servers that manage the authentication of remote devices and UBIQUITY Manager.
    • Relay Server: They consist of a distributed redundant set of servers that act as a relay for an end-to-end connection between UBIQUITY Manager and remote devices.
  3. Remote devices: They consist of industrial automation devices installed at a remote location, such as HMIs, IPCs and routers embedding the UBIQUITY Runtime, and the Augmented Reality app.
Note: See Client and server connectivity to learn more about this topic.

Remote access process overview

UBIQUITY Manager, Runtime and routers authenticate to an Access Server by means of SSL/TSL outgoing connections, which are usually allowed by firewalls.

When UBIQUITY Manager is going to establish a connection to Runtime or a router, the following process occurs:
  1. The affected endpoints select the Relay Server that provides the best round-trip-time.
  2. A secure end-to-end connection establishes between the endpoints and the Relay Server.
  3. The Relay Server forwards any encrypted messages, without decrypting them.

Server infrastructure options

Two Server Infrastructures are optionally available and can be set through the Connection Settings Tool.
Note: See UBIQUITY Manager Tools for further information on this subject.
  • Public: The connection is established through the Server Infrastructure managed by ASEM.
  • Private: The connection is established through a private Server Infrastructure, available on request through implementation of the Private Server settings.