UCH 1.0 Current
Universal Control Hub
Universal Control Hub 1.0
Abstract
The Universal Control Hub (UCH) is the middleware component of the Universal Remote Console framework. It occupies the central position in the URC architecture, sitting between controllers (user interfaces) and targets (devices and services). The UCH manages discovery, connection establishment, and ongoing communication between these endpoints, enabling any compliant controller to operate any compliant target regardless of manufacturer or platform.
The concept of a centralized control hub was first developed at the Trace Research & Development Center at the University of Wisconsin-Madison, where the initial reference implementation demonstrated the viability of the architecture. The first production-grade implementation was created by Meticube in Portugal in 2009, marking the transition from research prototype to commercially deployable middleware.
Architecture
The UCH downloads socket descriptions from the Resource Server and exposes them to connected controllers. A socket description is a machine-interpretable specification of a target's functionality, including its variables, commands, and notifications. By mediating access to these descriptions, the UCH enables controllers to dynamically generate appropriate user interfaces without prior knowledge of the target device.
For integrating devices and services that do not natively support the URC protocol, the UCH supports Target Adapters. These adapter modules translate between the URC framework and proprietary or legacy protocols such as UPnP, ZigBee, KNX, or HTTP APIs, significantly expanding the range of controllable targets.
The UCH architecture also supports cascading mode for distributed deployments. Cascading allows multiple UCH instances to interconnect in hierarchical, mesh, peer-to-peer, or proxying configurations. This is particularly useful in large-scale installations such as smart buildings, hospital systems, or campus-wide accessibility infrastructure where a single UCH instance would be insufficient.
Scope
This technical report defines the runtime environment, lifecycle management, discovery protocols, session management, and error handling for the Universal Control Hub. It specifies the interfaces that Target Adapters and controllers must implement, the message flows for typical interaction scenarios, and the requirements for conformance testing. The scope is limited to the hub component itself; the communication protocol between controllers and the UCH is defined separately in URC-HTTP Protocol 2.0.
Implementations
The primary open-source implementation is the Trace URC SDK, hosted on SourceForge. It includes UCHj, a Java-based UCH (version 3.1), and UCH-Android, an adaptation for the Android platform. Both are released under open-source licenses to encourage adoption and experimentation by the research community.
Meticube developed commercial variants of the UCH in three editions: Basic, Professional, and Enterprise. These were available in .NET, Java, and C++ to match different deployment environments. The Professional and Enterprise editions included advanced features such as load balancing, multi-tenant session isolation, and enterprise-grade logging for large-scale accessibility deployments.
Related Standards
- URC-HTTP Protocol 2.0 — the RESTful communication protocol used between controllers and the UCH
- URC Overview 2.0 — conceptual introduction to the entire URC framework
- Resource Server HTTP 1.0 — the protocol used to retrieve socket descriptions from the Resource Server
- URC-Light 1.0 — lightweight profile for resource-constrained IoT devices
- ISO/IEC 24752-1:2014 — the international standard defining the URC framework architecture