WEBVTT - What is 5G?

0:00:04.120 --> 0:00:07.160
<v Speaker 1>Get in touch with technology with tech Stuff from how

0:00:07.200 --> 0:00:13.760
<v Speaker 1>stuff works dot com. Hey there, and welcome to tech Stuff.

0:00:13.800 --> 0:00:16.759
<v Speaker 1>I'm your host, Jonathan Strickland. I'm an executive producer with

0:00:16.800 --> 0:00:18.720
<v Speaker 1>How Stuff Works, and I heart radio and I love

0:00:18.760 --> 0:00:22.360
<v Speaker 1>of all things tech. And you've probably heard a little

0:00:22.400 --> 0:00:25.639
<v Speaker 1>bit about five G technology as of late. Back in

0:00:25.800 --> 0:00:29.040
<v Speaker 1>January two thousand nineteen, some of the buzz around five

0:00:29.120 --> 0:00:31.800
<v Speaker 1>G was all about how computer manufacturers are starting to

0:00:31.840 --> 0:00:35.120
<v Speaker 1>build in five G technology into the next generation of

0:00:35.200 --> 0:00:38.880
<v Speaker 1>smartphones and laptops and other devices, and both A T

0:00:39.000 --> 0:00:42.919
<v Speaker 1>and T and Verizon had marketing pushes already that mentioned

0:00:42.960 --> 0:00:46.400
<v Speaker 1>five G in recent products and services, despite the fact

0:00:46.440 --> 0:00:51.080
<v Speaker 1>that these technologies aren't actually fully five G. But we'll

0:00:51.120 --> 0:00:53.320
<v Speaker 1>get to that. And then you had the President of

0:00:53.360 --> 0:00:56.320
<v Speaker 1>the United States saying that the US companies should really

0:00:56.360 --> 0:00:59.240
<v Speaker 1>be rolling out five G technology faster, and that we

0:00:59.240 --> 0:01:03.000
<v Speaker 1>should already be looking into six G, which isn't even

0:01:03.040 --> 0:01:07.000
<v Speaker 1>a thing. Heck, five G isn't really a thing yet,

0:01:07.040 --> 0:01:11.720
<v Speaker 1>at least not practically. Wireless technology can be confusing on

0:01:11.760 --> 0:01:14.080
<v Speaker 1>a good day, so I figured it's high time I

0:01:14.160 --> 0:01:17.120
<v Speaker 1>tackled this subject. So, what the heck is five G

0:01:17.600 --> 0:01:20.000
<v Speaker 1>and why does it matter. I'm going to try and

0:01:20.080 --> 0:01:22.640
<v Speaker 1>cover a bit about how five G works as well,

0:01:23.000 --> 0:01:25.800
<v Speaker 1>but it gets super complicated, so I'm gonna save that

0:01:25.880 --> 0:01:28.000
<v Speaker 1>for the end, and I'm not going to get too

0:01:28.040 --> 0:01:33.520
<v Speaker 1>technical because one it would require eight episodes, and two

0:01:34.160 --> 0:01:37.320
<v Speaker 1>I don't fully understand all the ins and outs myself,

0:01:37.440 --> 0:01:40.760
<v Speaker 1>so just being fully transparent there. Anyway, let's get the

0:01:40.800 --> 0:01:44.040
<v Speaker 1>relatively easy part out of the way. First. Five G

0:01:44.560 --> 0:01:49.160
<v Speaker 1>refers to the fifth generation of wireless standards. Now that

0:01:49.600 --> 0:01:53.440
<v Speaker 1>by itself sounds pretty straightforward, but in reality, things get

0:01:53.520 --> 0:01:57.240
<v Speaker 1>really messy when you start looking into details. While each

0:01:57.440 --> 0:02:01.680
<v Speaker 1>G refers to a different generation, there were different standards

0:02:02.040 --> 0:02:05.720
<v Speaker 1>within each generation, making it a bit more complicated, and

0:02:05.800 --> 0:02:09.600
<v Speaker 1>generations would overlap one another. While we would be rolling

0:02:09.639 --> 0:02:13.560
<v Speaker 1>out four G, you still had companies investing and improving

0:02:13.680 --> 0:02:18.160
<v Speaker 1>three G. So this isn't very clear cut. It's not

0:02:18.280 --> 0:02:20.840
<v Speaker 1>like you can just look at one span of years

0:02:20.880 --> 0:02:24.000
<v Speaker 1>and say this represents two G and in the next

0:02:24.040 --> 0:02:27.080
<v Speaker 1>band this represents three G. It's a little more wibbly

0:02:27.120 --> 0:02:31.720
<v Speaker 1>wobbly timey whymy than that. But this is also easier

0:02:31.720 --> 0:02:34.480
<v Speaker 1>to think about if I use an analogy, something that

0:02:34.560 --> 0:02:37.160
<v Speaker 1>we're all familiar with. So I'm going to talk about computers.

0:02:37.600 --> 0:02:40.919
<v Speaker 1>I'm going to arbitrarily divide up personal computers into different

0:02:40.960 --> 0:02:43.840
<v Speaker 1>generations for the purposes of this example. But please keep

0:02:43.840 --> 0:02:46.440
<v Speaker 1>in mind this is really just to illustrate a point,

0:02:46.520 --> 0:02:48.239
<v Speaker 1>and I'm going to be skipping over a lot of stuff.

0:02:48.280 --> 0:02:51.400
<v Speaker 1>So I am going to say that in the first

0:02:51.560 --> 0:02:55.880
<v Speaker 1>generation of mainstream personal computers, once you get out of

0:02:55.919 --> 0:02:59.640
<v Speaker 1>the hobbyist level, we have the Apple two computers and

0:02:59.680 --> 0:03:02.960
<v Speaker 1>the I b MPC computers. Now I'm ignoring all the

0:03:03.000 --> 0:03:06.000
<v Speaker 1>other models out there, like the Common sixty four really

0:03:06.040 --> 0:03:09.200
<v Speaker 1>in just to simplify things. So we're talking about Apple

0:03:09.240 --> 0:03:12.240
<v Speaker 1>and IBM computers. So these two types of computers were

0:03:12.240 --> 0:03:14.760
<v Speaker 1>in the first generation, but they each operated on their

0:03:14.760 --> 0:03:17.440
<v Speaker 1>own chip sets and operating systems, so they were not

0:03:17.560 --> 0:03:21.399
<v Speaker 1>compatible with each other. They're both first generation, but they're

0:03:21.440 --> 0:03:26.000
<v Speaker 1>both proprietary in their own approach. In the second generation,

0:03:26.360 --> 0:03:30.560
<v Speaker 1>we then have the Macintosh computer and the IBM Clone computers.

0:03:31.000 --> 0:03:34.440
<v Speaker 1>Now these computers were more advanced than their predecessors, but

0:03:34.600 --> 0:03:38.800
<v Speaker 1>still were incompatible with each other. Then in the third generation,

0:03:38.840 --> 0:03:42.240
<v Speaker 1>you have Mac computers, so no longer just Macintosh. Now

0:03:42.320 --> 0:03:46.280
<v Speaker 1>we call them Max and all the different Windows based machines,

0:03:46.760 --> 0:03:49.960
<v Speaker 1>so each generation had more than one standard in it,

0:03:50.080 --> 0:03:54.480
<v Speaker 1>and the same can be said for wireless technologies. I've

0:03:54.520 --> 0:03:57.920
<v Speaker 1>covered the different generations of wireless tech and other episodes,

0:03:58.040 --> 0:04:01.200
<v Speaker 1>but I'm going to give a cliffs notes version of

0:04:01.240 --> 0:04:03.600
<v Speaker 1>what it was all about on this episode. So we

0:04:03.640 --> 0:04:08.080
<v Speaker 1>could say that each generation is marked by two major features.

0:04:08.440 --> 0:04:12.880
<v Speaker 1>First that each generation improved upon the data transfer rates

0:04:13.080 --> 0:04:17.920
<v Speaker 1>of its preceding generation, and second that each generation changed

0:04:17.960 --> 0:04:21.960
<v Speaker 1>the encoding methods for data, which not only enabled these

0:04:22.040 --> 0:04:26.200
<v Speaker 1>improved data transfer rates, but also made each succeeding generation

0:04:26.480 --> 0:04:29.560
<v Speaker 1>incompatible with the previous ones, meaning that if you had

0:04:29.600 --> 0:04:33.920
<v Speaker 1>an old cellular phone or device with cellular wireless capabilities,

0:04:34.320 --> 0:04:37.320
<v Speaker 1>it wouldn't be able to take advantage of these newer

0:04:37.360 --> 0:04:40.479
<v Speaker 1>wireless communications technologies. If you had a two G cell phone,

0:04:40.800 --> 0:04:44.440
<v Speaker 1>you could not use the three G cell phone network. Typically,

0:04:44.920 --> 0:04:49.480
<v Speaker 1>newer devices would have some compatibility with older standards, usually

0:04:49.480 --> 0:04:52.880
<v Speaker 1>because it takes time to roll out these new systems,

0:04:53.040 --> 0:04:58.680
<v Speaker 1>so you want to have built in backwards compatibility so

0:04:58.720 --> 0:05:01.320
<v Speaker 1>that if you can't get access to the new network,

0:05:01.360 --> 0:05:04.839
<v Speaker 1>you can at least still use the older network. This

0:05:05.000 --> 0:05:07.760
<v Speaker 1>sometimes would even require the user to make the switch

0:05:08.000 --> 0:05:11.240
<v Speaker 1>on uh the actual device they were using to go

0:05:11.400 --> 0:05:15.599
<v Speaker 1>to an older wireless network. But even just saying that

0:05:15.640 --> 0:05:19.839
<v Speaker 1>each generation is faster than the previous one isn't really accurate.

0:05:19.880 --> 0:05:23.120
<v Speaker 1>I mentioned just a minute ago these generations can overlap.

0:05:23.680 --> 0:05:28.400
<v Speaker 1>So when each generation first emerged out of the development

0:05:28.400 --> 0:05:30.960
<v Speaker 1>phase into the deployment phase, so it's becoming a real

0:05:31.000 --> 0:05:34.520
<v Speaker 1>world thing, it wasn't really capable of delivering its full

0:05:34.520 --> 0:05:39.400
<v Speaker 1>potential right away. Nearly every generation saw improvements and data

0:05:39.480 --> 0:05:42.960
<v Speaker 1>rates over time, and sometimes you're in a situation in

0:05:43.000 --> 0:05:47.160
<v Speaker 1>which the network or your device can't manage the ideal

0:05:47.200 --> 0:05:52.159
<v Speaker 1>transfer rates. So you've got a device that maybe runs

0:05:52.160 --> 0:05:54.560
<v Speaker 1>on let's say the three G network, and you've got

0:05:54.560 --> 0:05:58.040
<v Speaker 1>a three G network, but there could be other elements

0:05:58.080 --> 0:06:02.240
<v Speaker 1>at play that mean you can't get the ideal speeds

0:06:02.279 --> 0:06:05.479
<v Speaker 1>of the three G network even though you're using the

0:06:05.520 --> 0:06:08.719
<v Speaker 1>proper technologies. I'll talk more about that in a second

0:06:08.760 --> 0:06:12.479
<v Speaker 1>to actually we can cover it now. So I'm specifically

0:06:12.480 --> 0:06:16.000
<v Speaker 1>thinking about situations like the one I would find myself

0:06:16.160 --> 0:06:19.200
<v Speaker 1>in when I would attend c e S a few

0:06:19.320 --> 0:06:22.840
<v Speaker 1>years ago, maybe a decade ago. So CEES the Consumer

0:06:22.839 --> 0:06:26.760
<v Speaker 1>Electronics Show is heavily attended by people all using multiple

0:06:26.800 --> 0:06:31.400
<v Speaker 1>devices that are tapping into the local mobile networks. So

0:06:31.600 --> 0:06:37.400
<v Speaker 1>there are phones, their tablets, their computers. There's tons of interference.

0:06:37.440 --> 0:06:40.159
<v Speaker 1>There's just there's a lot of trying to connect to

0:06:40.200 --> 0:06:43.120
<v Speaker 1>the network at c E S And it doesn't really

0:06:43.160 --> 0:06:46.120
<v Speaker 1>matter which carrier you have. The fact that there's so

0:06:46.200 --> 0:06:49.440
<v Speaker 1>many people there and so many devices, all the carriers

0:06:49.560 --> 0:06:53.600
<v Speaker 1>are hit with requests to tap into the networks at

0:06:53.600 --> 0:06:57.080
<v Speaker 1>the same time, so it tends to over tax those networks.

0:06:57.279 --> 0:06:59.120
<v Speaker 1>And even if your phone indicates that you have a

0:06:59.120 --> 0:07:01.400
<v Speaker 1>strong signal, I can look at my phone it says, oh,

0:07:01.400 --> 0:07:04.520
<v Speaker 1>I've got full bars of signal. I can easily connect

0:07:04.520 --> 0:07:06.760
<v Speaker 1>to the network. You would end up with a terrible

0:07:06.880 --> 0:07:10.200
<v Speaker 1>data transfer rate where you couldn't even send a text

0:07:10.280 --> 0:07:12.280
<v Speaker 1>message out. There were times when I would switch my

0:07:12.320 --> 0:07:16.760
<v Speaker 1>phone to an older wireless standard and pop onto a

0:07:16.880 --> 0:07:20.720
<v Speaker 1>less congested network. Even though the top data transfer rate

0:07:20.760 --> 0:07:25.680
<v Speaker 1>of the older generation was less impressive than the current generation,

0:07:26.040 --> 0:07:30.080
<v Speaker 1>I would get better results due to the lack of traffic. So, yeah,

0:07:30.160 --> 0:07:34.240
<v Speaker 1>this gets really messy. It's not so clear cut. Now,

0:07:34.320 --> 0:07:37.280
<v Speaker 1>let's talk about the generations themselves and keep in mind

0:07:37.320 --> 0:07:39.720
<v Speaker 1>Like I said, these generations had a lot of overlap.

0:07:40.080 --> 0:07:43.720
<v Speaker 1>Some regions like Asia would roll out new generations faster

0:07:44.280 --> 0:07:46.880
<v Speaker 1>than other parts of the world, like North America. So

0:07:46.920 --> 0:07:49.280
<v Speaker 1>there's no hard and fast dates that we can use

0:07:49.480 --> 0:07:53.440
<v Speaker 1>for this, because the deployment of each generation took a

0:07:53.440 --> 0:07:56.760
<v Speaker 1>long time and didn't start everywhere all at the same time.

0:07:57.360 --> 0:08:00.240
<v Speaker 1>Now you could argue that there is a U O

0:08:00.360 --> 0:08:03.800
<v Speaker 1>G generation of wireless communications before we even get the

0:08:03.880 --> 0:08:09.320
<v Speaker 1>one G. The zero G generation would include radio telephones.

0:08:09.440 --> 0:08:12.760
<v Speaker 1>This is before there were cellular networks, before there were

0:08:12.800 --> 0:08:17.520
<v Speaker 1>cell towers, so this is pure radio transmission. The following

0:08:17.560 --> 0:08:21.880
<v Speaker 1>generations would move to cell tower technology and there would

0:08:21.920 --> 0:08:25.320
<v Speaker 1>be this new technology that would allow a handoff or

0:08:25.320 --> 0:08:28.640
<v Speaker 1>a handshake from one cell tower to another to allow

0:08:28.680 --> 0:08:32.760
<v Speaker 1>a call to transfer from one tower to another tower

0:08:33.320 --> 0:08:37.080
<v Speaker 1>without interrupting the actual call. The first generation of wireless

0:08:37.080 --> 0:08:41.520
<v Speaker 1>communication standards only carried voice signals. There was no data

0:08:41.640 --> 0:08:45.480
<v Speaker 1>beyond voice, and it included a lot of different standards

0:08:45.520 --> 0:08:48.800
<v Speaker 1>like A MPs or AMPS in North America and in

0:08:49.080 --> 0:08:52.040
<v Speaker 1>MT in Eastern Europe, or T A C S TAX

0:08:52.520 --> 0:08:55.480
<v Speaker 1>in the UK, and several more UH and it was

0:08:55.520 --> 0:09:00.720
<v Speaker 1>analog that was the analog generation of wireless community cation standards.

0:09:00.960 --> 0:09:04.839
<v Speaker 1>The second generation, or two G, was able to carry

0:09:04.880 --> 0:09:07.439
<v Speaker 1>not just voice, but data signals. This was the first

0:09:07.679 --> 0:09:12.840
<v Speaker 1>digital way of carrying cell phone conversations. Also, this allowed

0:09:12.880 --> 0:09:16.679
<v Speaker 1>for encryption. You could encrypt the signal. In the analog days,

0:09:17.280 --> 0:09:20.559
<v Speaker 1>you could technically tap in and listen to people talking

0:09:20.800 --> 0:09:26.120
<v Speaker 1>on wireless communications because it was unencrypted. That changed with

0:09:26.160 --> 0:09:29.000
<v Speaker 1>two G. So this is our switch from analog to

0:09:29.040 --> 0:09:31.840
<v Speaker 1>digital cellular phones, and it also introduced us to the

0:09:31.880 --> 0:09:34.959
<v Speaker 1>era of text messaging that was suddenly possible with two G.

0:09:35.440 --> 0:09:38.800
<v Speaker 1>And the standards in this generation included G S M C,

0:09:39.080 --> 0:09:42.880
<v Speaker 1>d M A, and T d M A. Then, depending

0:09:42.960 --> 0:09:45.560
<v Speaker 1>upon whom you ask, we get a bit of a cheat.

0:09:45.800 --> 0:09:49.640
<v Speaker 1>This happens in between lots of the different generations. So

0:09:49.720 --> 0:09:52.520
<v Speaker 1>there's some people who say there's a generation two point

0:09:52.600 --> 0:09:56.200
<v Speaker 1>five G or enhanced two G. This was not a

0:09:56.240 --> 0:10:00.560
<v Speaker 1>total departure from the two G standards and methods of operation,

0:10:00.720 --> 0:10:04.280
<v Speaker 1>but it allowed for better data transfer rates. So G,

0:10:04.440 --> 0:10:07.640
<v Speaker 1>p R S and EDGE would be considered two point

0:10:07.679 --> 0:10:11.280
<v Speaker 1>five G technologies, at least by some people. Other people say, no,

0:10:11.520 --> 0:10:13.920
<v Speaker 1>you don't split out two point five G. Those are

0:10:13.960 --> 0:10:16.920
<v Speaker 1>all two G standards, so it should all belong in

0:10:16.960 --> 0:10:20.439
<v Speaker 1>the same family, and because no one really agrees with this,

0:10:20.800 --> 0:10:23.840
<v Speaker 1>it makes matters even more confusing than they already were.

0:10:24.240 --> 0:10:26.559
<v Speaker 1>Then we get the three G that allowed enough data

0:10:26.679 --> 0:10:29.840
<v Speaker 1>throughput for video signals to come through. I would argue

0:10:29.880 --> 0:10:33.320
<v Speaker 1>the three G advances are what allowed truly useful applications

0:10:33.320 --> 0:10:39.040
<v Speaker 1>of smartphone technology, although interestingly some companies like Apple took

0:10:39.040 --> 0:10:43.559
<v Speaker 1>their time actually embracing three G. Standards included U T

0:10:43.880 --> 0:10:46.360
<v Speaker 1>M S C D M A, two thousand H S

0:10:46.440 --> 0:10:49.360
<v Speaker 1>P D A, and E V D O, and like

0:10:49.480 --> 0:10:52.320
<v Speaker 1>two G, some people split that generation out to be

0:10:52.720 --> 0:10:56.520
<v Speaker 1>three and three point five or even three three point

0:10:56.520 --> 0:11:00.320
<v Speaker 1>five and three point seven five G. The real purpose

0:11:00.320 --> 0:11:02.840
<v Speaker 1>of that, again is to single out advances that allowed

0:11:02.840 --> 0:11:06.320
<v Speaker 1>for better data transfer rates. By the end of the

0:11:06.320 --> 0:11:10.280
<v Speaker 1>three G development cycle, some standards could support data transfer

0:11:10.360 --> 0:11:13.040
<v Speaker 1>rates of a few megabits per second, whereas the two

0:11:13.080 --> 0:11:16.520
<v Speaker 1>G technologies maxed out at a couple of hundred kilobits

0:11:16.679 --> 0:11:20.280
<v Speaker 1>per second. So I'll talk a little bit about what

0:11:20.400 --> 0:11:23.000
<v Speaker 1>these data transfer rates mean in a second so that

0:11:23.040 --> 0:11:25.040
<v Speaker 1>we get a better understanding of it. But essentially it

0:11:25.080 --> 0:11:27.839
<v Speaker 1>meant that you could send more information in the same

0:11:27.880 --> 0:11:32.720
<v Speaker 1>amount of time as older devices could do. Right now,

0:11:33.280 --> 0:11:35.880
<v Speaker 1>the latest tech we can use belongs to four G,

0:11:36.440 --> 0:11:39.080
<v Speaker 1>or you could argue four point five if you wanted to.

0:11:39.800 --> 0:11:45.679
<v Speaker 1>This is the enhanced protocol. The standards would be Y

0:11:45.760 --> 0:11:49.800
<v Speaker 1>MAX and Long Term Evolution or LTE. Now these days

0:11:50.120 --> 0:11:53.400
<v Speaker 1>you'd be more likely to talk about LTE Advanced. To

0:11:53.480 --> 0:11:55.920
<v Speaker 1>be a four G system, it first has to meet

0:11:55.960 --> 0:12:00.800
<v Speaker 1>requirements that were established in the International Mobile Telecommunication Advanced

0:12:00.920 --> 0:12:05.680
<v Speaker 1>Set of Standards. The International Telecommunication Union is a department

0:12:05.760 --> 0:12:09.599
<v Speaker 1>in the United Nations and it's responsible for creating those standards.

0:12:10.120 --> 0:12:13.920
<v Speaker 1>This technology is still scaling up today with data transfer

0:12:14.000 --> 0:12:16.760
<v Speaker 1>rates and the hundreds of megabits per second in some

0:12:16.920 --> 0:12:20.400
<v Speaker 1>of the implementations. Some of them are even hitting up

0:12:20.400 --> 0:12:24.720
<v Speaker 1>to a gigabit per second at least in theory. Now, again,

0:12:24.760 --> 0:12:27.560
<v Speaker 1>that doesn't mean you're actually going to see data transfer

0:12:27.640 --> 0:12:30.839
<v Speaker 1>rates at that level, even if you have a compatible

0:12:30.840 --> 0:12:33.680
<v Speaker 1>device and service. But in general, if you do have

0:12:33.760 --> 0:12:36.560
<v Speaker 1>those things, you'll be able to download or stream content

0:12:36.679 --> 0:12:39.600
<v Speaker 1>more effectively than those of us who do not have

0:12:39.800 --> 0:12:43.560
<v Speaker 1>access to those services and products. So what does this

0:12:43.640 --> 0:12:46.640
<v Speaker 1>all mean for us? Well, it mostly boils down to

0:12:46.920 --> 0:12:51.640
<v Speaker 1>two really big things per generation, where do our phones work?

0:12:52.200 --> 0:12:55.480
<v Speaker 1>And how much data can we access per given unit

0:12:55.559 --> 0:12:58.680
<v Speaker 1>of time. So back during the two G days, the

0:12:58.760 --> 0:13:02.640
<v Speaker 1>United States was split between using the G s M standard,

0:13:02.880 --> 0:13:06.200
<v Speaker 1>which was also used in Europe and Asia, or the

0:13:06.280 --> 0:13:09.600
<v Speaker 1>c d M A standard, which was primarily just used

0:13:09.600 --> 0:13:11.160
<v Speaker 1>in the United States. There were a couple of other

0:13:11.160 --> 0:13:14.400
<v Speaker 1>places that also used it, but US was the primary

0:13:15.000 --> 0:13:18.000
<v Speaker 1>uh place where you would find c d M A technology.

0:13:18.080 --> 0:13:20.520
<v Speaker 1>So if you happen to have service with a T

0:13:20.720 --> 0:13:23.240
<v Speaker 1>and T or T Mobile, you had a G s

0:13:23.360 --> 0:13:26.120
<v Speaker 1>M phone which at least had the potential to work

0:13:26.200 --> 0:13:29.320
<v Speaker 1>on European networks. That wasn't a guarantee, by the way.

0:13:29.440 --> 0:13:33.720
<v Speaker 1>You actually had to have a special band of antenna

0:13:33.880 --> 0:13:35.760
<v Speaker 1>and chip in your phone in order to be able

0:13:35.800 --> 0:13:38.360
<v Speaker 1>to use European networks even if you had a G

0:13:38.559 --> 0:13:40.880
<v Speaker 1>s M phone, but at least in theory it was

0:13:40.920 --> 0:13:45.720
<v Speaker 1>compatible if you were on Verizon or Sprint in those days,

0:13:45.760 --> 0:13:47.680
<v Speaker 1>and that meant you were using a c d M

0:13:47.720 --> 0:13:51.920
<v Speaker 1>A phone, which was not compatible with Europe's systems at all.

0:13:52.080 --> 0:13:53.800
<v Speaker 1>So you would have to get a different phone if

0:13:53.840 --> 0:13:56.760
<v Speaker 1>you wanted to travel to Europe and and call somebody.

0:13:57.080 --> 0:14:01.320
<v Speaker 1>Now that's just one example of one ACE where you

0:14:01.440 --> 0:14:03.920
<v Speaker 1>had a standard that works in certain parts of the

0:14:03.920 --> 0:14:06.240
<v Speaker 1>world and not in others. This is still true for

0:14:06.360 --> 0:14:10.840
<v Speaker 1>a lot of different wireless communications technologies. All right, we've

0:14:10.840 --> 0:14:13.280
<v Speaker 1>set the ground. We're gonna go into a little more

0:14:13.360 --> 0:14:15.800
<v Speaker 1>detail about data transfer rates and talk about five G

0:14:15.920 --> 0:14:18.600
<v Speaker 1>in just a moment. But first let's take a quick break.

0:14:26.080 --> 0:14:30.960
<v Speaker 1>More recent generations of wireless communications technologies generally provide better

0:14:31.040 --> 0:14:33.960
<v Speaker 1>data transfer speeds, and we often refer to them as

0:14:34.000 --> 0:14:37.840
<v Speaker 1>being faster, that the four G network is faster than

0:14:37.880 --> 0:14:41.880
<v Speaker 1>the three G network, But really what we mean is

0:14:41.920 --> 0:14:45.680
<v Speaker 1>that the more recent generations have a higher capacity to

0:14:45.800 --> 0:14:50.960
<v Speaker 1>deliver information on our devices, because ultimately, all this information

0:14:51.120 --> 0:14:54.080
<v Speaker 1>is traveling at the speed of light more or less,

0:14:54.560 --> 0:14:58.640
<v Speaker 1>well less, you can't go more, so no transmission is

0:14:58.680 --> 0:15:02.840
<v Speaker 1>really faster than any other. It's not like the signals

0:15:02.880 --> 0:15:06.200
<v Speaker 1>of two G traveled more slowly than the signals of

0:15:06.240 --> 0:15:08.840
<v Speaker 1>three G. They all travel at the same speed. It's

0:15:08.880 --> 0:15:13.680
<v Speaker 1>just that the later generations were able to carry more

0:15:13.800 --> 0:15:17.240
<v Speaker 1>data in that same amount of speed. So let's go

0:15:17.320 --> 0:15:20.280
<v Speaker 1>with another analogy. I love using analogies to explain this

0:15:20.360 --> 0:15:22.800
<v Speaker 1>kind of stuff, and we're going to talk about cars.

0:15:23.000 --> 0:15:27.000
<v Speaker 1>I think that makes it fairly clear. So in this analogy,

0:15:27.320 --> 0:15:30.320
<v Speaker 1>let's say you've got a smart car and you've got

0:15:30.320 --> 0:15:33.360
<v Speaker 1>a semitruck, and they're both on the same stretch of road,

0:15:33.720 --> 0:15:36.400
<v Speaker 1>and the road's speed limit is thirty miles per hour.

0:15:36.720 --> 0:15:39.120
<v Speaker 1>And for the sake of this example, we're going to

0:15:39.160 --> 0:15:42.920
<v Speaker 1>assume both drivers are following that speed limit, which I

0:15:42.960 --> 0:15:46.360
<v Speaker 1>admit is pretty low, but they're both following it. So

0:15:46.400 --> 0:15:49.120
<v Speaker 1>in the world telecommunications, we don't have any choice but

0:15:49.200 --> 0:15:51.960
<v Speaker 1>to follow the universal speed limit. You cannot go faster

0:15:52.040 --> 0:15:55.080
<v Speaker 1>than light. But here we're just saying that the drivers

0:15:55.160 --> 0:15:58.640
<v Speaker 1>will not go above the speed limits. So the smart

0:15:58.640 --> 0:16:02.720
<v Speaker 1>car in the semi truck are moving at the same speed. However,

0:16:03.160 --> 0:16:06.560
<v Speaker 1>you can fit a whole lot more stuff inside that

0:16:06.640 --> 0:16:09.680
<v Speaker 1>semi truck than you could in the little smart car,

0:16:10.160 --> 0:16:13.120
<v Speaker 1>So you can deliver a huge amount of material in

0:16:13.240 --> 0:16:15.680
<v Speaker 1>one trip in the semi truck, and the smart car

0:16:15.720 --> 0:16:18.400
<v Speaker 1>would have to take lots of trips to deliver the

0:16:18.400 --> 0:16:22.640
<v Speaker 1>same amount of stuff. So, while both vehicles or protocols

0:16:22.960 --> 0:16:26.840
<v Speaker 1>are going at the same speed, one can finish a

0:16:26.880 --> 0:16:29.720
<v Speaker 1>given job faster than the other one because it can

0:16:29.800 --> 0:16:34.400
<v Speaker 1>carry more. So in my description of c E S earlier,

0:16:34.440 --> 0:16:38.000
<v Speaker 1>we could say that I actually jumped into a smart

0:16:38.040 --> 0:16:41.320
<v Speaker 1>car because it could take advantage of a special smart

0:16:41.360 --> 0:16:44.320
<v Speaker 1>car lane on the road and travel at the full

0:16:44.400 --> 0:16:47.760
<v Speaker 1>blistering speed of thirty miles per hour. Meanwhile, the semi

0:16:47.840 --> 0:16:51.120
<v Speaker 1>truck was stuck in the normal traffic lane, and that

0:16:51.160 --> 0:16:52.960
<v Speaker 1>one was getting backed up because there were just too

0:16:52.960 --> 0:16:56.320
<v Speaker 1>many people trying to get on that same road and

0:16:56.320 --> 0:16:59.160
<v Speaker 1>it was making traffic slow down. But because I was

0:16:59.200 --> 0:17:03.960
<v Speaker 1>in the less used older lane, I had switched from

0:17:04.000 --> 0:17:07.560
<v Speaker 1>three G t two G. Let's say I could go

0:17:08.119 --> 0:17:12.560
<v Speaker 1>pretty fast because there wasn't anyone in my way. That's

0:17:12.600 --> 0:17:15.199
<v Speaker 1>one of the things that we talked about when we're

0:17:15.200 --> 0:17:20.520
<v Speaker 1>looking at relying upon earlier generations of wireless communications technologies.

0:17:21.560 --> 0:17:25.639
<v Speaker 1>The official name for the five G radio system is

0:17:25.760 --> 0:17:28.879
<v Speaker 1>five G in R And as you may have guessed

0:17:28.960 --> 0:17:32.600
<v Speaker 1>in our stands for new radio and this new radio

0:17:32.640 --> 0:17:36.760
<v Speaker 1>standard will be incompatible with older standards. So if you

0:17:36.800 --> 0:17:39.800
<v Speaker 1>had a pure five G device, one that was only

0:17:39.840 --> 0:17:43.640
<v Speaker 1>connected to five G networks, the chip set, the antenna,

0:17:43.760 --> 0:17:46.040
<v Speaker 1>all of it is just tuned to five G, you

0:17:46.080 --> 0:17:50.560
<v Speaker 1>would probably have a pretty lousy experience. Initially because carriers

0:17:50.560 --> 0:17:53.240
<v Speaker 1>would still be building out their networks. You would have

0:17:53.800 --> 0:17:57.160
<v Speaker 1>very spotty coverage. In fact, you might even live someplace

0:17:57.200 --> 0:18:00.760
<v Speaker 1>where you'd have no coverage whatsoever because don't live within

0:18:00.960 --> 0:18:05.480
<v Speaker 1>range of a five G tower. You'd find that your

0:18:05.560 --> 0:18:08.520
<v Speaker 1>device only works in a few locations with service, and

0:18:08.560 --> 0:18:12.720
<v Speaker 1>for that reason, manufacturers are more likely to roll out

0:18:12.800 --> 0:18:16.560
<v Speaker 1>five G phones, laptops, and other devices that also contain

0:18:16.840 --> 0:18:20.800
<v Speaker 1>four G technology in them to avoid that problem, so

0:18:20.840 --> 0:18:24.480
<v Speaker 1>that your device will rely on four G networks unless

0:18:24.480 --> 0:18:26.879
<v Speaker 1>a five G network is available, in which case it

0:18:26.880 --> 0:18:28.960
<v Speaker 1>will ramp up, it'll switch on over to five G,

0:18:29.880 --> 0:18:33.119
<v Speaker 1>and otherwise they'll they'll lean very heavily on four G

0:18:33.240 --> 0:18:37.480
<v Speaker 1>in places where five G is of limited availability or reliability.

0:18:37.880 --> 0:18:41.320
<v Speaker 1>These types of networks, which continues to support these older

0:18:41.359 --> 0:18:44.760
<v Speaker 1>standards while rolling out new ones, have a name. They're

0:18:44.800 --> 0:18:48.480
<v Speaker 1>called n s A networks. Now in this case, the

0:18:48.800 --> 0:18:52.119
<v Speaker 1>n essay does not refer to the spy agency in

0:18:52.160 --> 0:18:56.960
<v Speaker 1>the United States that's looking at all electronic communications. Instead,

0:18:57.600 --> 0:19:01.720
<v Speaker 1>it means non stand alone, meaning the network must pair

0:19:01.800 --> 0:19:07.360
<v Speaker 1>one wireless technology with at least one other wireless technology. Eventually,

0:19:07.920 --> 0:19:12.120
<v Speaker 1>as these networks become more robust, they can sunset the

0:19:12.200 --> 0:19:17.800
<v Speaker 1>older wireless communications standards and become standalone or s A networks.

0:19:18.200 --> 0:19:20.520
<v Speaker 1>We're starting to see this happen right now. In fact,

0:19:20.560 --> 0:19:24.560
<v Speaker 1>some companies have already shut down their two G networks

0:19:24.600 --> 0:19:27.760
<v Speaker 1>and sunset them. Those are no longer supported. Others are

0:19:27.800 --> 0:19:30.120
<v Speaker 1>still supporting the two G networks but planned to shut

0:19:30.160 --> 0:19:32.480
<v Speaker 1>them down in the near future. I believe T Mobile

0:19:33.040 --> 0:19:36.159
<v Speaker 1>has extended operations until twenty twenty, but then is going

0:19:36.200 --> 0:19:39.880
<v Speaker 1>to shut down it's two G network. For example, there

0:19:39.920 --> 0:19:43.879
<v Speaker 1>are three main goals for five G technology. One is

0:19:43.880 --> 0:19:48.160
<v Speaker 1>to have even greater data transfer rates, and like previous generations,

0:19:48.200 --> 0:19:51.440
<v Speaker 1>will likely see a range of data transfer rates rollout

0:19:51.520 --> 0:19:55.520
<v Speaker 1>in various networks. The actual experience will depend upon lots

0:19:55.520 --> 0:19:58.720
<v Speaker 1>of different factors, such as the design of the network,

0:19:59.000 --> 0:20:02.320
<v Speaker 1>the actual device or using the number of other devices

0:20:02.359 --> 0:20:05.399
<v Speaker 1>that are on that network, the communications frequency that the

0:20:05.440 --> 0:20:08.120
<v Speaker 1>network is relying upon and your device is relying upon,

0:20:08.160 --> 0:20:10.439
<v Speaker 1>and so on. So it's really hard to give a

0:20:10.480 --> 0:20:13.639
<v Speaker 1>solid number to what five G speeds will mean. That

0:20:13.720 --> 0:20:16.639
<v Speaker 1>being said, let's at least get some ballpark figures in

0:20:16.680 --> 0:20:20.440
<v Speaker 1>here or else it's no use whatsoever. In February two eighteen,

0:20:20.440 --> 0:20:24.560
<v Speaker 1>at the Mobile World Congress, Qualcom released the results of

0:20:24.600 --> 0:20:28.119
<v Speaker 1>some five G simulation tests it had conducted in an

0:20:28.119 --> 0:20:31.359
<v Speaker 1>effort to see what we might expect from five G

0:20:32.280 --> 0:20:35.960
<v Speaker 1>in the early early days in areas like Frankfurt or

0:20:36.000 --> 0:20:40.960
<v Speaker 1>in San Francisco, California. The simulation took into account cell

0:20:41.040 --> 0:20:44.479
<v Speaker 1>tower locations that are already in those cities and the

0:20:44.560 --> 0:20:47.480
<v Speaker 1>frequency allocations that would be allowed in those cities. In

0:20:47.520 --> 0:20:50.800
<v Speaker 1>other words, what parts of the radio spectrum would carriers

0:20:50.800 --> 0:20:54.000
<v Speaker 1>be allowed to use. Because five G technology doesn't work

0:20:54.000 --> 0:20:58.119
<v Speaker 1>across the entire radio spectrum. They're specific bands frequency bands

0:20:58.160 --> 0:21:01.160
<v Speaker 1>that five G is focused on. And it also accounted

0:21:01.200 --> 0:21:05.440
<v Speaker 1>for differences in connectivity strength and geography. So the simulation

0:21:05.480 --> 0:21:09.240
<v Speaker 1>focused on what Qualcom considered to be a reasonable expectation

0:21:09.320 --> 0:21:12.160
<v Speaker 1>of a five gene network rollout in the short term.

0:21:12.480 --> 0:21:15.320
<v Speaker 1>So we're talking like they're saying, well, a year from now,

0:21:15.400 --> 0:21:19.159
<v Speaker 1>assuming we roll these these uh systems out, here's what

0:21:19.200 --> 0:21:22.080
<v Speaker 1>we could expect at the end of that year. So

0:21:22.160 --> 0:21:25.159
<v Speaker 1>with all of that said, Qualcom found that the Frankfurt

0:21:25.320 --> 0:21:28.840
<v Speaker 1>simulation saw an increase from fifty six megabits per second

0:21:29.160 --> 0:21:32.640
<v Speaker 1>on a four G network to four hundred ninety megabits

0:21:32.720 --> 0:21:35.280
<v Speaker 1>per second for five G, which is a big jump,

0:21:35.760 --> 0:21:38.800
<v Speaker 1>but it's lagging behind some of the more advanced LTE

0:21:39.040 --> 0:21:42.120
<v Speaker 1>four G systems that are deploying today in other parts

0:21:42.160 --> 0:21:44.639
<v Speaker 1>of the world. So, in other words, we already have

0:21:45.000 --> 0:21:49.159
<v Speaker 1>four G systems that deliver data at that rate or

0:21:49.240 --> 0:21:53.080
<v Speaker 1>even higher. So you say, you could say, yes, the

0:21:53.119 --> 0:21:55.720
<v Speaker 1>five G and Frankfort would be an improvement, but it's

0:21:55.720 --> 0:21:59.680
<v Speaker 1>still lagging behind other four G tech. The San Francisco

0:21:59.680 --> 0:22:03.360
<v Speaker 1>simulation saw browsing speed go from seventy one megabits per

0:22:03.400 --> 0:22:07.520
<v Speaker 1>second on four G to one point four gigabits per

0:22:07.560 --> 0:22:12.040
<v Speaker 1>second for five G, so it's on even greater increase

0:22:12.160 --> 0:22:16.359
<v Speaker 1>on data transfer rates. In the simulation, median five G

0:22:16.600 --> 0:22:20.320
<v Speaker 1>users could watch streaming video at eight K resolution running

0:22:20.359 --> 0:22:23.359
<v Speaker 1>at one hundred twenty frames per second, which is pretty

0:22:23.440 --> 0:22:27.240
<v Speaker 1>darn impressive. But just to get a bigger picture of everything.

0:22:27.480 --> 0:22:29.560
<v Speaker 1>While all this is going on, while we're seeing this

0:22:29.640 --> 0:22:33.080
<v Speaker 1>five G rollout happening, we're also seeing the four G

0:22:33.240 --> 0:22:37.560
<v Speaker 1>networks continue to get enhancements. Qual Calm is rolling out

0:22:37.600 --> 0:22:39.760
<v Speaker 1>the X twenty four modem, which is going to be

0:22:39.800 --> 0:22:43.400
<v Speaker 1>in several smartphones in twenty nineteen. That is a four

0:22:43.480 --> 0:22:46.600
<v Speaker 1>G technology, but it has the ability to support data

0:22:46.640 --> 0:22:50.560
<v Speaker 1>transfer rates of up to two gigabits per second. Keep

0:22:50.560 --> 0:22:52.959
<v Speaker 1>in mind, the simulation for five G maxed out at

0:22:53.000 --> 0:22:57.120
<v Speaker 1>one point four gigabits per second, so this older four

0:22:57.200 --> 0:23:00.679
<v Speaker 1>G technology would have an even better data transfer rate,

0:23:00.720 --> 0:23:05.240
<v Speaker 1>at least in an ideal implementation. Now, in the real world,

0:23:06.280 --> 0:23:08.960
<v Speaker 1>we're probably not going to see anyone actually experienced that

0:23:09.080 --> 0:23:11.680
<v Speaker 1>kind of speed, but at least in theory, the devices

0:23:11.680 --> 0:23:14.439
<v Speaker 1>could support them. This is another example of how the

0:23:14.560 --> 0:23:18.760
<v Speaker 1>late phase for one generation of wireless communication can sometimes

0:23:18.800 --> 0:23:23.840
<v Speaker 1>outperform the early phase of the succeeding generation. Now, over time,

0:23:24.000 --> 0:23:26.760
<v Speaker 1>the five G system will leave four G in the dust.

0:23:27.359 --> 0:23:30.120
<v Speaker 1>It's not uncommon to see predictions of data transfer rates

0:23:30.200 --> 0:23:33.960
<v Speaker 1>hitting ten gigabits per second or faster, which is hard

0:23:34.000 --> 0:23:38.000
<v Speaker 1>for me to imagine, but that's always the case early on,

0:23:38.119 --> 0:23:41.920
<v Speaker 1>before these technologies become part of our daily lives. And besides,

0:23:42.200 --> 0:23:45.399
<v Speaker 1>we might never actually see our own experience match that

0:23:45.520 --> 0:23:48.879
<v Speaker 1>predicted result. But if we do, what would that mean. Well,

0:23:49.160 --> 0:23:51.800
<v Speaker 1>at ten gigabits per second, you can download a full

0:23:52.000 --> 0:23:57.200
<v Speaker 1>four K definition feature length film in about twenty five seconds.

0:23:57.680 --> 0:24:02.320
<v Speaker 1>I'm not talking about streaming. I'm talking about downloading Yawza.

0:24:02.600 --> 0:24:05.480
<v Speaker 1>The second big feature of five G is a reduction

0:24:05.680 --> 0:24:09.879
<v Speaker 1>in response time or reduction in latency. Latency refers to

0:24:09.880 --> 0:24:12.840
<v Speaker 1>the lag you experience between when you activate something and

0:24:12.840 --> 0:24:16.400
<v Speaker 1>when that's something actually happens. In video games, we would

0:24:16.400 --> 0:24:19.479
<v Speaker 1>say something like the lag between pushing a jump button

0:24:19.800 --> 0:24:23.600
<v Speaker 1>and having Mario actually jump is latency. In the equal

0:24:23.720 --> 0:24:27.840
<v Speaker 1>Calm San Francisco simulation I mentioned earlier, the company observed

0:24:27.880 --> 0:24:32.000
<v Speaker 1>a response time that was twenty three times faster than

0:24:32.040 --> 0:24:36.000
<v Speaker 1>the median four G experience, which means latency would be

0:24:36.040 --> 0:24:40.240
<v Speaker 1>reduced dramatically. That means five G could become the technology

0:24:40.280 --> 0:24:44.640
<v Speaker 1>we rely upon for time critical applications. So, for example,

0:24:44.960 --> 0:24:48.199
<v Speaker 1>autonomous cars that might rely at least in part on

0:24:48.240 --> 0:24:51.439
<v Speaker 1>a networked system could run on five G. When the

0:24:51.440 --> 0:24:54.920
<v Speaker 1>information you're requesting is needed to operate a vehicle that's

0:24:55.040 --> 0:24:59.359
<v Speaker 1>driving at driving speed in traffic, latency is something you

0:24:59.480 --> 0:25:02.920
<v Speaker 1>really have to eliminate as quickly as you possibly can. Now.

0:25:02.960 --> 0:25:05.600
<v Speaker 1>I don't expect we're going to see driverless cars switch

0:25:05.760 --> 0:25:09.440
<v Speaker 1>entirely to some sort of cloud based operating system where

0:25:09.480 --> 0:25:12.560
<v Speaker 1>you have a centralized data center that's making all the

0:25:12.640 --> 0:25:15.400
<v Speaker 1>decisions for all the cars that are on the road.

0:25:16.040 --> 0:25:18.600
<v Speaker 1>But I do imagine the driverless cars of the future

0:25:18.640 --> 0:25:22.880
<v Speaker 1>will balance on board systems that process information right there

0:25:22.920 --> 0:25:26.680
<v Speaker 1>inside the car itself with support systems that live in

0:25:26.720 --> 0:25:30.600
<v Speaker 1>the cloud. So we've got better data transfer rates and

0:25:30.640 --> 0:25:33.800
<v Speaker 1>we've got faster response times. As the first two big

0:25:33.880 --> 0:25:37.119
<v Speaker 1>features of five G. The third one is that the

0:25:37.240 --> 0:25:40.000
<v Speaker 1>five G systems will be able to handle many more

0:25:40.119 --> 0:25:44.439
<v Speaker 1>devices connected to an individual system at the same time,

0:25:44.720 --> 0:25:48.600
<v Speaker 1>and this is absolutely necessary as the Internet of things

0:25:48.640 --> 0:25:52.719
<v Speaker 1>trends shows no sign of slowing down. I'll explain more

0:25:52.720 --> 0:25:55.600
<v Speaker 1>in just a second, but first let's take another quick break.

0:26:02.960 --> 0:26:06.080
<v Speaker 1>It's pretty hard to get a reckoning on the number

0:26:06.080 --> 0:26:09.280
<v Speaker 1>of devices that are connected to the Internet, but it's

0:26:09.280 --> 0:26:12.520
<v Speaker 1>a lot. According to Statista, by the end of two

0:26:12.560 --> 0:26:17.280
<v Speaker 1>thousand eighteen, there were twenty three point fourteen billion Internet

0:26:17.280 --> 0:26:20.159
<v Speaker 1>of Things devices connected to the network of networks in

0:26:20.240 --> 0:26:24.600
<v Speaker 1>some fashion. That same site estimates that by five there

0:26:24.640 --> 0:26:28.560
<v Speaker 1>will be more than seventy five billion IoT gadgets connected

0:26:28.600 --> 0:26:32.040
<v Speaker 1>to the Internet. But that's just one estimation and other

0:26:32.119 --> 0:26:36.080
<v Speaker 1>sources have different numbers. There is something that's in common

0:26:36.119 --> 0:26:40.000
<v Speaker 1>with all those different numbers, they're all real, real big,

0:26:40.520 --> 0:26:43.880
<v Speaker 1>So they may not all specifically agree on how many

0:26:43.960 --> 0:26:47.000
<v Speaker 1>billion devices are connected to the Internet, but they all

0:26:47.040 --> 0:26:50.600
<v Speaker 1>agree that it is many billion, and it's just gonna

0:26:50.640 --> 0:26:54.560
<v Speaker 1>get bigger. To support all those devices, providers have to

0:26:54.560 --> 0:26:58.680
<v Speaker 1>build out network capacity. Otherwise you would find it impossible

0:26:58.760 --> 0:27:02.720
<v Speaker 1>to use your phone because is there too many doorbells, cameras, thermostats,

0:27:02.720 --> 0:27:06.240
<v Speaker 1>and refrigerators connected to the networks. Actually, to be fair,

0:27:06.280 --> 0:27:08.840
<v Speaker 1>that's a bit of an oversimplification because the way we

0:27:08.920 --> 0:27:11.679
<v Speaker 1>tend to connect devices to the Internet through stuff like

0:27:11.840 --> 0:27:15.239
<v Speaker 1>local area networks and routers, and it ignores stuff like

0:27:15.280 --> 0:27:18.520
<v Speaker 1>the specific frequency bands that the devices and systems are using.

0:27:18.520 --> 0:27:21.040
<v Speaker 1>But the point is pretty valid. You get to a

0:27:21.040 --> 0:27:25.439
<v Speaker 1>point where networks, whether they are local or wide area,

0:27:25.760 --> 0:27:29.960
<v Speaker 1>or the Internet itself, end up getting congested. Now you've

0:27:30.040 --> 0:27:33.600
<v Speaker 1>likely heard about Verizon or A T and T talking

0:27:33.680 --> 0:27:37.320
<v Speaker 1>up some of their technologies as five G, but five

0:27:37.440 --> 0:27:41.240
<v Speaker 1>G as a fully mature technology has not really rolled

0:27:41.240 --> 0:27:45.199
<v Speaker 1>out yet as I'm recording this podcast in February two, nineteen,

0:27:45.240 --> 0:27:48.960
<v Speaker 1>and we're probably not going to see any real serious,

0:27:49.040 --> 0:27:53.399
<v Speaker 1>widespread deployment until twenty twenty. There'll be some in twenty

0:27:53.520 --> 0:27:57.840
<v Speaker 1>nineteen some pilot programs, but as far as national coverage,

0:27:57.880 --> 0:28:01.160
<v Speaker 1>we may be looking at twenty maybe twin twenty one.

0:28:01.880 --> 0:28:04.240
<v Speaker 1>Even then, it's going to be a gradual rollout, and

0:28:04.280 --> 0:28:06.359
<v Speaker 1>it's going to take time to reach a lot of

0:28:06.400 --> 0:28:09.840
<v Speaker 1>different service areas. Dense urban environments will get it first

0:28:10.080 --> 0:28:12.879
<v Speaker 1>most likely, but the further out you are from one

0:28:12.920 --> 0:28:15.240
<v Speaker 1>of those, the longer it may take before you get

0:28:15.280 --> 0:28:17.520
<v Speaker 1>this coverage. So it's going to be a few years

0:28:17.560 --> 0:28:20.480
<v Speaker 1>before most of us can regularly take advantage of five G.

0:28:20.920 --> 0:28:23.119
<v Speaker 1>And on top of that, it's going to take another

0:28:23.200 --> 0:28:26.560
<v Speaker 1>few years for developers to create the apps and services

0:28:26.600 --> 0:28:29.679
<v Speaker 1>that will give value to the five G technology. I

0:28:29.760 --> 0:28:33.199
<v Speaker 1>say this pretty confidently because that's how it's unrolled in

0:28:33.280 --> 0:28:38.320
<v Speaker 1>previous generations. When four G came out in it took

0:28:38.360 --> 0:28:41.720
<v Speaker 1>about three years for services like video calls to really

0:28:41.760 --> 0:28:45.480
<v Speaker 1>mature and take advantage of four G technology, which makes sense,

0:28:45.520 --> 0:28:47.080
<v Speaker 1>you know, it takes a few years for developers to

0:28:47.080 --> 0:28:50.800
<v Speaker 1>figure out how they can best leverage the platform. So

0:28:51.240 --> 0:28:53.640
<v Speaker 1>what is going on with these five G claims from

0:28:53.760 --> 0:28:58.080
<v Speaker 1>A T and T and Verizon, Well, it's largely marketing speak,

0:28:58.840 --> 0:29:01.680
<v Speaker 1>specifically more so with A T and T than Verizon.

0:29:01.720 --> 0:29:04.880
<v Speaker 1>But I'll explain. I think, as this episode is making clear,

0:29:04.960 --> 0:29:07.960
<v Speaker 1>the whole wireless generation thing is super confusing to the

0:29:08.000 --> 0:29:11.600
<v Speaker 1>average person. On the one hand, these companies are offering

0:29:11.640 --> 0:29:16.160
<v Speaker 1>up technologies and services that push beyond the median experience

0:29:16.280 --> 0:29:19.360
<v Speaker 1>of four G on their networks. On the other hand,

0:29:19.560 --> 0:29:22.880
<v Speaker 1>they're doing so with technologies that are not completely five G.

0:29:23.440 --> 0:29:24.800
<v Speaker 1>So you can think of it as saying that the

0:29:24.840 --> 0:29:29.080
<v Speaker 1>tech gives users access to five G speeds but isn't

0:29:29.120 --> 0:29:33.160
<v Speaker 1>actually fully five G itself. So let's start with a

0:29:33.240 --> 0:29:35.320
<v Speaker 1>T and T. The company is marketing some of its

0:29:35.320 --> 0:29:39.600
<v Speaker 1>advanced four G phones as five G E, and the

0:29:39.680 --> 0:29:43.959
<v Speaker 1>E stands for evolution. But these five G E phones

0:29:44.000 --> 0:29:47.880
<v Speaker 1>won't actually support five G wireless communication, and that's what

0:29:48.000 --> 0:29:51.760
<v Speaker 1>has some folks upset. The implication is that these phones

0:29:51.800 --> 0:29:55.800
<v Speaker 1>will run on frequencies and networks that enable really strong

0:29:56.000 --> 0:29:59.040
<v Speaker 1>data transfer rates, but that's not the same thing as

0:29:59.120 --> 0:30:03.720
<v Speaker 1>running on actual five G technology. Instead, five G E

0:30:03.960 --> 0:30:08.320
<v Speaker 1>is really LTE advanced. It is capable of supporting data

0:30:08.360 --> 0:30:12.000
<v Speaker 1>transfer speeds of around forty megabits per second. To be

0:30:12.080 --> 0:30:14.600
<v Speaker 1>fair to a T and T, this isn't an unprecedented

0:30:14.840 --> 0:30:18.440
<v Speaker 1>marketing move. T Mobile did the same thing when it

0:30:18.560 --> 0:30:22.200
<v Speaker 1>rolled out an h s P A plus technology. This

0:30:22.320 --> 0:30:25.320
<v Speaker 1>was a three G technology that it rolled out, but

0:30:25.440 --> 0:30:29.000
<v Speaker 1>it was much faster than the older three G technology

0:30:29.080 --> 0:30:32.640
<v Speaker 1>T Mobile had previously deployed, so the company decided to

0:30:32.680 --> 0:30:36.720
<v Speaker 1>market it as four G, even though the technical specification

0:30:36.800 --> 0:30:39.800
<v Speaker 1>meant it was still three G. A T and T,

0:30:39.920 --> 0:30:42.840
<v Speaker 1>by the way, back in those days criticized T Mobile

0:30:42.880 --> 0:30:46.000
<v Speaker 1>for doing this and saying that they made things less

0:30:46.000 --> 0:30:49.760
<v Speaker 1>transparent and less understandable to customers. But then A T

0:30:49.880 --> 0:30:52.000
<v Speaker 1>and T did the same thing with its own hsp

0:30:52.160 --> 0:30:55.120
<v Speaker 1>A plus network and said that that was also four G.

0:30:55.400 --> 0:31:01.239
<v Speaker 1>So yeah, and people wonder why these topics are so

0:31:01.320 --> 0:31:06.440
<v Speaker 1>difficult to explain. Even without this marketing misinformation, it's hard

0:31:06.520 --> 0:31:09.800
<v Speaker 1>to talk about this stuff. Verizon, by the way, their

0:31:09.840 --> 0:31:14.320
<v Speaker 1>five G offering isn't for phones. It's instead for home networks,

0:31:14.360 --> 0:31:18.959
<v Speaker 1>So this is a home network solution instead of getting

0:31:19.000 --> 0:31:23.680
<v Speaker 1>say fiber to your house or copper. In many cases,

0:31:23.720 --> 0:31:26.040
<v Speaker 1>I'm still running on copper. I don't have fiber optics

0:31:26.040 --> 0:31:29.960
<v Speaker 1>at my house yet. Verizon's five G offering is also

0:31:30.040 --> 0:31:33.880
<v Speaker 1>not true five G, but it's a lot closer to

0:31:33.960 --> 0:31:35.960
<v Speaker 1>it than a T and T is it's using some

0:31:36.080 --> 0:31:38.880
<v Speaker 1>of the technologies that are part of the five G approach,

0:31:39.280 --> 0:31:41.720
<v Speaker 1>so it has lower latency, it has pretty good data

0:31:41.800 --> 0:31:46.640
<v Speaker 1>transfer rates, but it does not use the five G

0:31:47.120 --> 0:31:51.960
<v Speaker 1>in OUR communications standard. Instead, it relies upon a communication

0:31:52.040 --> 0:31:57.440
<v Speaker 1>standard that Verizon itself made called five G t F. Eventually,

0:31:57.760 --> 0:32:01.360
<v Speaker 1>Verizon plans to switch over to the industry agreed upon

0:32:01.640 --> 0:32:04.400
<v Speaker 1>upon standard of in OUR. That's going to require a

0:32:04.480 --> 0:32:10.520
<v Speaker 1>Verizon to actually switch out physical equipment at different stations

0:32:10.680 --> 0:32:13.400
<v Speaker 1>around its service area. So it's going to be a

0:32:13.400 --> 0:32:16.959
<v Speaker 1>big investment on the part of the company. So I

0:32:17.000 --> 0:32:21.840
<v Speaker 1>guess Verizon was weighing decisions. Does it go forward rolling

0:32:21.840 --> 0:32:25.400
<v Speaker 1>out this sort of temporary patch knowing that it's going

0:32:25.440 --> 0:32:27.800
<v Speaker 1>to have to undo that work in the future to

0:32:28.360 --> 0:32:34.560
<v Speaker 1>upgrade to in OUR standards, or does it wait and

0:32:34.640 --> 0:32:37.960
<v Speaker 1>try to just move with the industry to adopt in our.

0:32:38.480 --> 0:32:41.680
<v Speaker 1>The benefit of going forward is that you get an

0:32:41.760 --> 0:32:46.720
<v Speaker 1>early hit at those consumers who want to have those

0:32:46.760 --> 0:32:51.280
<v Speaker 1>five G features as soon as they possibly can. But

0:32:51.400 --> 0:32:53.240
<v Speaker 1>the danger is you're going to have to spend a

0:32:53.240 --> 0:32:56.400
<v Speaker 1>lot of money to change out all that equipment. Verizon,

0:32:56.480 --> 0:32:58.240
<v Speaker 1>for its part, is said they're not going to pass

0:32:58.280 --> 0:33:01.240
<v Speaker 1>those costs down to customers. They're gonna see a big

0:33:01.280 --> 0:33:05.719
<v Speaker 1>bump in their subscription uh fees in order for Verizon

0:33:05.800 --> 0:33:08.240
<v Speaker 1>to go in and change out all this equipment once

0:33:08.320 --> 0:33:10.680
<v Speaker 1>it's once the company has decided that the in our

0:33:10.800 --> 0:33:14.160
<v Speaker 1>standard is established enough for them to make this change.

0:33:14.200 --> 0:33:16.880
<v Speaker 1>There's also no guarantee of when that will happen, so

0:33:17.120 --> 0:33:21.560
<v Speaker 1>a lot of unanswered questions still. Alright, well, I put

0:33:21.600 --> 0:33:23.640
<v Speaker 1>it off as long as I possibly could, but it

0:33:23.720 --> 0:33:26.040
<v Speaker 1>is time to talk about what actually will make five

0:33:26.120 --> 0:33:28.440
<v Speaker 1>G work. I'm going to do this from a very

0:33:28.760 --> 0:33:33.480
<v Speaker 1>very high level bird's eye view is probably too low

0:33:33.520 --> 0:33:37.800
<v Speaker 1>of an altitude, let's say a satellite view of the technology. So,

0:33:38.840 --> 0:33:43.200
<v Speaker 1>like earlier generations of cellular technology, five GEN networks have

0:33:43.600 --> 0:33:47.480
<v Speaker 1>cell sites that cover a territory. The territory is divided

0:33:47.560 --> 0:33:52.360
<v Speaker 1>up into sectors. Moving through sectors needs to be seamless

0:33:52.520 --> 0:33:54.880
<v Speaker 1>for the end user. So for me and you, whenever

0:33:54.920 --> 0:33:58.120
<v Speaker 1>we're moving around, we want to make sure that we

0:33:58.200 --> 0:34:01.280
<v Speaker 1>don't notice when we pass them one sector to the next.

0:34:01.320 --> 0:34:03.400
<v Speaker 1>If I'm on a phone call with you and I

0:34:03.440 --> 0:34:05.480
<v Speaker 1>happen to be riding in the back of a car

0:34:05.800 --> 0:34:09.040
<v Speaker 1>and I'm not really concerned with how irritating it might

0:34:09.080 --> 0:34:11.040
<v Speaker 1>be for me to be on a phone conversation while

0:34:11.080 --> 0:34:13.560
<v Speaker 1>someone else is driving. I'm chatting with you. I don't

0:34:13.560 --> 0:34:16.040
<v Speaker 1>want there to be any interruption in our phone call

0:34:16.440 --> 0:34:18.880
<v Speaker 1>as the car travels from one side of a city

0:34:18.920 --> 0:34:21.239
<v Speaker 1>to the other, and while it's doing that, it's going

0:34:21.280 --> 0:34:24.080
<v Speaker 1>to be passing through these sectors. This was sort of

0:34:24.120 --> 0:34:27.440
<v Speaker 1>the basis of the cellular technology approach, this idea that

0:34:27.840 --> 0:34:32.000
<v Speaker 1>there needs to be this this handshake in between cell

0:34:32.080 --> 0:34:36.399
<v Speaker 1>towers that allows the seamless transition of a call from

0:34:36.440 --> 0:34:39.480
<v Speaker 1>one tower to the next. And it's a pretty complicated

0:34:39.520 --> 0:34:42.120
<v Speaker 1>technology I've talked about in previous episodes of tech Stuff,

0:34:42.160 --> 0:34:45.000
<v Speaker 1>so we're not gonna go into more detail, but just

0:34:45.040 --> 0:34:47.520
<v Speaker 1>to say that five G is built on that same

0:34:47.560 --> 0:34:51.480
<v Speaker 1>sort of foundation, this idea of cells that represent a

0:34:51.520 --> 0:34:54.560
<v Speaker 1>certain area of service and that those cells can hand

0:34:54.680 --> 0:34:59.000
<v Speaker 1>off service to neighboring cells as a person is moving

0:34:59.040 --> 0:35:03.319
<v Speaker 1>through the different set There's so an important part of

0:35:03.360 --> 0:35:07.000
<v Speaker 1>the technology. The cells sites have to connect to a

0:35:07.120 --> 0:35:11.440
<v Speaker 1>network backbone. They themselves aren't just magical conversation, you know,

0:35:11.640 --> 0:35:15.839
<v Speaker 1>telecommunications points. They have to connect to a a larger

0:35:16.080 --> 0:35:20.680
<v Speaker 1>communications network. That connection can be wired, or it can

0:35:20.719 --> 0:35:25.680
<v Speaker 1>be wireless. Five G will use wider bandwidths of frequencies

0:35:25.680 --> 0:35:29.400
<v Speaker 1>than four G did, but the encoding for data across

0:35:29.480 --> 0:35:32.680
<v Speaker 1>the five G networks is similar to that of four G.

0:35:32.920 --> 0:35:36.279
<v Speaker 1>It's called O F d M. But there's really no

0:35:36.440 --> 0:35:38.600
<v Speaker 1>need for us to get into that too deeply. It

0:35:38.640 --> 0:35:41.480
<v Speaker 1>gets way too technical and it becomes nearly impossible to

0:35:41.520 --> 0:35:44.880
<v Speaker 1>talk about without visual aids. It's just important to remember

0:35:44.920 --> 0:35:48.200
<v Speaker 1>this is the methodology by which five G will convert

0:35:49.160 --> 0:35:53.680
<v Speaker 1>data into signals and then from signals back into data.

0:35:54.760 --> 0:35:57.799
<v Speaker 1>I know that signals are kind of a kind of data,

0:35:57.840 --> 0:35:59.680
<v Speaker 1>but you don't understand what I mean. It's for the

0:35:59.680 --> 0:36:02.719
<v Speaker 1>trend mission of that data. Five G is going to

0:36:02.800 --> 0:36:06.120
<v Speaker 1>run on two bands of frequencies that are on either

0:36:06.200 --> 0:36:09.919
<v Speaker 1>side of six giga hurts um, but by other either side,

0:36:09.960 --> 0:36:12.439
<v Speaker 1>I mean significantly on either side of six gig hurts.

0:36:12.480 --> 0:36:15.120
<v Speaker 1>Six gig hurts is kind of the dividing line between them.

0:36:15.200 --> 0:36:20.000
<v Speaker 1>So it hurts is one wave cycle per second, So

0:36:20.080 --> 0:36:23.360
<v Speaker 1>if you have a wave that's going at one hurts,

0:36:23.480 --> 0:36:27.439
<v Speaker 1>it means it takes a full second for one wave

0:36:27.520 --> 0:36:30.759
<v Speaker 1>length to pass through a given point. You've identified a

0:36:30.800 --> 0:36:35.240
<v Speaker 1>point you're measuring how many radio waves passed that point

0:36:35.280 --> 0:36:38.680
<v Speaker 1>in one second. You count one, that's one hurts. Six

0:36:38.719 --> 0:36:42.120
<v Speaker 1>giga hurts would be a frequency in which six billion

0:36:42.360 --> 0:36:46.879
<v Speaker 1>wave cycles pass a given point every second. The low

0:36:46.960 --> 0:36:51.840
<v Speaker 1>frequency networks will operate within existing WiFi and cellular bands,

0:36:51.880 --> 0:36:54.960
<v Speaker 1>so at that wavelength, signals can travel the same distance

0:36:55.080 --> 0:36:57.719
<v Speaker 1>as what we use today. The nice thing about that

0:36:57.800 --> 0:36:59.880
<v Speaker 1>means you don't have to build out a ton of

0:37:00.120 --> 0:37:02.840
<v Speaker 1>new cells to get the same coverage. You could actually

0:37:02.880 --> 0:37:07.320
<v Speaker 1>add equipment to existing cell towers to support five G

0:37:08.120 --> 0:37:11.000
<v Speaker 1>because you can transmit just as far as you could

0:37:11.000 --> 0:37:17.160
<v Speaker 1>with the four G methodology. However, those frequencies aren't able

0:37:17.200 --> 0:37:19.920
<v Speaker 1>to carry quite as much data on them as the

0:37:19.960 --> 0:37:26.080
<v Speaker 1>high frequencies ones can, so you won't get crazy fast

0:37:26.560 --> 0:37:30.520
<v Speaker 1>or a crazy huge data transfer rates. They would still

0:37:30.560 --> 0:37:34.840
<v Speaker 1>probably be better than four G, but not the enormous,

0:37:34.840 --> 0:37:37.600
<v Speaker 1>incredible potential ones we've heard about, but we would still

0:37:37.640 --> 0:37:44.240
<v Speaker 1>probably see data transfer rates that are better than LTE. However,

0:37:44.280 --> 0:37:47.160
<v Speaker 1>the high frequency five G tech is a different story.

0:37:47.560 --> 0:37:51.640
<v Speaker 1>It will rely on millimeter wave frequencies around the twenty

0:37:51.680 --> 0:37:55.279
<v Speaker 1>eight and thirty nine giga hurts bands because that's where

0:37:55.320 --> 0:37:58.680
<v Speaker 1>there's a whole lot of space for big communications channels

0:37:59.000 --> 0:38:01.879
<v Speaker 1>that can carry huge amounts of data very quickly. These

0:38:01.960 --> 0:38:05.799
<v Speaker 1>radio waves can't travel as far with enough power to

0:38:05.840 --> 0:38:10.239
<v Speaker 1>be as reliable as the lower frequency variant can, so

0:38:10.280 --> 0:38:12.520
<v Speaker 1>in other words, they don't have as great a range

0:38:12.920 --> 0:38:16.600
<v Speaker 1>of transmission, which means companies wouldn't have to probably build

0:38:16.600 --> 0:38:21.279
<v Speaker 1>out a lot more five G cells to make their

0:38:21.320 --> 0:38:25.080
<v Speaker 1>network have enough coverage. On the flip side, these cells

0:38:25.120 --> 0:38:28.080
<v Speaker 1>wouldn't have to be nearly as powerful as the cell

0:38:28.120 --> 0:38:31.480
<v Speaker 1>towers we rely upon today. They could actually require much

0:38:31.600 --> 0:38:34.480
<v Speaker 1>less power to operate, so instead of using a few

0:38:34.560 --> 0:38:38.720
<v Speaker 1>high powered cellular antenna towers to cover a given region,

0:38:39.200 --> 0:38:42.680
<v Speaker 1>you would have a whole bunch of low power, high

0:38:42.800 --> 0:38:47.640
<v Speaker 1>frequency transmitters. For some regions, like densely populated urban areas,

0:38:47.960 --> 0:38:51.319
<v Speaker 1>many of the carriers out there have already built out

0:38:51.400 --> 0:38:53.840
<v Speaker 1>the infrastructure that could support this type of five G.

0:38:54.600 --> 0:38:58.239
<v Speaker 1>They're already these additional cell towers that could just have

0:38:58.320 --> 0:39:02.279
<v Speaker 1>five G tacked onto them and the infrastructure is good

0:39:02.280 --> 0:39:05.279
<v Speaker 1>to go. However, in other areas, like in suburbs, once

0:39:05.320 --> 0:39:08.719
<v Speaker 1>you move out of these densely populated areas, it can

0:39:08.760 --> 0:39:11.719
<v Speaker 1>get harder to get the permission necessary to build out

0:39:11.719 --> 0:39:14.560
<v Speaker 1>the infrastructure. There are a lot of communities that don't

0:39:14.640 --> 0:39:19.200
<v Speaker 1>want to have these these transmission towers erected in their community.

0:39:19.280 --> 0:39:22.800
<v Speaker 1>It's sort of that not in my backyard, the Nimbigi principle.

0:39:22.880 --> 0:39:25.480
<v Speaker 1>I don't want that to be on the top of

0:39:25.520 --> 0:39:28.080
<v Speaker 1>this building. It's too close to my house. That kind

0:39:28.080 --> 0:39:31.719
<v Speaker 1>of thing. So this isn't a technical challenge. This is

0:39:31.760 --> 0:39:35.160
<v Speaker 1>a social or political challenge that companies are going to

0:39:35.200 --> 0:39:38.520
<v Speaker 1>have to overcome to have a good five G deployment

0:39:38.560 --> 0:39:41.919
<v Speaker 1>if they want to use these high frequencies. Now, as

0:39:41.920 --> 0:39:44.880
<v Speaker 1>I record this, a T and T is pre prepping.

0:39:44.920 --> 0:39:48.080
<v Speaker 1>It's a true five G rollout in a few select cities,

0:39:48.440 --> 0:39:51.320
<v Speaker 1>and it will be of modest size and will likely

0:39:51.360 --> 0:39:53.680
<v Speaker 1>only see a few phones in two thousand nineteen that

0:39:53.719 --> 0:39:57.319
<v Speaker 1>actually support five G technology. But at least we could

0:39:57.320 --> 0:40:00.200
<v Speaker 1>say those phones and services will be true five G

0:40:00.920 --> 0:40:03.719
<v Speaker 1>rather than four G that happens to be marketed as

0:40:03.719 --> 0:40:06.759
<v Speaker 1>if it were five G, and five G could really

0:40:06.800 --> 0:40:10.040
<v Speaker 1>transform how we get internet at home. If carriers can

0:40:10.040 --> 0:40:12.960
<v Speaker 1>get permission to build out those five G networks and

0:40:13.080 --> 0:40:17.400
<v Speaker 1>provide coverage, they can run fiber to specific cell sites

0:40:17.440 --> 0:40:20.920
<v Speaker 1>to those cell towers, they could connect those by fiber

0:40:21.000 --> 0:40:24.080
<v Speaker 1>to the network backbone, and then they can use wireless

0:40:24.080 --> 0:40:28.200
<v Speaker 1>transmissions to deliver internet service to customer homes, so there's

0:40:28.239 --> 0:40:32.240
<v Speaker 1>no need to run fiber out to the actual customer homes.

0:40:32.239 --> 0:40:37.160
<v Speaker 1>This cuts way down on cost. Uh. It also speeds

0:40:37.160 --> 0:40:40.319
<v Speaker 1>things up significantly. You don't have to dig up the

0:40:40.440 --> 0:40:43.240
<v Speaker 1>ground and bury cables and all that kind of stuff

0:40:43.239 --> 0:40:47.560
<v Speaker 1>and disrupt traffic. It could be a much faster deployment.

0:40:47.800 --> 0:40:52.520
<v Speaker 1>Assuming that the carriers get that permission to erect the

0:40:52.520 --> 0:40:56.440
<v Speaker 1>the cell towers or to add the technology to existing

0:40:56.480 --> 0:41:01.160
<v Speaker 1>cell towers, so you can get true broadband speed delivered

0:41:01.560 --> 0:41:04.680
<v Speaker 1>wirelessly to your home. You wouldn't have to have some

0:41:04.719 --> 0:41:07.960
<v Speaker 1>technician come out and hook up cable. You would just

0:41:08.040 --> 0:41:11.480
<v Speaker 1>get a wireless modem from your carrier. The other nice

0:41:11.480 --> 0:41:14.160
<v Speaker 1>thing about this is that if it does in fact happen,

0:41:14.680 --> 0:41:17.840
<v Speaker 1>it should mean that more people in the United States

0:41:17.840 --> 0:41:22.000
<v Speaker 1>in particular, will get more choices for their broadband provider.

0:41:22.160 --> 0:41:25.719
<v Speaker 1>Right now, a lot of people, myself included, if you

0:41:25.760 --> 0:41:29.560
<v Speaker 1>want true broadband speeds, if you want the faster speeds

0:41:29.600 --> 0:41:33.120
<v Speaker 1>in your area, you're limited to one provider. There's not

0:41:33.280 --> 0:41:37.120
<v Speaker 1>really a choice there so at my house, there's one

0:41:37.160 --> 0:41:40.840
<v Speaker 1>provider that can deliver the speeds I want to my house.

0:41:41.360 --> 0:41:47.000
<v Speaker 1>The next closest one is slower than the one I have,

0:41:47.640 --> 0:41:50.279
<v Speaker 1>so that's not really acceptable to me. And there's not

0:41:50.360 --> 0:41:54.080
<v Speaker 1>a lot of incentive for the other carriers to spend

0:41:54.120 --> 0:41:56.480
<v Speaker 1>the huge amount of money you would take to roll

0:41:56.560 --> 0:41:59.520
<v Speaker 1>fiber out to my house and compete with the one

0:41:59.600 --> 0:42:04.200
<v Speaker 1>provider or that is delivering that kind of service. By

0:42:04.239 --> 0:42:09.600
<v Speaker 1>going the wireless route, you've reduced the cost of deployment significantly,

0:42:10.239 --> 0:42:14.160
<v Speaker 1>and in theory, you could have a lot more competition

0:42:14.320 --> 0:42:17.919
<v Speaker 1>in those same areas, and competition is fantastic. We want

0:42:18.120 --> 0:42:23.919
<v Speaker 1>competition because when there's competition, the consumer benefits. Companies will

0:42:23.960 --> 0:42:28.080
<v Speaker 1>try to be competitive and pricing and features, and you

0:42:28.120 --> 0:42:33.000
<v Speaker 1>can pick whichever package best suits your needs instead of

0:42:33.040 --> 0:42:35.520
<v Speaker 1>just being stuck with whatever happens to be available in

0:42:35.520 --> 0:42:40.080
<v Speaker 1>your area. This is my dream that we get to

0:42:40.200 --> 0:42:43.480
<v Speaker 1>that that future. I'm hoping that that actually happens. Now.

0:42:43.680 --> 0:42:46.200
<v Speaker 1>I would advise folks to hold off on jumping onto

0:42:46.200 --> 0:42:49.400
<v Speaker 1>the five G bandwagon for a little bit. The deployment

0:42:49.440 --> 0:42:52.000
<v Speaker 1>is going to take some time and initial results might

0:42:52.000 --> 0:42:55.279
<v Speaker 1>be a little disappointing. At first, I suspect it's going

0:42:55.320 --> 0:42:58.840
<v Speaker 1>to be twenty or maybe even before we start seeing

0:42:59.120 --> 0:43:03.839
<v Speaker 1>any really impelling implementations of five G. Now I say that,

0:43:04.520 --> 0:43:07.640
<v Speaker 1>but I also imagine I'll probably ignore my own advice

0:43:07.760 --> 0:43:10.640
<v Speaker 1>and jump into the five G world earlier rather than later.

0:43:11.360 --> 0:43:13.480
<v Speaker 1>So what the heck do I know? But I know

0:43:13.560 --> 0:43:17.120
<v Speaker 1>that at least for the first year, I'll likely be

0:43:17.200 --> 0:43:20.440
<v Speaker 1>somewhat disappointed, which is crazy because I already know this

0:43:20.520 --> 0:43:22.680
<v Speaker 1>going into it. Why would I be disappointed if I

0:43:22.680 --> 0:43:24.800
<v Speaker 1>know it's already gonna happen, because I'm in a rational

0:43:24.920 --> 0:43:27.399
<v Speaker 1>human being. I think that's a good time to wrap up.

0:43:28.000 --> 0:43:30.960
<v Speaker 1>If you guys have any suggestions for future episodes of

0:43:31.000 --> 0:43:33.600
<v Speaker 1>tech Stuff, why don't you send me a message. The

0:43:33.640 --> 0:43:37.200
<v Speaker 1>email addresses tech Stuff at how stuff works dot com,

0:43:37.320 --> 0:43:40.080
<v Speaker 1>or hop on over to our website that's tech Stuff

0:43:40.120 --> 0:43:43.200
<v Speaker 1>podcast dot com. You'll find an archive of all of

0:43:43.200 --> 0:43:46.279
<v Speaker 1>our episodes there. You also find links to find us

0:43:46.320 --> 0:43:49.960
<v Speaker 1>on social media like Twitter and Facebook, and you'll find

0:43:49.960 --> 0:43:52.360
<v Speaker 1>a link to our store. And so we're at t

0:43:52.600 --> 0:43:55.600
<v Speaker 1>public dot com slash tech stuff, where every purchase you

0:43:55.680 --> 0:43:57.399
<v Speaker 1>make in our store goes to help with the show,

0:43:57.440 --> 0:44:00.120
<v Speaker 1>and we greatly appreciate it, and I will talk to

0:44:00.120 --> 0:44:09.000
<v Speaker 1>you again really soon for more on this and thousands

0:44:09.040 --> 0:44:21.160
<v Speaker 1>of other topics, because it how stuff works. Dot com