Millimeter-wave Wi-Fi has always been a bargain with a catch. Move up into the tens-of-gigahertz bands and you get enormous bandwidth — the headroom that makes multi-gigabit wireless links plausible. But those frequencies are physically unforgiving: the signal is directional, it wants line of sight, and it is blocked by walls, furniture, and the human body. A mmWave beam that is delivering several gigabits one second can collapse the next because someone walked between the access point and the device. The cruel part is the timing: the moment the link degrades is precisely the moment you need to send the feedback that would re-steer the beam or drop to a more robust modulation — and that feedback has to travel over the very link that just fell apart. A patent application published in this week's drop takes that problem head-on by refusing to send the control conversation over the unreliable link at all.

The hero record is US20260181737A1, "Methods And Mechanism To Enable Multi-Link Millimeter Wave Request And Report," published June 25, 2026 as a pending US application and assigned to InterDigital Patent Holdings, Inc. It is classified under H04W 88/06 — the class for radio equipment supporting multiple transmission schemes. The disclosed device is a multi-link device (MLD), the 802.11be / Wi-Fi multi-link primitive: a single logical station or access point that operates more than one physical link at the same time. The move the application makes is to assign those two links different jobs. One link — a first, reliable link, described in the embodiments as a sub-7GHz link — becomes the control plane. The other — the secondary mmWave link — becomes the high-bandwidth data plane. The control needed to establish and maintain the secondary link is carried in the signaling fields of frames sent over the first link.

Control and response information for establishing/maintaining the secondary wireless link may be communicated in signaling fields of a frame over the first wireless link to enable a more reliable control information exchange than may otherwise be available via the secondary wireless link. In some embodiments, the first wireless link is a sub-7 GHz link and the secondary wireless link is a mmWave link.— Methods And Mechanism To Enable Multi-Link Millimeter Wave Request And Report, US20260181737A1

How the cross-link signaling actually works

Walk the independent claim and the mechanism is concrete. A multi-link station (ML STA) first transmits to a multi-link access point (ML AP), on the first wireless link, a capability indication that it supports exchanging control information for a second wireless link over that first link. This is the handshake that makes the rest legal: the station announces it can talk about link B while connected on link A. The AP then sends a request frame on the first link, with the frame itself indicating that it carries a request corresponding to the second link. The station replies on the first link with a response frame that, likewise, indicates it carries a response corresponding to the second link. So the entire request/report round trip about the mmWave link happens over the sub-7GHz link, where it is far more likely to get through. The dependent claims pin down that the first link is sub-7GHz and the second is mmWave, and that the request or response can carry link adaptation control information for the second link — the feedback radios use to pick modulation and coding for current conditions.

The clever, pragmatic part is that the application does not invent a new frame format from scratch. It reaches for the control fields 802.11 already has and enhances them to carry second-link meaning. The claims call out the A-Control subfield of the high-efficiency variant HT (high throughput) Control field as a vehicle for the link-adaptation information; they call out trigger frames as the request frame; and they enumerate enhanced versions of established control subfields — an enhanced Bandwidth Query Report (BQR) subfield, a High Efficiency Link Adaptation (HLA) control subfield, an enhanced Triggered Response Scheduling (TRS) control field, and an enhanced TXOP-sharing resource request — each now able to describe the other link rather than the one it is riding on. In other words, the existing in-band signaling that a Wi-Fi link uses to manage itself is repurposed as cross-link signaling, so a frame on the sub-7GHz link can request a bandwidth report or schedule a response for the mmWave link.

The payoff shows up in the claim that closes the loop: after receiving link-adaptation control information over the first link, the station transmits or receives a data frame over the second link based on that information. That is the whole thesis in one limitation. The control decision is made where reliability is cheap; the high-rate data then flows over mmWave configured by that decision. When the beam wobbles, the renegotiation does not have to fight its way through the wobble — it is already happening on the link that did not wobble.

Where it sits in the field, and in this week's drop

State-of-the-art context matters here. Multi-link operation (MLO) arrived with Wi-Fi 7 (802.11be) mostly as a throughput-and-latency play: bond 2.4, 5, and 6GHz links to aggregate capacity or fail traffic over from a congested band to a clear one. What this filing does is point the same machinery at a different goal — using one link as a reliable controller for another. That framing is the natural bridge toward folding 60GHz-class mmWave (the old 802.11ad/ay territory) into the mainstream MLD model, where historically mmWave lived as a standalone technology that struggled precisely because its control plane shared its fragility. Carrying the control over sub-7GHz is the architectural idea that makes a flaky mmWave link a manageable member of a multi-link device rather than an all-or-nothing gamble.

InterDigital's other recently published applications in this drop fill in the surrounding picture, and they cluster around the same theme of coordinating links, resources, and devices. US20260181690A1, "Enhancements For Resource Allocation In WLAN Systems," describes a station receiving a frame that allocates different frequency resources to different stations and using RTS/CTS exchanges before data — multi-user resource coordination on the same WLAN fabric the hero record extends. The rest of the cluster steps from Wi-Fi over to ambient IoT, but on a continuous spectrum of the same problem: how a coordinating node sets up, schedules, and adapts links to constrained devices. US20260181688A1 describes scheduling with sampling-frequency-offset estimation for ambient IoT, where a reader configures measurement windows and device-to-reader scheduling. US20260181680A1 describes an ambient-IoT reader doing grant processing and message prioritization, evaluating transmissions from a set of AIoT devices against preconfigured conditions. US20260181601A1 describes reader-to-device FDMA for ambient IoT, mapping symbol groups onto frequency subbands. And US20260181550A1, "Power Saving Mechanisms In NR," reaches into 5G New Radio connected-mode discontinuous reception. Read together they sketch a portfolio organized around the same instinct the hero record embodies: put the coordination intelligence in a robust control channel so the fragile link only has to do the one thing it is good at.

The standard caveat is the load-bearing one. US20260181737A1 is a published application, not a granted patent, and it describes an invention rather than a shipped, benchmarked radio. It tells us how the disclosed approach is meant to work — control on sub-7GHz, data on mmWave, existing 802.11 control fields enhanced to cross-reference each other — and where that sits relative to the multi-link operation already in Wi-Fi 7; it does not tell us how it performs in a real room, or which claims will ultimately issue. For a technology reader that is the right altitude. Strip the assignee's name off the cover and the interesting fact is the architecture: the oldest objection to millimeter-wave Wi-Fi has always been that the control conversation rides the same fragile beam as the data, and this filing simply moves that conversation to a link that does not break.