Home›Journal›USB at the display end: what a BYOM room asks of the link
ENGINEERING · 4 November 2026 · 6 min read

USB at the display end: what a BYOM room asks of the link.

In a bring-your-own-meeting room the camera, speakerphone and touch overlay sit at the display and reach the laptop over an extender's USB 2.0 channel. What 480 Mb/s means in practice, why the isochronous figure is the one that counts, which camera formats fit — and how to write the link into a specification.

JOURNAL / 019
WHAT 480 MBIT/S LEAVES FOR A ROOM CAMERA480 · USB 2.0 SIGNALLING RATEUSB 2.0 HI-SPEEDSIGNALLING RATE480 MBIT/SNOT A THROUGHPUTBULK CEILING13 × 512 B PER 125 µS MICROFRAME≈426 MBIT/SNOTHING RESERVEDPERIODIC CAP80 % OF EACH MICROFRAME≈384 MBIT/SISOCHRONOUS + INTERRUPTONE ISOCHRONOUS ENDPOINT3 × 1,024 B PER MICROFRAME≈197 MBIT/SRESERVED · NO RETRYYUY2 1080P30 · UNCOMPRESSED4:2:2 · 16 BIT PER PIXEL≈995 MBIT/SDOES NOT FIT USB 2.0MJPEG · H.264 1080P30COMPRESSED IN THE CAMERAFITS — THE RATE VARIES BY CAMERA AND SETTINGPER CAMERA DATASHEETCHECK ITS TRANSFER TYPE02004006008001,000 MBIT/SMBIT/S ON ONE USB 2.0 LINKAN EXTENDER STATES ITS OWN USB FIGURES — ISOCHRONOUS FOR CAMERAS AND AUDIO, BULK FOR STORAGE — SPECIFY BOTH
USB 2.0's 480 Mbit/s is a signalling rate. What a camera can use is set by the transfer type — and uncompressed 1080p30 needs about twice the whole bus.

In a bring-your-own-meeting room the laptop runs the call, and the room lends it a camera, a speakerphone and often a touch overlay. Those sit at the display; the laptop sits at the table. Between them is usually an extender's USB 2.0 channel, and the meeting depends less on USB 2.0's 480 Mb/s than on what the channel carries for isochronous transfers, the kind cameras and audio use. That is the figure to specify.

This follows the data contract in USB-C is a promise the room must keep to the far end of the cable.

What does a BYOM room ask of the USB link?

That the laptop sees the room's devices as its own. Microsoft calls these BYOD rooms: rooms with no meeting-enabled compute, where the Teams client scans the connected displays and USB audio and video peripherals as the user reaches the pre-join screen. It identifies a room's peripherals by product ID, vendor ID and serial number, and Microsoft asks makers to report unique serial numbers through the USB descriptor or EDID. Zoom's BYOD mode lets a laptop with a USB connection use a Zoom Room's camera, microphone and speakers. Where those devices are mounted at the display, that USB connection is an extension.

Is USB 2.0 really 480 Mb/s?

As a signalling rate, yes: the USB-IF gives the Hi-Speed rate as 480 Mb/s. As throughput, no. Bus time is divided into 125 µs microframes. Bulk data moves in 512-byte packets, at most 13 to a microframe: about 426 Mb/s before any host or device limit. Periodic transfers, isochronous and interrupt, are held by default to 80 per cent of each microframe, about 384 Mb/s. One high-speed isochronous endpoint can declare at most three transactions per microframe; Microsoft's worked example, three of 1,024 bytes, comes to about 197 Mb/s.

An extension link adds a channel of its own, with whatever throughput its maker states; the HDBaseT Alliance lists “enhanced USB2.0 bandwidth” among the changes in 3.0. A datasheet that gives separate figures for isochronous and bulk devices is telling you something useful.

Why do isochronous and bulk transfers behave differently?

Isochronous transfers carry time-bound streams. The host reserves bus time for them; there is no handshake and no retry, so data hit by an error is lost rather than late. USB audio streams this way: Microsoft's USB Audio 2.0 driver requires an isochronous data endpoint in every streaming alternate setting. UVC cameras may use isochronous or bulk endpoints, at the maker's choice.

Bulk transfers are resent on error, but nothing is reserved for them: they are scheduled only in unused bus time, and on a busy bus they can wait indefinitely. Storage lives here. A touch overlay is a HID device, reporting over an interrupt pipe; Microsoft recommends that touchscreen controllers and high-bandwidth devices do not share a USB hub.

The reservation is the catch. A camera claims isochronous bandwidth by selecting an alternate setting, a packet size per microframe, so the claim is for the setting, not the picture. If it fails, Microsoft's guidance is to try smaller settings until one succeeds; with no bandwidth left, the device cannot be configured. In the room, that is a camera that comes up at a low resolution, or not at all.

Which camera formats fit a USB 2.0 link?

A UVC camera sends uncompressed YUV or compressed frames; the Windows inbox driver handles YUY2 and NV12, MJPEG and, under UVC 1.5, H.264. YUY2 is 4:2:2 at two bytes a pixel, so 1080p30 needs 1920 × 1080 × 16 × 30 ≈ 995 Mb/s, about twice USB 2.0's signalling rate. PTZOptics puts 1080p30 at 24-bit colour at about 1.5 Gbps and concludes that over USB 2.0 the camera must compress.

Compressed 1080p30 fits. How much of the link it takes depends on the camera and its settings, so take the figure, and the transfer type, from its maker; there is no generic number.

4K is a USB 3 matter. Logitech requires a USB 3.0 cable and port for 4K from Rally; Huddly gives about 1 Gbit/s for its IQ camera and asks for a USB 3.0 port; some USB 3 cameras drop to a low-resolution stream on USB 2.0. Over a USB 2.0 channel, specify a camera that delivers compressed 1080p30 on USB 2.0, or give a 4K camera a USB 3 extension or a room PC at the display.

What does HDBaseT 3.0 carry besides video?

The HDBaseT Alliance describes 3.0 as carrying uncompressed HDMI 2.0 audio and video, 1Gb Ethernet, USB 2.0, controls and power over one category cable. USB 2.0 joined the feature set in 2.0; 3.0 enhanced its bandwidth and took Ethernet from 100 Mbps to full-duplex gigabit. The room's peripherals need no separate USB extender, and the laptop can have a wired network on the same cable. The channel is still USB 2.0: a USB 3 device on it runs as USB 2.0 at best.

Which laptop gets the peripherals when the source changes?

A wall plate with two inputs has to decide which host the room's USB devices belong to. If the USB does not follow the video, the second presenter shares a screen while the camera stays with the first laptop. Teams scans the connected peripherals as the user reaches the pre-join screen, so the hand-over belongs at connection and selection, not mid-call. Write the rule down: which input the USB follows, and what happens when the selected input has no USB host.

How do you write the USB link into a specification?

  • USB version, end to end: USB 2.0 Hi-Speed from the device ports at the display to the host port at the table; USB 3 only where a USB 3 extension or a room PC is specified.
  • Throughput by transfer type: the extender's isochronous and bulk figures in Mbps, stated separately, with the camera's and speakerphone's isochronous needs inside the first.
  • Camera mode: compressed 1080p30, MJPEG or H.264; no uncompressed 1080p.
  • Device ports and current: the number and type of ports at the display, the current each supplies and whether it is shared, against the devices' stated draw.
  • Host selection: which input the USB follows, and the behaviour with no host connected.
  • Proof: commissioned in a real call, with the camera in its real mode and the speakerphone and touch overlay in use together.

Our own product pages state these figures in that form. The TC-RX-100 HDBaseT 3.0 receiver gives three USB 2.0 device ports at the display, two USB-A and one USB-C with 2.5 A shared, and USB throughput of about 160 Mbps for isochronous devices such as cameras and audio and about 232 Mbps for bulk devices such as storage, and an Ethernet port that gives the laptop at the plate the wired network through its USB connection. The TC-WP-SWC-210 wall plate takes USB-C or HDMI; its USB-B host port follows the HDMI input, and it reaches 40 m at 4K60 4:4:4 with USB, control and power on one CAT6A cable.

The bus is 480 Mb/s. The room runs on the isochronous figure, so that is the one to write down.

Questions, answered briefly

Is USB 2.0 fast enough for a meeting-room camera?
For compressed video, yes: a camera sending MJPEG or H.264 at 1080p30 fits a USB 2.0 link, though how much of the link it uses depends on the camera and its settings. Uncompressed 1080p30 in YUY2 needs about 995 Mb/s, about twice USB 2.0's 480 Mb/s signalling rate, and 4K cameras that require USB 3 do not belong on a USB 2.0 channel.

What is the difference between isochronous and bulk USB transfers?
Isochronous transfers have bus time reserved for them and are not retried, which suits cameras and audio. Bulk transfers are resent on error but get only the bus time left over, which suits storage. An extender can carry the two at different rates, so ask for both figures.

Does HDBaseT carry USB?
USB 2.0 joined the HDBaseT feature set in HDBaseT 2.0, and the HDBaseT Alliance describes HDBaseT 3.0 as carrying uncompressed HDMI 2.0 audio and video, 1Gb Ethernet, USB 2.0, control and power over one category cable, with enhanced USB 2.0 bandwidth. The channel is USB 2.0, so USB 3 devices run at USB 2.0 at best, and each product states its own USB throughput.

Why does a USB camera drop to a low resolution through an extender?
A camera reserves isochronous bandwidth by choosing a setting with a fixed packet size. If that reservation does not fit, the driver tries smaller settings, and if no bandwidth is left the device cannot be configured. Check the camera's isochronous need against the extender's isochronous figure, and specify a compressed 1080p30 mode.

Published by TELECIS · 4 November 2026 · Filed under Engineering
Specifying?

Send the room.

We return the architecture, the bill of materials, and the route to supply.