Zoom out for a second on what gets cheap and what stays hard. CubeSats made the individual satellite inexpensive, but cheap hardware does not automatically make a good constellation. Arranging hundreds of small satellites into orbits that deliver the coverage, revisit times, and connectivity you actually want is a serious design problem, and it does not get cheaper just because the parts did.
Georgia Tech's grant US11705964B2 (inventors Ian F. Akyildiz and Ahan Kak), classified in H04B 7/18521 (satellite-communications systems) with H04W 16/26, claims a large-scale constellation-design framework for CubeSats. A framework is the key word: it is methodology for laying out a swarm, not a single satellite design.
Here is the thread that ties it to the rest of the sector. We have seen patents on building satellites cheaply (modular array architectures), operating them as a fleet (command-and-control systems), and networking them (inter-satellite optical mesh). Constellation design sits upstream of all of it, deciding how many satellites go where before any of those other problems even arise.
The accessible way to see why it matters: the same hundred CubeSats can give you excellent global coverage or frustrating gaps depending purely on how their orbits are arranged. The design framework is the difference, and getting it right up front is far cheaper than discovering the gaps after launch.
Watch this: as launch costs keep falling and small-satellite swarms proliferate, systematic constellation-design tooling becomes more valuable, because the constraint shifts from can-we-afford-the-satellites to can-we-arrange-them-well. The 2023 framework reads as academic groundwork for a problem the whole industry now has to solve at scale.