WEBVTT 00:00:00.000 --> 00:00:02.580 Have you ever wondered how an event like the 00:00:02.580 --> 00:00:05.559 American Super Bowl manages hundreds of wireless 00:00:05.559 --> 00:00:07.860 microphones without turning into this chaotic 00:00:07.860 --> 00:00:10.759 wall of static is a massive undertaking. Right. 00:00:10.919 --> 00:00:15.410 Or. on the complete flip side how security professionals 00:00:15.410 --> 00:00:18.489 actually sweep a room for hidden spy bugs you 00:00:18.489 --> 00:00:20.449 know to make sure a sensitive conversation actually 00:00:20.449 --> 00:00:23.149 stays private the stakes are incredibly high 00:00:23.149 --> 00:00:26.269 in both scenarios exactly well today we are taking 00:00:26.269 --> 00:00:28.850 a deep dive into the invisible world that makes 00:00:28.850 --> 00:00:31.850 all of that possible we are pulling our insights 00:00:31.850 --> 00:00:34.490 from this remarkably dense wikipedia article 00:00:34.490 --> 00:00:38.420 uh simply titled radio frequency sweeps. It's 00:00:38.420 --> 00:00:40.560 a very concise document, but it covers a lot 00:00:40.560 --> 00:00:43.000 of ground. It really does. So our mission today 00:00:43.000 --> 00:00:45.520 is to unpack this technical document and reveal 00:00:45.520 --> 00:00:47.920 the fascinating, totally invisible landscape 00:00:47.920 --> 00:00:50.340 of the radio waves that are constantly buzzing 00:00:50.340 --> 00:00:53.100 around you, along with the tools we use to police 00:00:53.100 --> 00:00:55.020 and monitor them. Which is something we rely 00:00:55.020 --> 00:00:57.240 on constantly without realizing. Oh, absolutely. 00:00:57.520 --> 00:00:59.820 Okay, let's unpack this. What exactly are we 00:00:59.820 --> 00:01:01.820 looking at when we talk about a radio frequency 00:01:01.820 --> 00:01:04.959 sweep? Drawing directly from our source material, 00:01:05.239 --> 00:01:09.000 an RF sweep, is the process of scanning a radio 00:01:09.000 --> 00:01:12.700 frequency band. You're doing this to detect signals 00:01:12.700 --> 00:01:15.260 that are currently being transmitted within that 00:01:15.260 --> 00:01:17.579 specific range. So it's kind of like... You're 00:01:17.579 --> 00:01:20.359 systematically mapping the active broadcasting 00:01:20.359 --> 00:01:23.659 elements in a given neighborhood of the electromagnetic 00:01:23.659 --> 00:01:26.859 spectrum. Got it. I was thinking it's sort of 00:01:26.859 --> 00:01:29.239 like slowly turning the dial on a really old 00:01:29.239 --> 00:01:32.560 car radio to find a station. But obviously on 00:01:32.560 --> 00:01:34.819 a much more sophisticated scale. That's a great 00:01:34.819 --> 00:01:37.420 analogy, actually. The hardware required to do 00:01:37.420 --> 00:01:39.840 this is literally a tunable receiver with an 00:01:39.840 --> 00:01:42.019 adjustable receiving frequency. But it doesn't 00:01:42.019 --> 00:01:43.640 just sit on one channel, right? No, exactly. 00:01:43.900 --> 00:01:46.760 Instead of staying static, the equipment continuously 00:01:46.760 --> 00:01:49.280 changes its frequency of operation. It moves 00:01:49.280 --> 00:01:52.359 from a minimum frequency up to a maximum frequency, 00:01:52.439 --> 00:01:55.159 or vice versa. Just continuously scanning. Right, 00:01:55.219 --> 00:01:58.049 to survey the entire predefined band. The source 00:01:58.049 --> 00:02:00.269 makes a really specific point to emphasize that 00:02:00.269 --> 00:02:02.890 this isn't just a random haphazard process. The 00:02:02.890 --> 00:02:05.870 sweep is usually performed at a fixed, controllable 00:02:05.870 --> 00:02:07.810 rate. Yes, that controlled rate is essential. 00:02:08.270 --> 00:02:11.030 Like, it specifically gives the example of sweeping 00:02:11.030 --> 00:02:14.030 at a rate of 5 megahertz per second. What's fascinating 00:02:14.030 --> 00:02:16.979 here is how that simple act of sweeping... at 00:02:16.979 --> 00:02:19.960 that fixed rate creates this highly detailed 00:02:19.960 --> 00:02:22.780 map of the invisible activity in the air around 00:02:22.780 --> 00:02:25.639 us. Because if you sweep too fast, you risk stepping 00:02:25.639 --> 00:02:29.219 right over transient signals. Or you might fail 00:02:29.219 --> 00:02:31.379 to capture the full amplitude of a transmitter 00:02:31.379 --> 00:02:33.719 before the receiver has moved on to the next 00:02:33.719 --> 00:02:35.719 block of frequencies. Right, the filters need 00:02:35.719 --> 00:02:38.139 time to catch up. Exactly. If you sweep at that 00:02:38.139 --> 00:02:41.060 5 MHz per second rate, you're giving the receiver's 00:02:41.060 --> 00:02:44.030 internal filters enough time to settle. It accurately 00:02:44.030 --> 00:02:47.110 measures the power at each specific micro slice 00:02:47.110 --> 00:02:49.469 of the spectrum. Which brings us to the actual 00:02:49.469 --> 00:02:52.189 gear. The primary instrument the source introduces 00:02:52.189 --> 00:02:54.949 for all of this is the spectrum analyzer. A vital 00:02:54.949 --> 00:02:57.250 piece of equipment. The text notes that a spectrum 00:02:57.250 --> 00:02:59.830 analyzer incorporates that tunable receiver we 00:02:59.830 --> 00:03:01.990 were just talking about, but it pairs it with 00:03:01.990 --> 00:03:04.530 a two -dimensional visual display. That visual 00:03:04.530 --> 00:03:07.009 representation is where the diagnostic power 00:03:07.009 --> 00:03:09.889 of the sweep really comes into play. So to paint 00:03:09.889 --> 00:03:12.620 a picture for you listening. The x -axis, the 00:03:12.620 --> 00:03:15.219 horizontal line, represents the frequency. Right. 00:03:15.319 --> 00:03:18.219 And the axis, the vertical line, represents the 00:03:18.219 --> 00:03:21.500 measured power or signal strength. So as the 00:03:21.500 --> 00:03:23.919 receiver sweeps across the defined bandwidth, 00:03:24.099 --> 00:03:26.740 you get this immediate topological map of the 00:03:26.740 --> 00:03:29.979 RF environment. So a powerful continuous broadcast 00:03:29.979 --> 00:03:33.539 would just look like a massive spike at its specific 00:03:33.539 --> 00:03:36.639 frequency on the screen. Precisely. And the baseline 00:03:36.639 --> 00:03:38.960 thermal noise of the environment. just the background 00:03:38.960 --> 00:03:41.819 hum of the universe, that registers as a constant 00:03:41.819 --> 00:03:44.800 low -level jitter across the bottom of the display. 00:03:45.000 --> 00:03:47.500 Now, I noticed the source explicitly points out 00:03:47.500 --> 00:03:49.539 something interesting about how that power is 00:03:49.539 --> 00:03:52.219 measured. The logarithmic scale. Yeah. It says 00:03:52.219 --> 00:03:54.280 while the power could be displayed in linear 00:03:54.280 --> 00:03:56.979 units, a logarithmic scale usually measured in 00:03:56.979 --> 00:03:59.319 dBm, or guessable milliwatts, is usually more 00:03:59.319 --> 00:04:01.639 useful. Why is that? It all comes down to dynamic 00:04:01.639 --> 00:04:04.449 range. In a real -world environment, the power 00:04:04.449 --> 00:04:06.789 difference between signals is just staggering. 00:04:07.030 --> 00:04:09.949 Like a local television broadcast tower versus... 00:04:09.949 --> 00:04:12.610 Versus a low -power Bluetooth device sitting 00:04:12.610 --> 00:04:15.050 right next to you. We are talking about orders 00:04:15.050 --> 00:04:18.110 of magnitude in power difference. The loud shouts 00:04:18.110 --> 00:04:21.230 and the quiet whispers. Exactly. If an engineer 00:04:21.230 --> 00:04:23.730 tries to view both of those on a linear scale, 00:04:24.029 --> 00:04:26.939 they'd have to zoom out so far... to fit the 00:04:26.939 --> 00:04:29.339 massive amplitude of the TV transmitter on the 00:04:29.339 --> 00:04:31.459 screen. And then what happens to the Bluetooth 00:04:31.459 --> 00:04:34.199 signal? It becomes completely invisible. It would 00:04:34.199 --> 00:04:36.540 just blend right into that baseline noise floor 00:04:36.540 --> 00:04:38.660 at the bottom of the screen. Because a linear 00:04:38.660 --> 00:04:41.800 scale plots absolute power. But a logarithmic 00:04:41.800 --> 00:04:45.139 unit like dB solves that. Right, because it compresses 00:04:45.139 --> 00:04:47.819 that massive dynamic range into a format you 00:04:47.819 --> 00:04:50.079 can actually read. It increases exponentially, 00:04:50.279 --> 00:04:52.610 providing better detail at each value. So you 00:04:52.610 --> 00:04:55.329 can see the 100 -watt TV transmitter and the 00:04:55.329 --> 00:04:57.870 tiny micro -watt Bluetooth signal on the exact 00:04:57.870 --> 00:05:00.470 same screen without losing any detail. Cleanly 00:05:00.470 --> 00:05:02.949 and simultaneously. Which is critical, because 00:05:02.949 --> 00:05:05.490 the signals occupying this spectrum are not always 00:05:05.490 --> 00:05:07.949 just sitting there as steady, predictable spikes. 00:05:08.329 --> 00:05:10.129 Here's where it gets really interesting. The 00:05:10.129 --> 00:05:12.569 text pivots from the concept of a continuous, 00:05:12.709 --> 00:05:15.829 predictable sweep to this idea of frequency hopping. 00:05:16.129 --> 00:05:18.980 Yes, highly dynamic transmission methods. It 00:05:18.980 --> 00:05:21.459 highlights systems like CDMA code division multiple 00:05:21.459 --> 00:05:24.420 access. Instead of broadcasting continuously 00:05:24.420 --> 00:05:27.459 on a single static channel, they jump around. 00:05:27.680 --> 00:05:30.259 They physically switch from one operating frequency 00:05:30.259 --> 00:05:32.759 to another in real time. And it's not just chaotic 00:05:32.759 --> 00:05:35.540 jumping, right? The text says this hopping is 00:05:35.540 --> 00:05:38.439 usually performed in a random or pseudo -random 00:05:38.439 --> 00:05:41.339 pattern. Right. Frequency hopping spread spectrum. 00:05:41.560 --> 00:05:44.379 The transmitter and the intended receiver are 00:05:44.379 --> 00:05:47.250 synchronized to a specific algorithm. So they 00:05:47.250 --> 00:05:50.189 jump across dozens or hundreds of different frequencies 00:05:50.189 --> 00:05:52.709 in fractions of a second. So imagine you're operating 00:05:52.709 --> 00:05:55.410 that spectrum analyzer, doing your standard continuous 00:05:55.410 --> 00:05:58.750 sweep across the band. The odds of your receiver's 00:05:58.750 --> 00:06:01.370 tunable filter aligning perfectly with the exact 00:06:01.370 --> 00:06:03.730 frequency the hopping signal is using at that 00:06:03.730 --> 00:06:05.990 exact microsecond. Or basically zero. They are 00:06:05.990 --> 00:06:08.389 incredibly low. You wouldn't see a clean, solid 00:06:08.389 --> 00:06:11.110 spike. You'd likely just see brief, scattered 00:06:11.110 --> 00:06:14.170 blips as your sweep occasionally intersects with 00:06:14.170 --> 00:06:16.279 the transmission's pseudo -random pattern. It 00:06:16.279 --> 00:06:18.540 completely changes how complex signal transmission 00:06:18.540 --> 00:06:21.620 can be compared to just a simple continuous sweep. 00:06:21.899 --> 00:06:24.060 It really illustrates the cat -and -mouse nature 00:06:24.060 --> 00:06:27.720 of RF analysis. Right. So we've established what 00:06:27.720 --> 00:06:31.060 a sweep is, the spectrum analyzer, the loud and 00:06:31.060 --> 00:06:34.040 quiet signals, and the hopping. But the big question 00:06:34.040 --> 00:06:37.399 is, why do we need to sweep? Who is actually 00:06:37.399 --> 00:06:39.899 doing this? The source material provides several 00:06:39.899 --> 00:06:41.899 concrete scenarios, starting with regulatory 00:06:41.899 --> 00:06:44.800 agencies. The radio spectrum is a finite resource. 00:06:45.370 --> 00:06:48.730 And it needs strict oversight. Exactly. The article 00:06:48.730 --> 00:06:50.730 cites the FC system in the United States as the 00:06:50.730 --> 00:06:53.209 primary example. They use frequency sweeps to 00:06:53.209 --> 00:06:55.610 monitor the radio spectrum and ensure commercial 00:06:55.610 --> 00:06:58.589 and private users are strictly adhering to their 00:06:58.589 --> 00:07:01.069 licenses. So they're basically the traffic cops 00:07:01.069 --> 00:07:03.629 of the airwaves. They really are. A broadcaster 00:07:03.629 --> 00:07:05.930 is licensed to operate at a specific center frequency 00:07:05.930 --> 00:07:08.709 with a strictly defined maximum power output. 00:07:08.930 --> 00:07:10.490 And if they mess up their transmitter configuration 00:07:10.490 --> 00:07:13.029 and start bleeding over into adjacent frequencies? 00:07:13.269 --> 00:07:15.670 An FCC frequency sweep will immediately detect 00:07:15.670 --> 00:07:18.009 that out -of -band emission. They are continuously 00:07:18.009 --> 00:07:21.370 sweeping massive geographic areas to locate unlicensed 00:07:21.370 --> 00:07:24.350 transmitters or authorized users violating their 00:07:24.350 --> 00:07:26.569 power limits. But it's not just the government 00:07:26.569 --> 00:07:29.610 doing this. The text shifts over to the manufacturing 00:07:29.610 --> 00:07:32.829 floor. Consumer computers and electronic devices 00:07:32.829 --> 00:07:35.529 have to undergo testing using frequency sweeps, 00:07:35.529 --> 00:07:37.889 too. Yes, before they can even be brought to 00:07:37.889 --> 00:07:40.660 market. The goal is to ensure they avoid causing 00:07:40.660 --> 00:07:43.500 radio frequency interference with other established 00:07:43.500 --> 00:07:46.000 systems. Which makes sense. Every laptop or phone 00:07:46.000 --> 00:07:48.439 is packed with processors that generate electromagnetic 00:07:48.439 --> 00:07:51.160 fields. If they aren't properly shielded, those 00:07:51.160 --> 00:07:54.139 consumer devices essentially become rogue transmitters 00:07:54.139 --> 00:07:56.759 themselves. The source actually drills down even 00:07:56.759 --> 00:07:59.920 deeper into the manufacturing side. It mentions 00:07:59.920 --> 00:08:03.379 that specific parts, like RF oscillators, are 00:08:03.379 --> 00:08:05.879 subjected to sweeps to measure vital performance 00:08:05.879 --> 00:08:08.399 metrics. Right. It lists three... specific things 00:08:08.399 --> 00:08:11.459 they're looking for. Phase noise, harmonics, 00:08:11.519 --> 00:08:14.120 and spurious signals. So they use the sweep to 00:08:14.120 --> 00:08:16.740 measure the purity of the component. Exactly. 00:08:16.959 --> 00:08:19.600 An ideal oscillator generates energy at one single, 00:08:19.759 --> 00:08:23.079 infinitely thin frequency. But real -world physics 00:08:23.079 --> 00:08:25.959 introduces imperfections. Like phase noise. Which 00:08:25.959 --> 00:08:28.319 appears on the spectrum analyzer as a widening 00:08:28.319 --> 00:08:30.779 skirt around the base of the primary signal spike. 00:08:31.339 --> 00:08:33.799 And harmonics, which are the predictable mathematical 00:08:33.799 --> 00:08:36.620 byproducts. Right, integer multiples of the primary 00:08:36.620 --> 00:08:39.700 frequency. And spurious signals are the completely 00:08:39.700 --> 00:08:42.899 unpredictable artifacts. You need the high resolution 00:08:42.899 --> 00:08:45.879 visualization of a frequency sweep to catch all 00:08:45.879 --> 00:08:48.409 of that. It's wild that the exact same underlying 00:08:48.409 --> 00:08:51.330 technology scales from the FCC monitoring thousands 00:08:51.330 --> 00:08:54.269 of miles to an engineer testing a tiny oscillator. 00:08:54.629 --> 00:08:57.309 It's universally applicable. And speaking of 00:08:57.309 --> 00:08:59.850 wild applications, the source drops this detail 00:08:59.850 --> 00:09:01.990 that feels straight out of an espionage movie. 00:09:02.600 --> 00:09:05.399 Portable sweep equipment is used to detect covert 00:09:05.399 --> 00:09:08.220 listening devices. Commonly known as bugs. Yeah. 00:09:08.279 --> 00:09:10.480 Yes. If we connect this to the bigger picture, 00:09:10.600 --> 00:09:13.460 this is where RF sweeps bridge the gap between 00:09:13.460 --> 00:09:16.279 mass commercial regulation and individual privacy. 00:09:16.679 --> 00:09:19.500 Technical surveillance countermeasures. TSCM, 00:09:19.500 --> 00:09:21.759 exactly. They rely entirely on the principles 00:09:21.759 --> 00:09:24.480 of the tunable receiver and the spectrum analyzer. 00:09:24.779 --> 00:09:26.980 So a security professional locks into a boardroom. 00:09:27.019 --> 00:09:29.840 They aren't looking for a massive broadcast tower. 00:09:30.179 --> 00:09:32.759 They are performing a near -field RF sweep of 00:09:32.759 --> 00:09:35.679 that single room, systematically sweeping the 00:09:35.679 --> 00:09:37.940 local frequency bands, looking for an unauthorized 00:09:37.940 --> 00:09:40.759 transmitter. Because even a tiny microphone hidden 00:09:40.759 --> 00:09:43.639 in a wall has to emit radio frequency energy 00:09:43.639 --> 00:09:46.279 to get the audio out of the room. By walking 00:09:46.279 --> 00:09:48.759 through the space with a portable spectrum analyzer, 00:09:48.860 --> 00:09:51.480 they are looking for that localized spike in 00:09:51.480 --> 00:09:54.379 measured power that doesn't correspond to a known 00:09:54.379 --> 00:09:57.809 safe device like a Wi -Fi router. And I imagine 00:09:57.809 --> 00:09:59.750 with those frequency hopping techniques we talked 00:09:59.750 --> 00:10:02.429 about earlier, it takes immense technical skill 00:10:02.429 --> 00:10:04.830 to actually catch a modern bug. Oh, definitely. 00:10:04.950 --> 00:10:07.309 The operator has to configure their sweep rate 00:10:07.309 --> 00:10:10.289 and bandwidth perfectly to maximize the probability 00:10:10.289 --> 00:10:13.490 of intercepting those highly evasive signals. 00:10:13.889 --> 00:10:16.049 So what does this all mean when we take these 00:10:16.049 --> 00:10:18.029 concepts, the clean spectrum, the interference, 00:10:18.370 --> 00:10:20.710 the real -time monitoring, and apply them to 00:10:20.710 --> 00:10:23.549 a massive live event? The source document brings 00:10:23.549 --> 00:10:25.149 it all together with the Super Bowl example. 00:10:25.370 --> 00:10:27.289 Right. Professional audio. coordination at an 00:10:27.289 --> 00:10:29.549 American Super Bowl game. It is an absolute stress 00:10:29.549 --> 00:10:31.950 test for RF coordination. You've got hundreds 00:10:31.950 --> 00:10:34.110 of wireless microphones, wireless intercoms, 00:10:34.110 --> 00:10:36.590 broadcast telemetry, all operating simultaneously 00:10:36.590 --> 00:10:40.149 in this one stadium. The source explicitly points 00:10:40.149 --> 00:10:42.730 out that getting the optimum use out of all that 00:10:42.730 --> 00:10:46.049 gear requires performing a highly localized sweep 00:10:46.049 --> 00:10:49.309 of the radio spectrum. Because every single referee 00:10:49.309 --> 00:10:53.409 mic and coach and headset needs a pristine, uninterrupted 00:10:53.409 --> 00:10:56.659 channel to function. Or millions of viewers just 00:10:56.659 --> 00:10:59.700 hear static. Exactly. And the audio engineers 00:10:59.700 --> 00:11:01.659 have to utilize a slightly different sweeping 00:11:01.659 --> 00:11:04.659 strategy here. The text notes that their sweeps 00:11:04.659 --> 00:11:07.080 are generally limited in bandwidth. Just to the 00:11:07.080 --> 00:11:09.179 operating bandwidth of their specific devices? 00:11:09.480 --> 00:11:11.159 Right. They aren't looking at the whole electromagnetic 00:11:11.159 --> 00:11:14.120 spectrum. They're hyper -focused on the specific 00:11:14.120 --> 00:11:17.960 slice of UHF or VHF frequencies where their gear 00:11:17.960 --> 00:11:19.779 operates. They're hunting for the white space, 00:11:20.039 --> 00:11:22.519 the completely empty frequencies where a microphone 00:11:22.519 --> 00:11:24.659 can safely operate. And they can't just do it 00:11:24.659 --> 00:11:27.279 once. The RF environment of an empty stadium 00:11:27.279 --> 00:11:29.639 is radically different from game day with 80 00:11:29.639 --> 00:11:31.779 ,000 fans and all their cell phones. So they 00:11:31.779 --> 00:11:33.980 have to sweep in real time? Yes, during the event. 00:11:34.279 --> 00:11:36.100 They're constantly monitoring their spectrum 00:11:36.100 --> 00:11:38.279 analyzers, ensuring every piece of equipment 00:11:38.279 --> 00:11:40.919 is operating safely on previously agreed upon 00:11:40.919 --> 00:11:43.779 and coordinated frequencies. Actively policing 00:11:43.779 --> 00:11:46.980 their local airspace. Because if an unauthorized 00:11:46.980 --> 00:11:49.679 news crew powers up a transmitter on the sidelines, 00:11:49.820 --> 00:11:53.559 the real -time sweep instantly reveals the news 00:11:53.559 --> 00:11:55.720 spike. And the coordinators can track it down 00:11:55.720 --> 00:11:58.299 or move their own gear to a clean frequency before 00:11:58.299 --> 00:12:00.799 anyone at home notices. It requires an unbelievable 00:12:00.799 --> 00:12:03.740 amount of... invisible architecture and active 00:12:03.740 --> 00:12:06.179 policing. It really does, just so a referee can 00:12:06.179 --> 00:12:09.980 announce a penalty. Well, to briefly recap our 00:12:09.980 --> 00:12:12.200 journey today for you listening, we started with 00:12:12.200 --> 00:12:15.080 the basic mechanics of an RF sweep, turning the 00:12:15.080 --> 00:12:17.700 dial with a tunable receiver. Mapping the spectrum. 00:12:17.860 --> 00:12:20.289 Right. We looked at spectrum analyzers and why 00:12:20.289 --> 00:12:23.049 logarithmic DBM charts let us see the loudest 00:12:23.049 --> 00:12:25.889 and quietest signals at once. We touched on the 00:12:25.889 --> 00:12:28.629 chaos of frequency hopping. And then we explored 00:12:28.629 --> 00:12:31.070 the real world applications. Exactly. From the 00:12:31.070 --> 00:12:34.070 FCC enforcing licenses to lab testing computers, 00:12:34.230 --> 00:12:36.850 hunting for spy bugs, and finally coordinating 00:12:36.850 --> 00:12:39.889 a flawless Super Bowl broadcast. This raises 00:12:39.889 --> 00:12:42.230 an important question, though. Building on everything 00:12:42.230 --> 00:12:45.230 detailed in our source. If regulatory bodies 00:12:45.230 --> 00:12:49.009 like the FCC have to continuously sweep just 00:12:49.009 --> 00:12:52.009 to manage our finite spectrum, and a single stadium 00:12:52.009 --> 00:12:55.700 event requires a dedicated team, utilizing real 00:12:55.700 --> 00:12:58.299 -time analysis just to keep microphones working. 00:12:58.460 --> 00:13:01.399 Right. How incredibly crowded is our invisible 00:13:01.399 --> 00:13:03.759 radio spectrum becoming? That's a huge point. 00:13:03.960 --> 00:13:06.580 As we rely more and more on random frequency 00:13:06.580 --> 00:13:08.980 hopping and massive deployments of wireless tech, 00:13:09.200 --> 00:13:12.039 will the act of simply finding a quiet frequency 00:13:12.039 --> 00:13:14.220 soon become the biggest technical challenge of 00:13:14.220 --> 00:13:17.580 our time? Wow. The spectrum is finite, but our 00:13:17.580 --> 00:13:20.059 reliance on it just keeps growing. It's an invisible 00:13:20.059 --> 00:13:22.950 highway, and it is filling up fast. That is a 00:13:22.950 --> 00:13:25.090 fascinating thought to end on. Thank you for 00:13:25.090 --> 00:13:26.990 joining us on this deep dive. The next time you 00:13:26.990 --> 00:13:28.909 watch a live broadcast or even just look around 00:13:28.909 --> 00:13:31.149 the room you're in right now, consider the invisible 00:13:31.149 --> 00:13:33.350 radio waves filling the space and the sweeping 00:13:33.350 --> 00:13:35.309 tools working behind the scenes to keep it all 00:13:35.309 --> 00:13:37.210 organized. Until next time.