A BACnet/SC node can be a simple device, such as a thermostat, or a more sophisticated device that routes to an existing BACnet system, or it could be the main workstation for the entire facility. A node connects to the primary hub from which it receives broadcast and unicast messages. Or it can directly connect to one or more nodes to receive unicast messages from that node only.
A device with an expired certificate cannot connect to the hub. Device certificates need to be updated in a timely manner. This can be an administrative challenge especially if protecting your installation is extremely important.
The TLS connection from the device terminates at the hub. The hub decodes the message, then encrypts it again to send it on to the next connection. Decoding lets the hub read the destination address and properly forward the message to the correct recipient. A hub receives messages from only trusted devices.
BACnet/SC requires no BBMD configuration with static IP addresses. The hub takes part of this functionality in that it distributes the broadcast. The hub is the heart of the BACnet/SC network. It does not require a static IP address to pass data through a secure web socket using a URI (Universal Resource Identifier).The host can use a regular URI DNS name and even a resource path to locate the hub and make a web socket connection.
A hub may be a controller, a BACnet router, a Supervisor PC or a cloud service. With cloud deployment, a hub may be a virtual machine in a data center.
If the primary hub fails, a redundant, failover hub automatically takes over.

The failover hub takes over when the device node cannot reach the primary hub. A node is configured to identify both the primary and failover hubs. The use of a failover hub is optional, but recommended.
When the primary hub is available again, the network automatically reconnects to it.