Network Design Requirements

For the Visual Networking Platform

Introduction

The Userful Visual Networking Platform uses your existing network resources to deliver visual content.

This document explains how your network can take full advantage of Userful, and how to be configured to allow Userful to reach its full potential.

If you have any questions or comments about this article, please contact your Userful account manager or sales engineer, or email us at [email protected].

Userful On-Premise

Network Structure

The On-Premise server actively sends video data to the client. To ensure that this is done without interfering with other network traffic, it is a Userful design requirement to split the traffic into separate network segments.

Example of network segmentation for On-Premise systems

uClients

LG WebOS or Android uClient require access to a local server and the Internet to receive application and firmware updates. There is no need for direct access to the corporate LAN.

The uClient can operates on a completely isolated network, but you must manually deliver application and firmware updates to the device when the server receives the update.

Application updates can be delivered from a local server or manually using a USB key; LG WebOS firmware updates can be delivered from the Internet or installed on the device using a USB key.

Firmware updates for the Userful uClient adapter are not yet supported.

Userful uClients can access cloud-connect.userful.com via TCP port 443 and can traverse subnets while remaining connected to the same subnet as the local server. If the entire Userful system is used offline and there are no updates or Internet access, it is recommended to use zero clients whenever possible.

Zero Clients

The Zero Client can be hosted on a completely isolated network, with no access to anything other than the Userful server. Zero Client firmware updates are delivered by the server itself, and the Zero Client does not need to be connected to the Internet.

Network Addressing

All client types, right out of the box, will ask for a DHCP lease on the wired interface. Ideally, a DHCP server should be available to distribute the lease. If not, other measures must be taken.

uClients

uClient devices can have their network settings configured on the device itself, using attached or included peripherals.

Zero Clients

Zero Clients cannot be managed locally. If they do not receive a response to their DHCP request after a few minutes, they will be assigned an IP address of 10. 254.10.10. In this situation, they cannot be addressed by Userful and may assign themselves conflicting IP addresses.

Once the zero client has an IP address on the same network as the Userful server, you will be able to manage the client and change its IP settings from the Userful Control Center.

Network Capacity

Zero Clients and uClients have different network specifications that must be met for reliable operation.

Zero Clients

uClients

Stream Type

JPEG

RTSP

Bandwidth usage per device

~100Mbps @ 1080p60

~14Mbps @1080p60

~40Mbps @4K60

Connection to endpoint

1Gbps

100Mbps

Wifi Available

No

Yes, but not supported for on-premise applications

Latency tolerance

Under 5ms

Unlimited

Displays per 1Gbps uplink

10-12

~50

Displays per 10Gbps uplink

16 independent displays*

36 in a single video wall*

100+

*Driver limitations limit network interface throughput to Zero Clients at 2.5Gbps

Network Firewall

Server Rules

The following Internet destinations should be accessible by the Userful server for complete connectivity and support.

Protocol

Port

Destination

Rule

Description

TCP

80

updates.userful.com

updates2.userful.com

umirror2.com

Out

Software Updates

TCP

443

cloud-connect.userful.com

Out

Userful Manager

Licensing

TCP

443

remote.userful.com

Out

Support VPN

TCP/UDP

3478

turn.userful.com

In/Out

Remote content upload and (optional) webcam

The following local ports must be accessible from the corporate LAN to allow browser-based access and operation of Userful.

Protocol

Port

Destination

Protocol

Description

TCP

5353

LAN

Peer Discovery

TCP

5701

LAN

Failover

TCP

9000

LAN

HTTP

Userful Control Center

Multicast

54327

224.2.2.3

Failover

UDP

54327

LAN

Failover

TCP

54328

LAN

Failover

These local ports from the corporate LAN on an On-Premise Server are optional.

Protocol

Port

Destination

Protocol

Description

TCP

21

LAN

FTP

FTP File Transfer

TCP

22

LAN

SSH

Local SSH

TCP

80

LAN

HTTP

Redirects to 9000

TCP/UDP

137-139, 445

LAN

SMB

Windows File sharing

TCP/UDP

631

LAN

HTTP

Printer Configuration*

*Public Computing deployments only.

uClient Rules

The following ports and services must be available between a Userful On-Premise server and endpoints running uClient and between uClient and the Internet for proper operation.

Protocol

Port

Destination

Description

TCP

443

cloud-connect.userful.com

Userful Manager

UDP

123

Server

NTP

TCP

8554

Server

RTSP Streaming

TCP/UDP

14725

Server

Video Sync

TCP

14276

Server

Video Sync

UDP

16668

Server

uClient Discovery

Zero Client Rules

Zero Clients must be placed on a separate network from the Corporate network. They will use these ports and protocols to communicate with the Userful server. It is strongly recommended that access be unrestricted on this network.

Protocol

Port

Destination

Description

UDP

26668

Zero Clients

Zero Client Discovery

TCP

52330

Zero Clients

Zero Client Discovery

UDP

52330 - 52630 incl.

Zero Clients

Zero Client Discovery

TCP/UDP

Various High Numbers

Zero Clients

Zero Client Communication

Userful Cloud

Userful uClients are able to sync to Userful Cloud servers without any other local hardware or server. They are synced and managed entirely from the Cloud web service, which is hosted by Userful in AWS.

Zero Clients can not be used with Userful Cloud, they can only be paired to a local On-Premise server.

Network Structure

uClients connecting to Userful Cloud will download and play back content locally, so are not required to occupy their own separate network. Doing so is still a recommended best-practice.

Most uClient devices come with wireless interfaces. These are not supported for On-Premise deployments, and not recommended for Cloud deployments.

Network Addressing

uClient devices come out of the box querying for DHCP on their local wired interfaces. They can be manually locally configured with static IPs.

Network Capacity

uClient downloads content from cloud servers in Userful Manager to internal storage for local playback. There are no specific bandwidth or latency requirements, except that Internet bandwidth is sufficient to deliver large content files, and local communication for synchronization is reliable.

Network Firewall

uClient devices must be able to communicate with the Internet to sync with Userful Manager, and also must be able to communicate with each other across the local network to maintain content synchronization.

Protocol

Port

Destination

Description

TCP

443

cloud-connect.userful.com

Userful Manager

UDP

123

Other uClients

NTP

TCP

8554

Other uClients

RTSP Streaming

TCP/UDP

14725

Other uClients

Video Synchronization

TCP

14276

Other uClients

Video Synchronization

UDP

16668

Other uClients

uClient Discovery