WEBVTT - 5G and the Future of Mobile

0:00:00.160 --> 0:00:07.080
<v Speaker 1>Brought to you by Toyota. Let's go places. Welcome to

0:00:07.280 --> 0:00:14.920
<v Speaker 1>Forward Thinking, Haydn and welcomed up Forward Thinking, the podcast

0:00:15.000 --> 0:00:17.080
<v Speaker 1>that looks at the future and says, what's the story,

0:00:17.280 --> 0:00:20.840
<v Speaker 1>Morning Glory, what's the word humming bird. I'm Jonathan Strickland,

0:00:20.920 --> 0:00:25.360
<v Speaker 1>I'm Lauren, and I'm Joe McCormick. And today we're going

0:00:25.400 --> 0:00:30.639
<v Speaker 1>to talk about five gus it's one more. It is

0:00:30.680 --> 0:00:34.720
<v Speaker 1>one more than four thing. Oh, we probably would be

0:00:34.760 --> 0:00:39.120
<v Speaker 1>four G. Yeah. You know, I remember back in the

0:00:39.159 --> 0:00:41.360
<v Speaker 1>old days and when I was first getting into cell

0:00:41.360 --> 0:00:45.760
<v Speaker 1>phones and you don't getting into them more like like

0:00:45.880 --> 0:00:50.000
<v Speaker 1>I was like getting into baseball cards. Back when I

0:00:50.040 --> 0:00:52.480
<v Speaker 1>think I had my first cell phone. I remember hearing

0:00:52.520 --> 0:00:57.120
<v Speaker 1>about three G and and it was the heyday of

0:00:57.240 --> 0:00:59.880
<v Speaker 1>three G when three G was a great thing, and

0:01:00.040 --> 0:01:03.200
<v Speaker 1>had no idea what that meant. Well, you were not alone, Joe.

0:01:04.000 --> 0:01:07.440
<v Speaker 1>But recently I saw an interesting This was yet another

0:01:07.480 --> 0:01:10.600
<v Speaker 1>topic I came across because of something I saw in

0:01:11.120 --> 0:01:16.039
<v Speaker 1>Alexis madrigals Awesome Email, his Real Future email newsletter, which

0:01:16.040 --> 0:01:20.000
<v Speaker 1>if you're not subscribed to that you should. It's amazing. Yeah. Yeah,

0:01:20.040 --> 0:01:23.399
<v Speaker 1>but it's about five G. No, not not the newsletter

0:01:23.760 --> 0:01:27.039
<v Speaker 1>the topic that we want to talk about today, right, Right,

0:01:27.160 --> 0:01:30.600
<v Speaker 1>So we have a lot of ground to cover before

0:01:30.600 --> 0:01:33.280
<v Speaker 1>we can get to five G, right, for four G

0:01:33.520 --> 0:01:37.559
<v Speaker 1>is worth of material at least, right, Okay. So so

0:01:37.560 --> 0:01:42.680
<v Speaker 1>so all of this G business um has to do well. Okay,

0:01:42.680 --> 0:01:45.000
<v Speaker 1>So so g G stands for generation. Let's get that

0:01:45.040 --> 0:01:47.960
<v Speaker 1>out there right at the top end. Uh. And and

0:01:48.080 --> 0:01:52.160
<v Speaker 1>what generation of of stuff we're talking about has to

0:01:52.200 --> 0:01:55.920
<v Speaker 1>do with at its base level, how radio frequencies are

0:01:55.920 --> 0:02:00.280
<v Speaker 1>allotted for broadcast and communication. Yeah, all right, because because

0:02:00.320 --> 0:02:02.840
<v Speaker 1>that is how your cell phone works. It transmits data

0:02:02.920 --> 0:02:06.520
<v Speaker 1>back and forth to cellular towers via radio waves, as

0:02:06.640 --> 0:02:09.920
<v Speaker 1>does a lot of other stuff, right, And and so

0:02:10.040 --> 0:02:13.200
<v Speaker 1>bits of the radio spectrum are cordoned off for all

0:02:13.240 --> 0:02:16.320
<v Speaker 1>of these different uses, for for television and for flight navigation,

0:02:16.360 --> 0:02:19.480
<v Speaker 1>and for mobile data and for local data within your

0:02:19.520 --> 0:02:23.280
<v Speaker 1>house and and etcetera, and etcetera. Uh. And of course,

0:02:23.360 --> 0:02:28.000
<v Speaker 1>when organizations and governments started allocating these frequencies, no one

0:02:28.080 --> 0:02:31.520
<v Speaker 1>could have predicted the crush of mobile data. Uh, you

0:02:31.560 --> 0:02:34.680
<v Speaker 1>know that the demand or the supply, And no one

0:02:34.680 --> 0:02:37.760
<v Speaker 1>could have predicted the speed with which technology would be

0:02:37.800 --> 0:02:41.400
<v Speaker 1>developed to attempt to meet that demand. It's all been

0:02:41.560 --> 0:02:44.360
<v Speaker 1>really pretty haphazard, right, so this is going to make

0:02:44.400 --> 0:02:46.800
<v Speaker 1>it even weirder when we're trying to predict what the

0:02:46.880 --> 0:02:50.240
<v Speaker 1>next generation is going to look like. But there is

0:02:50.280 --> 0:02:53.399
<v Speaker 1>something maybe interesting to say about it. But I think

0:02:53.400 --> 0:02:55.320
<v Speaker 1>before we get there, we need to do a sort

0:02:55.360 --> 0:02:58.920
<v Speaker 1>of brief history of the g S and English and

0:02:58.919 --> 0:03:02.040
<v Speaker 1>and Lauren to your point, I mean, keep in mind

0:03:02.080 --> 0:03:06.720
<v Speaker 1>like this, this entire technology is just over a century old.

0:03:06.840 --> 0:03:10.400
<v Speaker 1>I mean from the point of using radio waves. Yeah,

0:03:10.520 --> 0:03:14.600
<v Speaker 1>so yeah, not not cellular phones that's much younger, but

0:03:14.800 --> 0:03:17.280
<v Speaker 1>the radio in general, where we've been using that for

0:03:17.360 --> 0:03:21.240
<v Speaker 1>a little more than a hundred years. And obviously when

0:03:21.240 --> 0:03:23.880
<v Speaker 1>it was first being used, no, there were no regulations

0:03:23.880 --> 0:03:26.600
<v Speaker 1>because it hadn't been a thing before, right Yeah. Ever

0:03:26.880 --> 0:03:30.359
<v Speaker 1>was just like so the regulations that came in place,

0:03:30.880 --> 0:03:33.520
<v Speaker 1>they were developed in different parts of the world, so

0:03:33.600 --> 0:03:37.040
<v Speaker 1>they're the allocations you will find in the United States

0:03:37.080 --> 0:03:39.360
<v Speaker 1>are not necessarily the same as you would find in Europe,

0:03:39.960 --> 0:03:41.720
<v Speaker 1>which may not be the same as you would find

0:03:41.720 --> 0:03:44.720
<v Speaker 1>in other parts of the world. So that also makes

0:03:44.760 --> 0:03:47.480
<v Speaker 1>things a little more complicated, because you know, if the

0:03:47.480 --> 0:03:50.080
<v Speaker 1>whole world we're working on one standard. This story would

0:03:50.080 --> 0:03:53.360
<v Speaker 1>probably be a lot easier, but that's not the way

0:03:53.400 --> 0:03:57.680
<v Speaker 1>things turned out. So let's start with the first generation,

0:03:58.080 --> 0:04:04.280
<v Speaker 1>the original series the Captain Kirk of the Cellular World. Um,

0:04:04.400 --> 0:04:09.760
<v Speaker 1>so that first generation was an analog cellular system, not digital.

0:04:10.720 --> 0:04:13.960
<v Speaker 1>This is this is one one G. Yeah, they probably

0:04:14.000 --> 0:04:16.400
<v Speaker 1>didn't call it that at the time. No. No, it's

0:04:16.400 --> 0:04:19.200
<v Speaker 1>like it's like you wouldn't say first annual. That's that's

0:04:19.240 --> 0:04:23.400
<v Speaker 1>not that's just dumb say that. Well they shouldn't anyway,

0:04:23.520 --> 0:04:27.000
<v Speaker 1>the the the unless they're of course talking about the

0:04:27.040 --> 0:04:29.080
<v Speaker 1>second time they've held the event. That could be the

0:04:29.160 --> 0:04:33.920
<v Speaker 1>first annual one at any rate. So one G stood

0:04:34.000 --> 0:04:38.560
<v Speaker 1>for technologies including n M T C nets, amps and

0:04:38.680 --> 0:04:42.040
<v Speaker 1>tax or A MPs and T A c s, which

0:04:42.040 --> 0:04:44.760
<v Speaker 1>all began in the nineteen eighties. They had very limited bandwidth,

0:04:44.920 --> 0:04:48.279
<v Speaker 1>so they really were only suitable for voice transmission. You

0:04:48.320 --> 0:04:53.839
<v Speaker 1>did get a few, um you know, radio modem type things,

0:04:53.880 --> 0:04:56.520
<v Speaker 1>but they were extremely limited in what they could do.

0:04:56.960 --> 0:05:00.599
<v Speaker 1>So this was really primarily for voice train smission and

0:05:00.640 --> 0:05:04.000
<v Speaker 1>that was it. Uh. These would be the old cellular

0:05:04.040 --> 0:05:06.479
<v Speaker 1>phones that you would remember if you're old enough, with

0:05:06.560 --> 0:05:09.360
<v Speaker 1>the big brick cellular phones, the giant ones with a

0:05:09.400 --> 0:05:13.839
<v Speaker 1>huge antenna. UM. That's that's this era we're talking about.

0:05:14.400 --> 0:05:16.400
<v Speaker 1>Then you get to two G. This is when we

0:05:16.440 --> 0:05:19.280
<v Speaker 1>start moving into the ninety nineties, and this is where

0:05:19.320 --> 0:05:24.840
<v Speaker 1>the two really big uh competing technologies came out of

0:05:24.960 --> 0:05:28.040
<v Speaker 1>G S M and c d M A. UH, specifically

0:05:28.320 --> 0:05:31.160
<v Speaker 1>c d M A one. There was also d AMPS

0:05:31.200 --> 0:05:33.080
<v Speaker 1>at this time. But this is when we get into

0:05:33.160 --> 0:05:36.400
<v Speaker 1>the first generation of digital cellular systems. So it's the

0:05:36.400 --> 0:05:40.880
<v Speaker 1>second generation of cell systems overall, but the first generation

0:05:41.000 --> 0:05:44.839
<v Speaker 1>of digital systems. Okay, you're saying a lot of acronyms.

0:05:45.200 --> 0:05:47.120
<v Speaker 1>What are what are all these about? So tell me

0:05:47.120 --> 0:05:50.640
<v Speaker 1>about amps and get some at least tell you. I'll

0:05:50.640 --> 0:05:52.400
<v Speaker 1>tell you about g S M and c d M

0:05:52.440 --> 0:05:54.800
<v Speaker 1>A because those are the two really important ones. G

0:05:55.040 --> 0:05:57.400
<v Speaker 1>s M stands for Global System for Mobiles and c

0:05:57.520 --> 0:06:01.279
<v Speaker 1>d M A stands for code division multiple access. Both

0:06:01.279 --> 0:06:04.320
<v Speaker 1>of these are technologies that allow for multiple access to

0:06:04.480 --> 0:06:09.680
<v Speaker 1>a tower to allow for transmission of radio signals. Very important,

0:06:09.880 --> 0:06:14.880
<v Speaker 1>very basic technology that allows cell phones to work. Obviously,

0:06:14.960 --> 0:06:16.200
<v Speaker 1>for a cell phone to work, you need to be

0:06:16.240 --> 0:06:18.240
<v Speaker 1>able to have access a tower so that you can

0:06:18.320 --> 0:06:20.560
<v Speaker 1>send your transmission to the tower to go onto the

0:06:20.560 --> 0:06:24.320
<v Speaker 1>network and then receive information back from the network. And

0:06:24.720 --> 0:06:28.159
<v Speaker 1>you need a methodology for handshakes. That's the time where

0:06:28.279 --> 0:06:31.719
<v Speaker 1>you are going between one tower and another, like you're

0:06:31.920 --> 0:06:34.599
<v Speaker 1>you're you're starting to leave one tower's transmission area while

0:06:34.600 --> 0:06:37.240
<v Speaker 1>you're entering another one, and there's a handshake here, I

0:06:37.279 --> 0:06:40.919
<v Speaker 1>am yeah. That allows that to continue without any interruption.

0:06:41.160 --> 0:06:42.800
<v Speaker 1>So that way, if Lauren and I are talking on

0:06:42.839 --> 0:06:46.200
<v Speaker 1>a cell phone and she's driving uh, and she goes

0:06:46.279 --> 0:06:49.479
<v Speaker 1>past one tower to another, there's not an interruption in

0:06:49.520 --> 0:06:54.080
<v Speaker 1>the conversation. So both of these technologies could do that.

0:06:54.160 --> 0:06:58.279
<v Speaker 1>They were both the basics for digital cell phones. However,

0:06:58.320 --> 0:07:02.000
<v Speaker 1>they're competing technologies. GS them phones won't work on a

0:07:02.040 --> 0:07:04.840
<v Speaker 1>c d M A system and vice versa. You can

0:07:04.960 --> 0:07:06.840
<v Speaker 1>get world phones, Like if you have a c d

0:07:06.960 --> 0:07:09.039
<v Speaker 1>M A phone, you can get a world phone where

0:07:09.040 --> 0:07:11.120
<v Speaker 1>it also has a G s M chip in it,

0:07:11.160 --> 0:07:13.200
<v Speaker 1>but it will still primarily work on a c d

0:07:13.360 --> 0:07:16.000
<v Speaker 1>M A network. Now, why the reason why I call

0:07:16.040 --> 0:07:19.480
<v Speaker 1>it world phones is that most of the world, the

0:07:19.600 --> 0:07:23.400
<v Speaker 1>overwhelming population of the world, relies on G s M.

0:07:24.120 --> 0:07:26.160
<v Speaker 1>The United States is one of the few places that

0:07:26.280 --> 0:07:29.520
<v Speaker 1>also has c d M A, So we have two

0:07:29.560 --> 0:07:32.880
<v Speaker 1>major carriers that use G s M. That would be

0:07:32.920 --> 0:07:35.120
<v Speaker 1>a T and T and T mobile. And then we

0:07:35.160 --> 0:07:38.880
<v Speaker 1>have two major carriers, maybe three if you include UH

0:07:38.920 --> 0:07:42.640
<v Speaker 1>some of the other slightly smaller but growing ones, but

0:07:42.720 --> 0:07:45.240
<v Speaker 1>two major ones in Verizon and Sprint that use c

0:07:45.360 --> 0:07:50.320
<v Speaker 1>d M A technology. And this is a problem obviously,

0:07:50.360 --> 0:07:52.120
<v Speaker 1>because it means that if you have a C d

0:07:52.280 --> 0:07:55.360
<v Speaker 1>M A phone, you are more limited in where you

0:07:55.360 --> 0:07:58.480
<v Speaker 1>can take that phone and actually use it, unless again,

0:07:58.520 --> 0:08:00.360
<v Speaker 1>you have a world phone. Most people in up either

0:08:00.440 --> 0:08:02.520
<v Speaker 1>having a travel phone where it's a G s M

0:08:02.600 --> 0:08:05.560
<v Speaker 1>M G s M phone just for travel, or you know,

0:08:05.640 --> 0:08:09.120
<v Speaker 1>you can uh invest in a world phone, and maybe

0:08:09.120 --> 0:08:11.640
<v Speaker 1>one day this will become moot, but for now it's

0:08:11.680 --> 0:08:14.360
<v Speaker 1>still a thing. So the reason why most of the

0:08:14.360 --> 0:08:16.560
<v Speaker 1>world uses G s M and stuff c d M

0:08:16.560 --> 0:08:20.840
<v Speaker 1>A is that in n European government's mandated it. They

0:08:20.840 --> 0:08:24.440
<v Speaker 1>said you have to use g s M and they

0:08:24.440 --> 0:08:26.800
<v Speaker 1>were specifically looking at that because they considered it an

0:08:26.840 --> 0:08:30.960
<v Speaker 1>industry consortium that had produced the G s M standard.

0:08:31.000 --> 0:08:34.240
<v Speaker 1>In other words, it was a partnership amongst several different companies.

0:08:34.559 --> 0:08:37.840
<v Speaker 1>No one company laid claim to ownership of it. UH.

0:08:37.920 --> 0:08:40.040
<v Speaker 1>That was not true with C d M A, which

0:08:40.080 --> 0:08:43.679
<v Speaker 1>was kind of a qual calm thing, so uh so

0:08:43.760 --> 0:08:47.719
<v Speaker 1>they thought GSM better than this privately owned standard. The

0:08:47.760 --> 0:08:51.080
<v Speaker 1>United States, however, looked at it as saying, hey, C

0:08:51.200 --> 0:08:54.439
<v Speaker 1>d M A is allowing for faster data and voice

0:08:54.440 --> 0:08:57.679
<v Speaker 1>transmission rates, clearer phone calls. You know that a better

0:08:57.720 --> 0:09:02.000
<v Speaker 1>experience earlier on. And that's why in the United States

0:09:02.000 --> 0:09:04.719
<v Speaker 1>you had some carriers pushing C d M A. Now

0:09:04.760 --> 0:09:07.080
<v Speaker 1>G s M caught up, but it took some time.

0:09:07.280 --> 0:09:09.200
<v Speaker 1>So at first C d M A was in the lead,

0:09:09.280 --> 0:09:12.560
<v Speaker 1>and then the two were more or less comparable. Um. Now,

0:09:12.600 --> 0:09:14.200
<v Speaker 1>if you have a G s M phone, it's very

0:09:14.240 --> 0:09:16.719
<v Speaker 1>easy to switch from one network to another. So if

0:09:16.760 --> 0:09:18.599
<v Speaker 1>I have an A T and T phone and I

0:09:18.640 --> 0:09:21.160
<v Speaker 1>want to switch to T Mobile, it's very easy to do.

0:09:21.240 --> 0:09:23.280
<v Speaker 1>I go to T Mobile, I get a new simcard

0:09:24.240 --> 0:09:26.520
<v Speaker 1>or uh and I just pop it into my my

0:09:26.600 --> 0:09:28.560
<v Speaker 1>phone and it should work fine. And the other nice

0:09:28.559 --> 0:09:30.600
<v Speaker 1>thing is if I want to switch phones within the

0:09:30.640 --> 0:09:34.439
<v Speaker 1>same network, it's easy. So let's say I've got my

0:09:34.640 --> 0:09:37.640
<v Speaker 1>Nexus four on T Mobile and I want to upgrade

0:09:37.640 --> 0:09:40.920
<v Speaker 1>to a Nexus six. Then I can get the new phone,

0:09:41.040 --> 0:09:44.320
<v Speaker 1>pop the simcard into my new phone, and it works

0:09:45.000 --> 0:09:46.800
<v Speaker 1>right out of the box like it's it's perfect. I

0:09:46.800 --> 0:09:48.760
<v Speaker 1>don't have to do anything else to it. That is,

0:09:48.800 --> 0:09:50.680
<v Speaker 1>of course, assuming that the sim card is the same

0:09:50.720 --> 0:09:54.320
<v Speaker 1>size for the two phones, because recently we've received a

0:09:54.360 --> 0:09:57.240
<v Speaker 1>lot of new types of sim card technology where they've

0:09:57.280 --> 0:09:59.680
<v Speaker 1>been getting smaller and smaller. So sometimes you still have

0:09:59.720 --> 0:10:02.720
<v Speaker 1>to go to a phone like carrier store in order

0:10:02.720 --> 0:10:04.760
<v Speaker 1>to get a new size, or if you have a

0:10:04.840 --> 0:10:09.480
<v Speaker 1>very steady hand, you can cut one down yourself. I

0:10:09.520 --> 0:10:11.400
<v Speaker 1>didn't trust myself, so I went to the store to

0:10:11.400 --> 0:10:15.880
<v Speaker 1>get one, so um. The other thing about early G

0:10:16.080 --> 0:10:17.360
<v Speaker 1>S M and C D M A was that C

0:10:17.480 --> 0:10:21.560
<v Speaker 1>D M A could not handle simultaneous voice and data.

0:10:22.120 --> 0:10:24.960
<v Speaker 1>So you might remember commercials, I think A T and

0:10:25.000 --> 0:10:29.040
<v Speaker 1>T rent commercials about how specifically with the iPhone you

0:10:29.080 --> 0:10:31.800
<v Speaker 1>could have both voice and data at the same time,

0:10:31.840 --> 0:10:34.000
<v Speaker 1>because at one time A T and T in the

0:10:34.040 --> 0:10:38.320
<v Speaker 1>United States was the only carrier that had the iPhone.

0:10:39.000 --> 0:10:41.400
<v Speaker 1>It's no longer the case, but for for several years

0:10:41.400 --> 0:10:43.720
<v Speaker 1>that was the case, and they said, hey, you can

0:10:43.840 --> 0:10:46.160
<v Speaker 1>use both on our phone. Because it happened to be

0:10:46.200 --> 0:10:47.760
<v Speaker 1>a G S M phone. They didn't, you know, it

0:10:47.840 --> 0:10:49.720
<v Speaker 1>sounded like they were saying that it was unique to

0:10:49.720 --> 0:10:52.000
<v Speaker 1>the iPhone. It wasn't. It was that it was the

0:10:52.280 --> 0:10:57.000
<v Speaker 1>network the technology they were using allowed for it. So

0:10:57.280 --> 0:11:00.920
<v Speaker 1>that is your two G. Uh. You think we would

0:11:00.920 --> 0:11:03.840
<v Speaker 1>immediately go to three G. But hold up a second,

0:11:04.240 --> 0:11:08.280
<v Speaker 1>because there's two point five G. This is starting to

0:11:08.320 --> 0:11:11.439
<v Speaker 1>sound like seasons of the New Battlestar Galactica. It feels

0:11:11.520 --> 0:11:14.920
<v Speaker 1>like that. It also it also feels like generations of

0:11:14.960 --> 0:11:17.600
<v Speaker 1>the iPhone, where the number that is associated with the

0:11:17.600 --> 0:11:23.199
<v Speaker 1>iPhone is not necessarily the actual generation of the iPhone.

0:11:23.280 --> 0:11:27.160
<v Speaker 1>Or or Windows, like this is Windows ten. We went

0:11:27.160 --> 0:11:30.680
<v Speaker 1>from Windows seven to Windows eight to Windows ten. I

0:11:30.760 --> 0:11:34.520
<v Speaker 1>love Windows. Schmickery. Do when can I get cell phone emmy?

0:11:35.120 --> 0:11:37.240
<v Speaker 1>All right, well let's let's go back to two point

0:11:37.240 --> 0:11:40.160
<v Speaker 1>five G. So this is where we get even more confusing.

0:11:40.200 --> 0:11:44.520
<v Speaker 1>All right, so we've got these two competing technologies that

0:11:44.600 --> 0:11:46.880
<v Speaker 1>you know in the in the G M S and

0:11:46.920 --> 0:11:49.959
<v Speaker 1>c d um ah. Now we get to g p

0:11:50.320 --> 0:11:53.160
<v Speaker 1>R S and c d M A two thousand one x.

0:11:53.520 --> 0:11:58.640
<v Speaker 1>These were enhanced to G networks. So here's the deal.

0:12:00.400 --> 0:12:03.160
<v Speaker 1>We're not just talking about generations here. It would be

0:12:03.200 --> 0:12:05.599
<v Speaker 1>so much easier if we were talking generations except for

0:12:05.640 --> 0:12:08.240
<v Speaker 1>the fact that since we have a branching technology tree,

0:12:08.440 --> 0:12:12.320
<v Speaker 1>you would have different generations as technology is mature at

0:12:12.320 --> 0:12:15.880
<v Speaker 1>different rates. Right, So G S M would be maturing

0:12:16.080 --> 0:12:19.680
<v Speaker 1>at at one and I think it's a g MS

0:12:19.720 --> 0:12:21.760
<v Speaker 1>a second ago. But G s M would be maturing

0:12:21.760 --> 0:12:23.160
<v Speaker 1>at one rate and C D M A would be

0:12:23.200 --> 0:12:27.800
<v Speaker 1>maturing at another rate. So that would make that confusing.

0:12:27.920 --> 0:12:31.160
<v Speaker 1>But to to try and make it a little more streamlined,

0:12:32.160 --> 0:12:36.000
<v Speaker 1>the various international organizations have come in to say, listen,

0:12:36.240 --> 0:12:40.040
<v Speaker 1>we're going to say that that generation stands for the

0:12:40.120 --> 0:12:44.960
<v Speaker 1>capability of your technology, not how many iterations there have been,

0:12:45.320 --> 0:12:49.480
<v Speaker 1>but there is a bare basic limit of of how

0:12:49.600 --> 0:12:53.080
<v Speaker 1>much data they have to be able to accept per second,

0:12:53.480 --> 0:12:55.880
<v Speaker 1>and if they meet that, that means they fall into

0:12:55.960 --> 0:13:00.400
<v Speaker 1>this generation versus that generation. That's nice. Yeah, So two

0:13:00.400 --> 0:13:03.800
<v Speaker 1>point five point five is two point five because it's

0:13:03.880 --> 0:13:06.320
<v Speaker 1>faster than two but it doesn't quite meet the standards

0:13:06.440 --> 0:13:09.160
<v Speaker 1>that were set for three G. So they had to

0:13:09.360 --> 0:13:11.959
<v Speaker 1>pick where do you put them? Do you don't want

0:13:11.960 --> 0:13:15.960
<v Speaker 1>to call it two G because as a carrier, you

0:13:16.000 --> 0:13:19.040
<v Speaker 1>want to use this as a selling point to your customers,

0:13:19.040 --> 0:13:22.160
<v Speaker 1>say our networks are faster than two G. But you

0:13:22.240 --> 0:13:25.120
<v Speaker 1>can't go and say they're three G because the data

0:13:25.240 --> 0:13:27.480
<v Speaker 1>rates aren't there yet. They could have just gone with

0:13:27.520 --> 0:13:31.440
<v Speaker 1>like awesome too, or three to two G plus or

0:13:31.520 --> 0:13:34.720
<v Speaker 1>two G plus or three G minus a little bit. Uh.

0:13:34.800 --> 0:13:37.560
<v Speaker 1>So that gives us to three G, where we have

0:13:37.640 --> 0:13:40.400
<v Speaker 1>a whole bunch of different competing standards which I'm not

0:13:40.400 --> 0:13:42.400
<v Speaker 1>even gonna go into. I mean edges in there. So

0:13:42.440 --> 0:13:44.320
<v Speaker 1>if you've ever heard about being on the edge network,

0:13:44.360 --> 0:13:47.360
<v Speaker 1>that's technically a three G network. They have even faster

0:13:47.480 --> 0:13:51.360
<v Speaker 1>data rates than previous generations, at about kill a bits

0:13:51.400 --> 0:13:56.600
<v Speaker 1>per second. So when I say even faster, that's pretty slow, yeah,

0:13:56.640 --> 0:13:59.000
<v Speaker 1>but faster than two G. So the u N International

0:13:59.080 --> 0:14:01.920
<v Speaker 1>Telecommunications Union set the standard for three G at two

0:14:01.920 --> 0:14:06.440
<v Speaker 1>megabets per second if the phone is stationary, and kill

0:14:06.520 --> 0:14:09.480
<v Speaker 1>bits per second for a phone that's in motion. Obviously,

0:14:09.480 --> 0:14:11.480
<v Speaker 1>phones that are in motion have to deal with this handshake,

0:14:11.920 --> 0:14:14.960
<v Speaker 1>so that's what complicates matters. If you are stationary, you

0:14:15.000 --> 0:14:16.640
<v Speaker 1>don't need to do that, and you can have a

0:14:16.679 --> 0:14:20.440
<v Speaker 1>faster download rate. Okay, so we're getting closer to the

0:14:20.480 --> 0:14:24.840
<v Speaker 1>present day. Yeah, when we hit four G, okay, yeah,

0:14:25.000 --> 0:14:27.040
<v Speaker 1>all right, tell me the story of four G. Four

0:14:27.120 --> 0:14:31.560
<v Speaker 1>G is another complicated story. Send to me sing, so

0:14:32.520 --> 0:14:35.880
<v Speaker 1>I can tell you what four G is supposed to be.

0:14:35.920 --> 0:14:38.960
<v Speaker 1>Four G is supposed to be one gigabit per second

0:14:39.080 --> 0:14:41.640
<v Speaker 1>when the phone is stationary or mobile device. It's not

0:14:41.720 --> 0:14:44.360
<v Speaker 1>just a phone now, but four G you should be

0:14:44.400 --> 0:14:48.320
<v Speaker 1>able to get a one gigabit per second download rate

0:14:48.960 --> 0:14:52.120
<v Speaker 1>when that when the device is not in motion, and

0:14:52.240 --> 0:14:55.840
<v Speaker 1>one hundred megabets per second when it is in motion. However,

0:14:57.360 --> 0:15:00.440
<v Speaker 1>none of the current standards that are touted as four

0:15:00.520 --> 0:15:05.120
<v Speaker 1>G meet that specification. Yeah, so they're just they're just

0:15:05.280 --> 0:15:08.800
<v Speaker 1>flipping the un off all the time. Yeah, they're essentially saying, listen,

0:15:08.800 --> 0:15:11.440
<v Speaker 1>we're calling this four G because it is the next

0:15:11.560 --> 0:15:16.640
<v Speaker 1>generation of our technology. It works in a completely different

0:15:16.680 --> 0:15:19.720
<v Speaker 1>way from three G. It uses a different methodology for

0:15:19.800 --> 0:15:24.480
<v Speaker 1>handling data. It's it's using brand new technology, so we

0:15:24.600 --> 0:15:26.600
<v Speaker 1>gotta call it something. We're not calling it three G

0:15:26.760 --> 0:15:29.040
<v Speaker 1>plus or three point five G, so we're calling it

0:15:29.080 --> 0:15:33.360
<v Speaker 1>four G. And you can take your standards and just

0:15:33.520 --> 0:15:36.080
<v Speaker 1>pretend like they don't exist, because that's what we're gonna do.

0:15:36.240 --> 0:15:39.080
<v Speaker 1>That's like if Star Trek the next generation had James

0:15:39.120 --> 0:15:42.600
<v Speaker 1>do Hand in the engineering room. Yeah, so we're just

0:15:43.240 --> 0:15:47.760
<v Speaker 1>we're just having him. It's no reason we're not explaining it. Um. Yeah,

0:15:47.840 --> 0:15:51.320
<v Speaker 1>and it's so so we have this four gen name

0:15:51.400 --> 0:15:54.280
<v Speaker 1>that's a marketing term. It's not really they're not four

0:15:54.320 --> 0:15:56.680
<v Speaker 1>G according to those UN standards, which by the way,

0:15:56.840 --> 0:15:59.640
<v Speaker 1>even the U N now is like whatever, okay, fine,

0:16:00.280 --> 0:16:02.640
<v Speaker 1>uh And the and the technologies that we're talking about

0:16:03.000 --> 0:16:05.160
<v Speaker 1>that are called for g R U l T E,

0:16:05.680 --> 0:16:08.440
<v Speaker 1>And then there's y max, and there's h s P

0:16:08.600 --> 0:16:11.440
<v Speaker 1>A plus. Hsp A plus comes in a couple of

0:16:11.480 --> 0:16:15.400
<v Speaker 1>different flavors of forty two. Although forty two are the

0:16:15.400 --> 0:16:17.640
<v Speaker 1>ones that are considered to be closer to four G speeds,

0:16:17.960 --> 0:16:20.640
<v Speaker 1>none of these get close to that one gigabit per

0:16:20.680 --> 0:16:25.000
<v Speaker 1>second uh LTE tops out of around a hundred megabits

0:16:25.040 --> 0:16:29.160
<v Speaker 1>per second or so. Um, you can get. The fastest

0:16:29.200 --> 0:16:31.960
<v Speaker 1>speed up scene for LT is three hundred megabits per second.

0:16:32.000 --> 0:16:35.960
<v Speaker 1>That was like an ideal test. Um. There is l

0:16:36.000 --> 0:16:40.120
<v Speaker 1>t A l t E Advanced, which could theoretically get

0:16:40.200 --> 0:16:44.320
<v Speaker 1>much faster, but that's not rolled out very widely right now.

0:16:44.960 --> 0:16:47.640
<v Speaker 1>Y max is kind of dead in the water. Essentially,

0:16:47.640 --> 0:16:50.480
<v Speaker 1>it's no longer really a thing. Everyone's looking at l

0:16:50.520 --> 0:16:54.000
<v Speaker 1>T E hsp A plus some some carriers use that.

0:16:54.040 --> 0:16:57.080
<v Speaker 1>T Mobile uses that, but they also use l T E.

0:16:57.160 --> 0:17:01.240
<v Speaker 1>They roll out LT networks as well, so that is

0:17:01.320 --> 0:17:03.720
<v Speaker 1>kind of leading us up to today. That's where we

0:17:03.760 --> 0:17:08.160
<v Speaker 1>are now, is with this mishmash of technologies. By the way,

0:17:08.600 --> 0:17:12.160
<v Speaker 1>if we all by we, I mean like the carriers,

0:17:12.440 --> 0:17:15.440
<v Speaker 1>if all the carriers adopted LTE, if they rolled out

0:17:15.880 --> 0:17:20.560
<v Speaker 1>robust LT networks and phased out the older networks, then

0:17:20.640 --> 0:17:24.520
<v Speaker 1>you could, in theory, have a phone that could work

0:17:24.560 --> 0:17:26.920
<v Speaker 1>on any network as long as it was an LTE phone,

0:17:26.960 --> 0:17:31.160
<v Speaker 1>because it's it's no longer this branching UH technology where

0:17:31.200 --> 0:17:33.080
<v Speaker 1>you've got the G S N versus C D M A.

0:17:33.440 --> 0:17:36.879
<v Speaker 1>It would all be unified in theory. In practice not

0:17:37.000 --> 0:17:41.200
<v Speaker 1>gonna happen because you've got companies putting in proprietary software

0:17:41.680 --> 0:17:44.119
<v Speaker 1>that is required to run in order for you to

0:17:44.160 --> 0:17:46.520
<v Speaker 1>do something like make a voice call, So you can't

0:17:46.560 --> 0:17:48.960
<v Speaker 1>just take the phone you have on one network and

0:17:49.040 --> 0:17:51.720
<v Speaker 1>pop onto another network and not have any problems. It's

0:17:51.760 --> 0:17:55.640
<v Speaker 1>it's overall advantageous I would say for humanity, um for

0:17:55.680 --> 0:17:59.040
<v Speaker 1>everyone to be working within the same infrastructure. But it's

0:17:59.080 --> 0:18:02.320
<v Speaker 1>it's honestly very advantageous from a business perspective to use

0:18:02.359 --> 0:18:05.840
<v Speaker 1>your own proprietary to lock you in. Yeah, you can

0:18:05.840 --> 0:18:08.199
<v Speaker 1>sell more stuff. Yeah, yeah, I love being locked in.

0:18:08.960 --> 0:18:12.119
<v Speaker 1>So it's so cozy. It's like a hobbit hole that

0:18:12.119 --> 0:18:14.800
<v Speaker 1>you can't leave. When I don't have to make choices,

0:18:15.000 --> 0:18:18.480
<v Speaker 1>my life is so much easier. Actually, there's some truth

0:18:18.520 --> 0:18:22.440
<v Speaker 1>to that. We should talk about the science of choice sometimes. Yeah,

0:18:22.480 --> 0:18:27.040
<v Speaker 1>I mean yeah, if you have, you know, unlimited choice,

0:18:27.040 --> 0:18:28.880
<v Speaker 1>then you could be paralyzed by it. We've talked about

0:18:28.920 --> 0:18:31.240
<v Speaker 1>that a couple of times on tech stuff. Yes, yes, okay,

0:18:31.320 --> 0:18:36.399
<v Speaker 1>but so so shade aside. Um, let's let's look forward

0:18:36.440 --> 0:18:40.000
<v Speaker 1>to this amazing future of five G. Okay, right, well,

0:18:40.040 --> 0:18:42.720
<v Speaker 1>what inspired us to talk about this today was, again,

0:18:42.760 --> 0:18:46.320
<v Speaker 1>like I said, uh, an article that I read about

0:18:46.640 --> 0:18:51.120
<v Speaker 1>people predicting five G what the next generation of this

0:18:51.359 --> 0:18:54.880
<v Speaker 1>wireless technology would be. So five G is not a

0:18:54.920 --> 0:18:57.720
<v Speaker 1>fixed standard yet, right, it's more of a kind of

0:18:57.720 --> 0:19:00.840
<v Speaker 1>an ambiguous concept. What's going on now is people are

0:19:00.920 --> 0:19:05.160
<v Speaker 1>debating and talking about what five G is going to be. Yeah,

0:19:05.160 --> 0:19:07.560
<v Speaker 1>they're kind of blue skying it. I mean, you can

0:19:07.600 --> 0:19:11.399
<v Speaker 1>make certain predictions saying that these are the sort of

0:19:11.400 --> 0:19:14.399
<v Speaker 1>things we would consider necessary for us to call it

0:19:14.480 --> 0:19:18.440
<v Speaker 1>five G. For example, we would expect even faster UH

0:19:18.600 --> 0:19:21.320
<v Speaker 1>data rates that would be that would be an expectation

0:19:21.480 --> 0:19:25.280
<v Speaker 1>of the advancement of the generations of this technology. But

0:19:25.320 --> 0:19:27.720
<v Speaker 1>there are other elements as well. So it's one of

0:19:27.760 --> 0:19:30.120
<v Speaker 1>those things. Again, since since we don't have a hard

0:19:30.160 --> 0:19:34.120
<v Speaker 1>and fast number, Ultimately, what might happen is the next

0:19:34.160 --> 0:19:36.879
<v Speaker 1>technology that comes out, people will start calling five G

0:19:37.200 --> 0:19:39.879
<v Speaker 1>and it may not come close to measuring up to

0:19:40.040 --> 0:19:42.679
<v Speaker 1>some of the things that people have proposed. Right, but

0:19:43.119 --> 0:19:46.760
<v Speaker 1>already there have been some like politicians and industry leaders

0:19:46.840 --> 0:19:50.080
<v Speaker 1>trying to set really ambitious goals for what should be done,

0:19:50.240 --> 0:19:54.160
<v Speaker 1>incredibly ambitious, like sometimes like you hear it and you think,

0:19:54.280 --> 0:19:58.359
<v Speaker 1>wait what Yeah. So the topic of five G was

0:19:58.400 --> 0:20:05.359
<v Speaker 1>addressed in March Mobile World Congress, and Bonnie Chop or

0:20:05.440 --> 0:20:08.639
<v Speaker 1>Recode put together a good right up afterwards, including predictions

0:20:08.680 --> 0:20:13.600
<v Speaker 1>made about speed, which came to the prediction was that

0:20:13.720 --> 0:20:18.000
<v Speaker 1>five G would feature ideal speeds of ten gigabits per

0:20:18.040 --> 0:20:24.080
<v Speaker 1>second And I just thought, w T some other letters.

0:20:25.680 --> 0:20:32.200
<v Speaker 1>Are are they the generation? Are they for real? Because

0:20:32.320 --> 0:20:35.399
<v Speaker 1>so the four Chop points out that the four G

0:20:35.600 --> 0:20:38.359
<v Speaker 1>standard the ideal standard is one gigabit per second, but

0:20:38.520 --> 0:20:42.440
<v Speaker 1>it's never actually that fast, is it. No? And what

0:20:42.640 --> 0:20:45.840
<v Speaker 1>prevents it from operating at that top speed, Well, there's

0:20:45.960 --> 0:20:48.920
<v Speaker 1>just the basic limitation of the systems themselves. Like I said,

0:20:48.960 --> 0:20:51.840
<v Speaker 1>with LTE, the regular LT you top out in around

0:20:51.880 --> 0:20:55.720
<v Speaker 1>three d megabits per second even under ideal circumstances. But

0:20:55.840 --> 0:20:58.719
<v Speaker 1>what goes into that speed is a whole bunch of factors. Um,

0:20:58.920 --> 0:21:01.760
<v Speaker 1>it's it's going to be the distance between you and

0:21:01.840 --> 0:21:04.640
<v Speaker 1>the tower that your device is communicating with. It's gonna

0:21:04.720 --> 0:21:08.440
<v Speaker 1>be um, the amount of other data that that tower

0:21:08.600 --> 0:21:11.720
<v Speaker 1>is handling at the time, Um, the weather, the number

0:21:11.800 --> 0:21:14.320
<v Speaker 1>of trees that are between you and the tower. Yeah, yeah,

0:21:14.440 --> 0:21:16.679
<v Speaker 1>it's tons of stuff like that. Now, if you are

0:21:16.720 --> 0:21:19.920
<v Speaker 1>talking about, you know, lab conditions, then that's where you

0:21:19.960 --> 0:21:22.800
<v Speaker 1>would probably get this ideal speed. But even in those

0:21:22.880 --> 0:21:25.760
<v Speaker 1>lab conditions, no one has come close to the gigabits

0:21:25.800 --> 0:21:32.200
<v Speaker 1>per second, although lt LTE Advanced has the theoretical peak

0:21:32.560 --> 0:21:36.520
<v Speaker 1>performance of three gigabits per second download speed one point

0:21:36.640 --> 0:21:39.800
<v Speaker 1>five gigabits per second upload speed. But as I said earlier,

0:21:40.359 --> 0:21:44.080
<v Speaker 1>there are not very many ILT advanced UH networks rolled

0:21:44.119 --> 0:21:46.520
<v Speaker 1>out yet, so it's we don't have a lot of

0:21:46.600 --> 0:21:49.800
<v Speaker 1>real world testing in that realm. Yeah, it should have

0:21:49.800 --> 0:21:52.560
<v Speaker 1>added to that list to the physical capacity, the physical

0:21:52.640 --> 0:21:56.480
<v Speaker 1>technological capacity of both your device and all of the

0:21:56.520 --> 0:21:59.200
<v Speaker 1>computers at the other end of the network that it's

0:21:59.240 --> 0:22:01.119
<v Speaker 1>talking to you. It's of like saying that you know,

0:22:01.200 --> 0:22:03.960
<v Speaker 1>if you have if you have a hallway that's ten

0:22:04.160 --> 0:22:07.280
<v Speaker 1>people wide, but your doorway is only one person wide,

0:22:07.720 --> 0:22:10.040
<v Speaker 1>then and you think of the doorway being your device,

0:22:10.160 --> 0:22:12.280
<v Speaker 1>then your device would be the bottleneck in that case.

0:22:12.600 --> 0:22:14.320
<v Speaker 1>Or or even you know, like I've got this really

0:22:14.359 --> 0:22:20.400
<v Speaker 1>elegant software and a tricycle. Yeah, yeah, that that would

0:22:20.400 --> 0:22:22.960
<v Speaker 1>not be helpful at home. Should have seen Laura gestu.

0:22:23.680 --> 0:22:26.840
<v Speaker 1>She was pointing at the tricycle. I believe I believed

0:22:27.040 --> 0:22:29.720
<v Speaker 1>there was a tricycle there. No, it's how how convincing.

0:22:29.760 --> 0:22:33.320
<v Speaker 1>It was maybe ten gigabits per second, which again was

0:22:33.440 --> 0:22:37.480
<v Speaker 1>the prediction here. Maybe that's not meaningful to you, So

0:22:37.640 --> 0:22:40.119
<v Speaker 1>think about it like this. It is one point to

0:22:40.640 --> 0:22:45.000
<v Speaker 1>five gigabytes per second, so that you could, like if

0:22:45.040 --> 0:22:47.880
<v Speaker 1>you wanted to download a video game, you could download

0:22:47.920 --> 0:22:51.040
<v Speaker 1>a copy of sky Room in like five seconds, or

0:22:51.240 --> 0:22:53.680
<v Speaker 1>or what about like a movie, Well, so like a

0:22:53.800 --> 0:22:58.600
<v Speaker 1>tin a dp HD movie and compressed format would maybe

0:22:58.640 --> 0:23:02.359
<v Speaker 1>take Also, like about five seconds are less. The computer

0:23:02.480 --> 0:23:06.240
<v Speaker 1>I used in college, you could download its entire hard

0:23:06.359 --> 0:23:09.120
<v Speaker 1>drive in less than three seconds. And if you want

0:23:09.160 --> 0:23:12.680
<v Speaker 1>another illustration of how fast this is, so ten gigabits

0:23:12.720 --> 0:23:16.480
<v Speaker 1>per second. That's ten times faster than the speeds promised

0:23:16.520 --> 0:23:21.680
<v Speaker 1>by Google Fiber and competing carriers. Wired connection, yeah, actual

0:23:21.920 --> 0:23:25.960
<v Speaker 1>optical cable going to your house. You know often, uh,

0:23:26.560 --> 0:23:29.040
<v Speaker 1>Like Lauren and I are both video gamers, so you

0:23:29.080 --> 0:23:32.880
<v Speaker 1>play some video games too, So we all are aware

0:23:33.040 --> 0:23:35.240
<v Speaker 1>of the idea that if you're playing an online game,

0:23:35.280 --> 0:23:38.040
<v Speaker 1>it's better to have that wired connection than it is

0:23:38.080 --> 0:23:40.200
<v Speaker 1>to go with wireless because you can have lag and

0:23:40.280 --> 0:23:42.600
<v Speaker 1>latency and all these other issues share any time that

0:23:42.600 --> 0:23:45.119
<v Speaker 1>you add that extra step of having to beam the

0:23:45.200 --> 0:23:50.960
<v Speaker 1>signal from your your your actual Yeah, it's better to

0:23:51.040 --> 0:23:55.240
<v Speaker 1>have that physical, dedicated line. And that's what I would

0:23:55.280 --> 0:23:59.680
<v Speaker 1>think too until I hear ten gibits per second wireless transmission,

0:23:59.720 --> 0:24:02.760
<v Speaker 1>because it's ten times faster than the optical fiber. I mean,

0:24:02.880 --> 0:24:05.640
<v Speaker 1>that would make you wonder like, okay, so why would

0:24:05.680 --> 0:24:08.320
<v Speaker 1>we even have optical fiber? What's the point of wires

0:24:08.440 --> 0:24:12.200
<v Speaker 1>at that point. Yeah, right, if you could actually get

0:24:12.240 --> 0:24:14.560
<v Speaker 1>to uh, that that point. We'll talk about this a

0:24:14.600 --> 0:24:16.479
<v Speaker 1>little bit more. I'm sure later if you can get

0:24:16.520 --> 0:24:20.120
<v Speaker 1>to a point where ten gigabits per second, even even

0:24:20.200 --> 0:24:23.720
<v Speaker 1>if that's the ideal and you never reached the ideal, okay, yeah, yeah,

0:24:23.800 --> 0:24:26.360
<v Speaker 1>let's say it's you know, the real speed you get

0:24:26.520 --> 0:24:31.479
<v Speaker 1>is four still, four times faster than fiber, is right.

0:24:31.560 --> 0:24:33.960
<v Speaker 1>And even then, when you say one gigabit per second

0:24:34.000 --> 0:24:37.879
<v Speaker 1>with Google Fiber that's the ideal for Google Fiber, you

0:24:38.000 --> 0:24:40.680
<v Speaker 1>might you might top out at nine megabits per second.

0:24:41.240 --> 0:24:43.480
<v Speaker 1>M that's not acceptable. So I'm going to get four

0:24:43.920 --> 0:24:47.600
<v Speaker 1>gigabits per second over over the air. You mentioned the

0:24:47.680 --> 0:24:52.840
<v Speaker 1>difference between lab conditions and real conditions. In ideal conditions,

0:24:52.960 --> 0:24:55.399
<v Speaker 1>what kind of things can we do now at the

0:24:55.480 --> 0:24:58.800
<v Speaker 1>top end of speaking, So with the five G technology

0:24:58.920 --> 0:25:01.160
<v Speaker 1>in the lab right now, uh, the average speed tends

0:25:01.160 --> 0:25:03.399
<v Speaker 1>to be around one gigabit per second, which, if you remember,

0:25:03.560 --> 0:25:06.600
<v Speaker 1>is the promise speed of four G. So it feels

0:25:06.600 --> 0:25:09.280
<v Speaker 1>like we're just playing catch up. But there have been

0:25:09.840 --> 0:25:12.760
<v Speaker 1>some some demos of much faster speed. Samsung held a

0:25:12.840 --> 0:25:15.480
<v Speaker 1>demo where they showed that they could hit seven point

0:25:15.600 --> 0:25:18.920
<v Speaker 1>five gigabits per second when it was stationary, and one

0:25:19.000 --> 0:25:22.200
<v Speaker 1>point two gigabits per second if the device was traveling

0:25:22.320 --> 0:25:24.680
<v Speaker 1>at a speed of a hundred kilometers per hour or

0:25:24.840 --> 0:25:29.320
<v Speaker 1>sixty two miles per hour. Pretty impressive. So at that speed,

0:25:29.440 --> 0:25:32.000
<v Speaker 1>I mean you could you could end up being able

0:25:32.080 --> 0:25:35.040
<v Speaker 1>to stream content without any problems. There's a ton of

0:25:35.119 --> 0:25:38.840
<v Speaker 1>stuff that you would be able to access. And you know,

0:25:39.040 --> 0:25:42.000
<v Speaker 1>we were talking a lot about mobile devices, but honestly,

0:25:42.119 --> 0:25:44.399
<v Speaker 1>this technology is working its way into a lot of

0:25:44.520 --> 0:25:48.399
<v Speaker 1>other platforms, including cars. So there are a lot of

0:25:48.480 --> 0:25:51.120
<v Speaker 1>potential uses and we'll talk a little bit about those

0:25:51.160 --> 0:25:53.399
<v Speaker 1>in a little in a moment or two. Yeah, So

0:25:53.640 --> 0:25:57.680
<v Speaker 1>another predicted standard of five G would be very very

0:25:57.840 --> 0:26:01.320
<v Speaker 1>low latency, like one mill the second latency. And if

0:26:01.359 --> 0:26:03.920
<v Speaker 1>you ask what is latency, that's just the time of

0:26:04.040 --> 0:26:07.200
<v Speaker 1>delay in delivering a packet from one device to another.

0:26:07.320 --> 0:26:10.240
<v Speaker 1>So a packets a piece of data. Uh, the amount

0:26:10.320 --> 0:26:12.800
<v Speaker 1>of data you can transmit in a certain period of

0:26:12.880 --> 0:26:16.359
<v Speaker 1>time might change, you might have more bandwidth or throughput, um,

0:26:16.480 --> 0:26:19.240
<v Speaker 1>but the latency is just the time lag in delivering

0:26:19.359 --> 0:26:25.000
<v Speaker 1>one packet. Uh. The other thing would be connectedness, how

0:26:25.160 --> 0:26:29.520
<v Speaker 1>much can a network support, Like how many things can

0:26:29.600 --> 0:26:33.160
<v Speaker 1>you wirelessly send data between at the same time? Yeah,

0:26:33.160 --> 0:26:36.520
<v Speaker 1>and this was this was a real concern, especially earlier

0:26:36.680 --> 0:26:39.320
<v Speaker 1>in cellular networks, where you would have towers that would

0:26:39.359 --> 0:26:42.520
<v Speaker 1>get overwhelmed and you have by like three signals at

0:26:42.560 --> 0:26:45.640
<v Speaker 1>the same time. Yea. And the old days yeah, in fact, yeah,

0:26:45.720 --> 0:26:47.720
<v Speaker 1>the old old days there were you would look and

0:26:47.760 --> 0:26:50.720
<v Speaker 1>you say, like, all right, this one city has a

0:26:50.800 --> 0:26:55.399
<v Speaker 1>broadcast tower and it can handle like two simultaneous connections

0:26:55.520 --> 0:26:58.840
<v Speaker 1>and that's it. You know. Obviously that technology has improved

0:26:58.880 --> 0:27:02.960
<v Speaker 1>over time. Yeah, and that is largely a software is shue,

0:27:03.000 --> 0:27:05.120
<v Speaker 1>I mean, also a memory issue. But what you're really

0:27:05.160 --> 0:27:09.680
<v Speaker 1>talking about is, uh, the capacity of a computer to multitasks. Yeah,

0:27:10.160 --> 0:27:12.879
<v Speaker 1>essentially that that's what it boils down to, and that

0:27:13.040 --> 0:27:15.399
<v Speaker 1>has improved significantly over time, and it would have to

0:27:16.040 --> 0:27:18.840
<v Speaker 1>because we're also talking about the burgeoning era of the

0:27:18.920 --> 0:27:23.119
<v Speaker 1>Internet of Things, when we're adding lots more devices to

0:27:23.359 --> 0:27:26.760
<v Speaker 1>various networks. So there it's not just your cell phone

0:27:26.880 --> 0:27:29.679
<v Speaker 1>or not just your computer, your tablet, it's also all

0:27:29.800 --> 0:27:32.359
<v Speaker 1>the devices in your house and your car and probably

0:27:32.400 --> 0:27:36.640
<v Speaker 1>a bunch of sensors outside taking data on various stuff. Yeah,

0:27:36.640 --> 0:27:38.800
<v Speaker 1>and now that you could have these things connecting into

0:27:38.880 --> 0:27:43.040
<v Speaker 1>their own network, which then connects to an access point. Right,

0:27:43.280 --> 0:27:45.440
<v Speaker 1>so you could have essentially a traffic manager in the

0:27:45.520 --> 0:27:48.080
<v Speaker 1>form of a router that would take care of some

0:27:48.200 --> 0:27:50.600
<v Speaker 1>of that. But it's also potential if you have the

0:27:50.680 --> 0:27:54.120
<v Speaker 1>capacity to handle billions of different devices at a time

0:27:54.160 --> 0:27:57.440
<v Speaker 1>on a single tower, you could have them connecting directly

0:27:57.480 --> 0:27:59.520
<v Speaker 1>to the network and not have to have a router.

0:28:00.000 --> 0:28:01.800
<v Speaker 1>I don't know that you would necessarily want to do that,

0:28:01.880 --> 0:28:03.520
<v Speaker 1>because you might want the router in order to do

0:28:03.680 --> 0:28:06.960
<v Speaker 1>some traffic management on your end or to control access

0:28:07.119 --> 0:28:10.879
<v Speaker 1>to things. Obviously, direct access to devices could pose a

0:28:10.960 --> 0:28:14.200
<v Speaker 1>security risk as well. There are probably lots of considerations

0:28:14.280 --> 0:28:18.159
<v Speaker 1>to take their. Another consideration for the system as a

0:28:18.200 --> 0:28:22.560
<v Speaker 1>whole is going to be the management of all of

0:28:22.720 --> 0:28:27.000
<v Speaker 1>those those those yeah, yeah, are really really the management

0:28:27.000 --> 0:28:29.000
<v Speaker 1>of the data flow, I suppose. Yeah, So this was

0:28:29.119 --> 0:28:31.399
<v Speaker 1>really interesting to me. We've talked a lot about the

0:28:31.480 --> 0:28:34.440
<v Speaker 1>other other elements of five G one of the proposed ones,

0:28:34.480 --> 0:28:37.520
<v Speaker 1>and keep in mind, again this is an ongoing discussion,

0:28:37.800 --> 0:28:40.200
<v Speaker 1>so some of these things we're talking about may become

0:28:40.240 --> 0:28:42.920
<v Speaker 1>a reality, and whatever does become five G and some

0:28:43.040 --> 0:28:45.320
<v Speaker 1>of them maybe don't become a reality. But one of

0:28:45.400 --> 0:28:49.360
<v Speaker 1>the things that was mentioned at a conference Ericson CEO

0:28:49.600 --> 0:28:53.200
<v Speaker 1>Hans Vestberg said that the five G networks should be

0:28:53.240 --> 0:28:56.360
<v Speaker 1>able to respond in real time to the various demands

0:28:56.520 --> 0:28:59.920
<v Speaker 1>of devices that were on the network and be able

0:29:00.200 --> 0:29:04.160
<v Speaker 1>to to to facilitate those devices so it delivers the

0:29:04.240 --> 0:29:06.800
<v Speaker 1>best experience for whatever that device might be and whatever

0:29:06.920 --> 0:29:10.160
<v Speaker 1>the use case might be. So, for example, if you

0:29:10.400 --> 0:29:12.840
<v Speaker 1>have a mobile device in your streaming a movie and HD,

0:29:13.360 --> 0:29:15.600
<v Speaker 1>you would need to have that fast download rate to

0:29:15.680 --> 0:29:18.800
<v Speaker 1>accommodate that huge amount of data that's streaming to your device.

0:29:19.000 --> 0:29:21.720
<v Speaker 1>So the network would accommodate you and say, all right,

0:29:21.760 --> 0:29:24.720
<v Speaker 1>we're going to give this data rate to that device

0:29:24.840 --> 0:29:26.680
<v Speaker 1>because that's how much it needs in order to do

0:29:26.840 --> 0:29:29.960
<v Speaker 1>the thing that they've asked. Let's say, though, that you

0:29:30.080 --> 0:29:33.280
<v Speaker 1>have a driverless car that connects back to the network,

0:29:33.560 --> 0:29:38.440
<v Speaker 1>then you want extremely low latency because safety depends upon it.

0:29:38.600 --> 0:29:42.800
<v Speaker 1>You can't have a lag between uh, the detection of

0:29:43.200 --> 0:29:47.440
<v Speaker 1>something like a potential obstacle and its response. Yeah, I

0:29:47.520 --> 0:29:50.200
<v Speaker 1>mean that's tragic when it happens in Halo, but but

0:29:50.320 --> 0:29:54.200
<v Speaker 1>it's real tragic when it happens exactly so that this

0:29:54.320 --> 0:29:56.360
<v Speaker 1>would be a case where you would need to have

0:29:56.560 --> 0:30:00.160
<v Speaker 1>the least amount of latency possible. It also opens up

0:30:00.200 --> 0:30:03.040
<v Speaker 1>the possibility of something we've talked about before. Remember when

0:30:03.080 --> 0:30:06.560
<v Speaker 1>we started talking about the early ideas of the autonomous

0:30:06.640 --> 0:30:11.440
<v Speaker 1>car involved a system that cars would navigate through, and

0:30:11.840 --> 0:30:13.720
<v Speaker 1>it would the cars would just be one part of

0:30:13.760 --> 0:30:17.440
<v Speaker 1>the system. And how we have seen cars evolved so

0:30:17.560 --> 0:30:20.640
<v Speaker 1>that they're more independent, right, they don't tend to work

0:30:20.720 --> 0:30:22.960
<v Speaker 1>within a network. They're independent and they have all the

0:30:23.040 --> 0:30:25.600
<v Speaker 1>systems self enclosed in the car. This is kind of

0:30:25.680 --> 0:30:29.080
<v Speaker 1>shifting back to the possibility of having a big, uh

0:30:29.280 --> 0:30:34.360
<v Speaker 1>interdependent system which could have benefits over a bunch of

0:30:34.560 --> 0:30:38.520
<v Speaker 1>independent vehicles. Um, but we talked about that extensively in

0:30:38.560 --> 0:30:40.880
<v Speaker 1>our autonomous car episode, so I'll go back over it.

0:30:41.880 --> 0:30:45.280
<v Speaker 1>Or you could have even the ability for the network too.

0:30:45.320 --> 0:30:48.600
<v Speaker 1>Sense when a gadget's batteries running low. So let's say

0:30:48.640 --> 0:30:51.080
<v Speaker 1>that you've been using your phone all day and you're

0:30:51.120 --> 0:30:53.040
<v Speaker 1>not home yet you want your phone to last a

0:30:53.080 --> 0:30:56.320
<v Speaker 1>little longer, and your phone is aware that the battery

0:30:56.640 --> 0:30:59.920
<v Speaker 1>is down to like, so now the network is a

0:31:00.040 --> 0:31:03.280
<v Speaker 1>where that your phone's batteries down, and it starts to

0:31:03.400 --> 0:31:06.440
<v Speaker 1>ping your phone less frequently to make sure that your

0:31:06.480 --> 0:31:10.000
<v Speaker 1>phone is still connected. And because it's pinging it less frequently,

0:31:10.040 --> 0:31:13.320
<v Speaker 1>sending it updates less frequently, your phone is just sipping

0:31:13.520 --> 0:31:15.840
<v Speaker 1>at that battery power instead of gulping it down, and

0:31:15.920 --> 0:31:19.000
<v Speaker 1>it extends the battery life of your device, which is

0:31:19.080 --> 0:31:23.800
<v Speaker 1>pretty cool. Yeah. Um. Other considerations would have to include

0:31:24.560 --> 0:31:29.040
<v Speaker 1>cooperation with previous networks, because part of what five G

0:31:29.160 --> 0:31:31.960
<v Speaker 1>would have to do to to be successful is leave

0:31:32.080 --> 0:31:34.760
<v Speaker 1>room for older devices that are only capable of connecting

0:31:34.880 --> 0:31:38.360
<v Speaker 1>through three or four. Yeah. That's that's a big issue,

0:31:38.480 --> 0:31:41.920
<v Speaker 1>right is you have to continue to support legacy devices

0:31:42.120 --> 0:31:45.080
<v Speaker 1>that backwards compatibility issue, right yeah, because not everyone is

0:31:45.160 --> 0:31:47.920
<v Speaker 1>able to. First of all, you never know when the

0:31:48.000 --> 0:31:49.720
<v Speaker 1>system is going to fail and you need the backup

0:31:49.760 --> 0:31:52.680
<v Speaker 1>systems there. Secondly, you never know when a system is

0:31:52.720 --> 0:31:54.360
<v Speaker 1>going to get overwhelmed. Like when I go to C

0:31:54.480 --> 0:31:56.640
<v Speaker 1>E S, I will often switch my phone so that

0:31:56.720 --> 0:31:59.520
<v Speaker 1>it uses a three G network and doesn't even look

0:31:59.560 --> 0:32:02.480
<v Speaker 1>for four G because it helps save me time and

0:32:02.600 --> 0:32:07.360
<v Speaker 1>effort and frustrationttery and battery exactly. Uh. And also, not

0:32:07.520 --> 0:32:11.360
<v Speaker 1>everyone can upgrade at the same time, right, Like if

0:32:11.440 --> 0:32:14.200
<v Speaker 1>we all were magically given five G phones as soon

0:32:14.280 --> 0:32:16.520
<v Speaker 1>as it came out. It'd be awesome, and we say, oh,

0:32:16.600 --> 0:32:18.240
<v Speaker 1>we don't need these other things. But that's not the

0:32:18.240 --> 0:32:20.200
<v Speaker 1>way the world works. I probably won't get a five

0:32:20.240 --> 0:32:24.160
<v Speaker 1>G phone until six G comes out. You know. Another

0:32:24.240 --> 0:32:28.600
<v Speaker 1>thing about this next generation generation in quotes is that

0:32:28.680 --> 0:32:33.240
<v Speaker 1>people are talking about using different radio bandwidths, these high

0:32:33.320 --> 0:32:38.160
<v Speaker 1>frequency bandwidths that could transmit a lot more data, right, sure,

0:32:38.880 --> 0:32:41.880
<v Speaker 1>but they would also have drawbacks to write, yeah, yeah,

0:32:42.120 --> 0:32:45.840
<v Speaker 1>this the more data can only be transferred across shorter

0:32:46.000 --> 0:32:49.560
<v Speaker 1>distances due to the physical properties of these particular high

0:32:49.640 --> 0:32:54.760
<v Speaker 1>frequency radio waves. You would need a lot more towers

0:32:54.840 --> 0:32:57.440
<v Speaker 1>and based stations and all of that and uh and

0:32:57.840 --> 0:33:01.600
<v Speaker 1>better antenna technology would would have to be another development. Yeah,

0:33:01.880 --> 0:33:05.360
<v Speaker 1>because I mean that that becomes sort of a a

0:33:05.480 --> 0:33:08.360
<v Speaker 1>social barrier, not a technological barrier in a way, because

0:33:08.480 --> 0:33:10.320
<v Speaker 1>then you've got people saying, I really don't want a

0:33:10.400 --> 0:33:13.600
<v Speaker 1>cell phone tower erected in my neighborhood, right, I don't.

0:33:13.640 --> 0:33:17.040
<v Speaker 1>I don't want that here, um or or or or

0:33:17.120 --> 0:33:21.280
<v Speaker 1>even you know the possibility of of like cellular desserts

0:33:21.360 --> 0:33:23.640
<v Speaker 1>the way that we have some nutritional deserts and in

0:33:24.080 --> 0:33:28.360
<v Speaker 1>large areas. Yes, so you could have really underserved areas,

0:33:28.800 --> 0:33:32.200
<v Speaker 1>So you might have some parts that are just swimming

0:33:32.280 --> 0:33:36.400
<v Speaker 1>in gigabits and other bits where other areas where you know,

0:33:36.560 --> 0:33:39.160
<v Speaker 1>you just that service just immediately drops out and until

0:33:39.240 --> 0:33:42.040
<v Speaker 1>you get to another densely populated area, you don't get

0:33:42.080 --> 0:33:45.400
<v Speaker 1>that service across the county line and you can't stream

0:33:45.480 --> 0:33:48.960
<v Speaker 1>blue rays constantly. Well, what's what's the timeline we're looking

0:33:49.040 --> 0:33:51.360
<v Speaker 1>at here? You know, we're talking a lot about the future.

0:33:51.480 --> 0:33:53.920
<v Speaker 1>How far into the future are we you talking about? Well,

0:33:54.600 --> 0:33:58.600
<v Speaker 1>two companies have talked about setting up temporary five gen

0:33:58.640 --> 0:34:02.400
<v Speaker 1>networks as soon as twenty eighteen UM Samsung for the

0:34:03.200 --> 0:34:07.320
<v Speaker 1>Winter Olympics in South Korea. And who a is that?

0:34:07.520 --> 0:34:09.839
<v Speaker 1>Is that? How you say that? I'm gonna I'm gonna

0:34:09.880 --> 0:34:15.040
<v Speaker 1>say yes because I hualei. That sounds too much like

0:34:15.120 --> 0:34:19.040
<v Speaker 1>it came from Anchorman. Yes, that one for for the

0:34:19.120 --> 0:34:22.719
<v Speaker 1>World Cup in Moscow the same year. Both of those

0:34:22.800 --> 0:34:27.600
<v Speaker 1>goals I think are ridiculously ambitious. I mean maybe, I

0:34:27.680 --> 0:34:29.560
<v Speaker 1>mean it's it's really hard to say for sure how

0:34:29.800 --> 0:34:31.680
<v Speaker 1>how this technology is going to develop over the next

0:34:31.719 --> 0:34:34.759
<v Speaker 1>few years. Is the date that I've seen floated for

0:34:35.400 --> 0:34:38.560
<v Speaker 1>commercial availability. And I know that Japan is hoping to

0:34:38.640 --> 0:34:42.560
<v Speaker 1>have a permanent network available for the twenty Summer Olympics.

0:34:43.719 --> 0:34:48.720
<v Speaker 1>But you know, I mean, amazing things can happen. Maybe

0:34:48.800 --> 0:34:51.319
<v Speaker 1>that could happen, But even if it does, I would

0:34:51.320 --> 0:34:53.200
<v Speaker 1>I would guess that it's going to be a much

0:34:53.280 --> 0:34:57.320
<v Speaker 1>longer period of time before five G completely overtakes the

0:34:57.400 --> 0:35:01.040
<v Speaker 1>prior networks, right, And even even if they build out

0:35:01.080 --> 0:35:03.640
<v Speaker 1>the network, you're still you still have to have the

0:35:03.719 --> 0:35:06.360
<v Speaker 1>technology to actually take advantage of that. So I imagine

0:35:06.880 --> 0:35:10.320
<v Speaker 1>that that technology will largely be limited to things like

0:35:10.440 --> 0:35:14.799
<v Speaker 1>broadcast stations that happened to have the capability of having

0:35:15.080 --> 0:35:18.600
<v Speaker 1>commercial level technology that can tappen, Because I mean, if

0:35:18.600 --> 0:35:22.200
<v Speaker 1>it's a temporary thing that's up for the Olympics, how

0:35:22.320 --> 0:35:25.200
<v Speaker 1>do they sell that to consumers? Hey, this phone is

0:35:25.200 --> 0:35:28.880
<v Speaker 1>going to be really fast for like two weeks, and

0:35:28.960 --> 0:35:31.520
<v Speaker 1>then it's gonna be not so fast because we're shutting

0:35:31.560 --> 0:35:33.719
<v Speaker 1>down the network. Yeah, I'm sure that it's some kind

0:35:33.760 --> 0:35:37.480
<v Speaker 1>of like promotional thing, uh, Sam Sung, Like, especially a

0:35:37.680 --> 0:35:40.600
<v Speaker 1>creator like Samsung who also has a hardware side of

0:35:40.640 --> 0:35:43.560
<v Speaker 1>the business, Um, would you know use that as a

0:35:43.600 --> 0:35:46.960
<v Speaker 1>promotional opportunity to give journalists. Their fancy cell phones are

0:35:48.840 --> 0:35:54.440
<v Speaker 1>five G burner phones. Yeah, yeah, I watched so much

0:35:54.560 --> 0:35:58.120
<v Speaker 1>Netflix in such a short amount of time. So let's

0:35:58.160 --> 0:36:00.759
<v Speaker 1>talk about how this stuff could really changed our lives.

0:36:00.800 --> 0:36:02.520
<v Speaker 1>We mentioned it a little bit with the idea of

0:36:02.719 --> 0:36:07.480
<v Speaker 1>this being faster than than potentially faster than than fiber connections.

0:36:09.000 --> 0:36:14.279
<v Speaker 1>Potentially could be way faster than fiber connections, assuming that

0:36:14.480 --> 0:36:17.080
<v Speaker 1>a statistic we read was not in fact a typo,

0:36:17.120 --> 0:36:19.560
<v Speaker 1>which is so hard for me to believe. Yeah. So

0:36:19.719 --> 0:36:24.000
<v Speaker 1>the head of tech development project called the Innovation Center,

0:36:24.120 --> 0:36:27.120
<v Speaker 1>which is out of the University of Surrey, a person

0:36:27.200 --> 0:36:30.080
<v Speaker 1>by the name of him tough as Zoli. Yeah, oh,

0:36:30.120 --> 0:36:31.959
<v Speaker 1>I didn't look up any of these things. I'm usually

0:36:32.040 --> 0:36:33.719
<v Speaker 1>so good at looking picks up before I come into

0:36:33.760 --> 0:36:35.960
<v Speaker 1>the studio. I apologize if I just put you your name,

0:36:36.320 --> 0:36:39.520
<v Speaker 1>human person. Um I told told the BBC that he

0:36:39.600 --> 0:36:42.480
<v Speaker 1>thinks that five G could lend itself to eight hundred

0:36:42.920 --> 0:36:47.640
<v Speaker 1>gigabits per second. What you need to put that in

0:36:47.680 --> 0:36:49.960
<v Speaker 1>a phrase that I'm going to be able to comprehend.

0:36:50.320 --> 0:36:55.480
<v Speaker 1>That's like downloading thirty three HD movies per second, thirty

0:36:55.600 --> 0:36:59.919
<v Speaker 1>three HD movies per second per second, or like three

0:37:00.160 --> 0:37:05.160
<v Speaker 1>Peter Jackson movies. Um, and you know a lot of

0:37:05.200 --> 0:37:07.480
<v Speaker 1>people like the first My first reaction to this is

0:37:07.520 --> 0:37:09.600
<v Speaker 1>always like, what would I ever need with that speed?

0:37:09.680 --> 0:37:12.840
<v Speaker 1>But I've said that throughout my entire life and managed

0:37:12.880 --> 0:37:14.680
<v Speaker 1>to take advantage of it. And well, I said that

0:37:14.719 --> 0:37:16.080
<v Speaker 1>the first time I looked at three and a quarter

0:37:16.120 --> 0:37:18.680
<v Speaker 1>inch floppy does. Yeah. Well, it is one of those

0:37:18.719 --> 0:37:22.680
<v Speaker 1>principles in computing is that where capability emerges, people will

0:37:22.719 --> 0:37:25.239
<v Speaker 1>find ways to use it well. And with the emerging

0:37:25.920 --> 0:37:30.239
<v Speaker 1>technologies of four K and eight K resolution coming out,

0:37:31.480 --> 0:37:35.280
<v Speaker 1>you could easily see this being a way of getting

0:37:35.400 --> 0:37:38.000
<v Speaker 1>access to that kind of content so that you get

0:37:38.080 --> 0:37:42.760
<v Speaker 1>this ultra high definition experience delivered over something that doesn't

0:37:42.800 --> 0:37:45.920
<v Speaker 1>have a bottleneck to it. Uh. Now, obviously four K

0:37:46.040 --> 0:37:48.040
<v Speaker 1>and eight K are also going to rely very heavily

0:37:48.200 --> 0:37:52.400
<v Speaker 1>on sophisticated compression algorithms because otherwise the rest of us

0:37:52.440 --> 0:37:56.040
<v Speaker 1>would never be able to see it. But if you are,

0:37:56.280 --> 0:37:58.520
<v Speaker 1>if you have the ability to through put eight hundred

0:37:58.520 --> 0:38:03.280
<v Speaker 1>gigabits per second, action is not necessarily your your number

0:38:03.320 --> 0:38:08.200
<v Speaker 1>one concern. Yeah, maybe over overtaking your data plan in

0:38:08.440 --> 0:38:12.719
<v Speaker 1>like thirty seven minutes would be your major concern. You

0:38:12.800 --> 0:38:15.400
<v Speaker 1>had data plans, what would they even look like? That's crazy.

0:38:15.640 --> 0:38:17.560
<v Speaker 1>I mean a lot of the potential for this that

0:38:17.880 --> 0:38:20.319
<v Speaker 1>one of the easiest and most obvious things to point

0:38:20.360 --> 0:38:23.200
<v Speaker 1>out is the potential for streaming media, like we've been saying,

0:38:23.280 --> 0:38:26.279
<v Speaker 1>you know, streaming high definition movies and stuff. One of

0:38:26.320 --> 0:38:29.120
<v Speaker 1>the things I thought is how it could change what

0:38:29.280 --> 0:38:33.360
<v Speaker 1>could be done with like cloud computing and cloud gaming

0:38:33.560 --> 0:38:38.480
<v Speaker 1>for example. Um So, wouldn't this make cloud gaming basically

0:38:38.719 --> 0:38:42.680
<v Speaker 1>unstoppable because why would you shell out for like a

0:38:42.760 --> 0:38:46.520
<v Speaker 1>workhorse console like a PS four or an Xbox one

0:38:46.680 --> 0:38:50.920
<v Speaker 1>or something that has strong hardware and computing power when

0:38:51.040 --> 0:38:53.960
<v Speaker 1>really all you need is an internet connected display and

0:38:54.040 --> 0:38:57.320
<v Speaker 1>a controller of some kind. Well yeah, especially if that

0:38:57.680 --> 0:39:01.320
<v Speaker 1>if you can have a really working serve service, and

0:39:01.400 --> 0:39:05.960
<v Speaker 1>we've seen services that try and take this model, succeeding

0:39:06.080 --> 0:39:09.840
<v Speaker 1>to various degrees or not succeeding to various degrees. But

0:39:09.920 --> 0:39:12.960
<v Speaker 1>if you had this, this ability to transmit that much

0:39:13.080 --> 0:39:15.759
<v Speaker 1>data that quickly, it would remove a lot of the

0:39:15.840 --> 0:39:18.839
<v Speaker 1>barriers people have seen, especially things like latency and lag.

0:39:19.600 --> 0:39:22.919
<v Speaker 1>It would potentially remove those concerns so that you could

0:39:22.920 --> 0:39:26.040
<v Speaker 1>have a really satisfying gaming experience without having to have

0:39:26.200 --> 0:39:29.600
<v Speaker 1>that console in your home, and it sends this It

0:39:29.880 --> 0:39:32.040
<v Speaker 1>creates this ability for you to have a service run

0:39:32.520 --> 0:39:37.200
<v Speaker 1>where the service provider can make the investment to improve

0:39:37.320 --> 0:39:42.279
<v Speaker 1>hardware as hardware advances come along. And then, you know,

0:39:42.440 --> 0:39:45.440
<v Speaker 1>because of the the massive amount of revenue generated on

0:39:45.520 --> 0:39:48.560
<v Speaker 1>a subscription service or even a pay to play per

0:39:48.680 --> 0:39:53.120
<v Speaker 1>game service, uh, you know, it's not a concern. Whereas

0:39:53.400 --> 0:39:56.560
<v Speaker 1>if I'm a PC gamer, one of the big barriers

0:39:56.640 --> 0:39:59.560
<v Speaker 1>to entry is just the investment to get a good

0:40:00.280 --> 0:40:03.480
<v Speaker 1>like a really good gaming rig um, and then to

0:40:03.680 --> 0:40:05.880
<v Speaker 1>keep it in really good shape because knowing that in

0:40:06.040 --> 0:40:08.920
<v Speaker 1>six months to a year, a lot of my equipment

0:40:09.000 --> 0:40:12.000
<v Speaker 1>is going to go from good to passable, and then

0:40:12.120 --> 0:40:13.880
<v Speaker 1>another six months to a year it's going to go

0:40:13.960 --> 0:40:17.879
<v Speaker 1>from passible to not acceptable, which means I constantly need

0:40:17.920 --> 0:40:20.520
<v Speaker 1>to be upgrading my system. This way, the all the

0:40:20.640 --> 0:40:23.960
<v Speaker 1>upgrades happen on the back end, not on your console. Now,

0:40:24.120 --> 0:40:26.600
<v Speaker 1>it might also mean that your subscription fee goes up.

0:40:26.760 --> 0:40:31.240
<v Speaker 1>But yeah, well, I mean wouldn't you wouldn't you always

0:40:31.480 --> 0:40:36.959
<v Speaker 1>need a system capable of parsing that gigabits per second

0:40:37.960 --> 0:40:44.319
<v Speaker 1>turn into meaningful visual information. Yeah, depending on how Yeah,

0:40:44.440 --> 0:40:47.000
<v Speaker 1>it would depend on how your your cloud gaming ones

0:40:47.040 --> 0:40:49.840
<v Speaker 1>and runs. If you're just doing the sort of like

0:40:50.040 --> 0:40:53.279
<v Speaker 1>streaming media model, I mean, they're what's happening is that

0:40:53.360 --> 0:40:56.960
<v Speaker 1>the game is running entirely on the server, and it's

0:40:57.040 --> 0:40:59.520
<v Speaker 1>just it's the data it's taking from you is what

0:40:59.680 --> 0:41:02.200
<v Speaker 1>button you're pushing, and the data it's giving to you

0:41:02.560 --> 0:41:06.080
<v Speaker 1>is visual and auditory. It's essentially as if you're watching

0:41:06.120 --> 0:41:10.239
<v Speaker 1>a movie. Yeah, it just has to be. So the

0:41:10.320 --> 0:41:12.440
<v Speaker 1>point you're making is is a valid one, Lauren. The

0:41:12.840 --> 0:41:16.400
<v Speaker 1>device would have to be capable of accepting whatever that

0:41:16.600 --> 0:41:19.680
<v Speaker 1>minimum amount of information is for that game system to

0:41:19.800 --> 0:41:22.759
<v Speaker 1>work properly. Uh. And if you if you had a

0:41:22.800 --> 0:41:26.400
<v Speaker 1>bottleneck there, then obviously you would have to upgrade whatever,

0:41:26.600 --> 0:41:29.479
<v Speaker 1>like your smart TV or whatever it might be. Maybe

0:41:29.560 --> 0:41:33.200
<v Speaker 1>it's like a little dumb set top box that connects

0:41:33.200 --> 0:41:36.440
<v Speaker 1>to your TV that that just accepts the information and

0:41:36.520 --> 0:41:38.640
<v Speaker 1>sends the signals to the TV. But even that would

0:41:38.680 --> 0:41:42.240
<v Speaker 1>have to have the capacity to accept this massive amount

0:41:42.280 --> 0:41:45.120
<v Speaker 1>of information. Yeah, like we like we were saying before,

0:41:45.480 --> 0:41:47.520
<v Speaker 1>there are two sides of this, right, there's the system,

0:41:47.640 --> 0:41:50.160
<v Speaker 1>the back end side, and there's the consumer side, the

0:41:50.239 --> 0:41:55.120
<v Speaker 1>device and having something capable of delivering huge amounts of

0:41:55.239 --> 0:41:58.279
<v Speaker 1>data and having something capable of accepting huge amount of

0:41:58.360 --> 0:42:01.000
<v Speaker 1>data are two different things. Yeah, and you gotta have

0:42:01.080 --> 0:42:05.920
<v Speaker 1>both of them otherwise it's a really one sided conversation. Yeah, exactly,

0:42:06.160 --> 0:42:09.520
<v Speaker 1>Like my phone could download this movie in like point

0:42:09.560 --> 0:42:13.440
<v Speaker 1>five seconds if it anyone would send, if anyone was

0:42:13.520 --> 0:42:19.560
<v Speaker 1>sending a beautiful movie and wants to Another big implication

0:42:19.840 --> 0:42:21.840
<v Speaker 1>of five G, of course, is going to be for

0:42:21.880 --> 0:42:26.839
<v Speaker 1>the Internet of things, right right, And yeah, you were

0:42:26.880 --> 0:42:29.520
<v Speaker 1>talking about that earlier because you know, right now a

0:42:29.600 --> 0:42:32.520
<v Speaker 1>lot of people have more than one wireless device. But

0:42:32.880 --> 0:42:36.000
<v Speaker 1>by if you know, your fridge and your air conditioning

0:42:36.080 --> 0:42:39.239
<v Speaker 1>in your coffee pot, and your car and your stoplights

0:42:39.280 --> 0:42:42.560
<v Speaker 1>and your storm drains and whatever else are all connected

0:42:42.600 --> 0:42:45.239
<v Speaker 1>to the web. People are predicting that there could be

0:42:45.520 --> 0:42:50.680
<v Speaker 1>fifty to a hundred billion connected devices worldwide. Um, yeah,

0:42:50.760 --> 0:42:53.080
<v Speaker 1>so you've gotta have some means of being able to

0:42:53.840 --> 0:42:57.440
<v Speaker 1>to facilitate that huge number of connections. Yeah. Yeah, like

0:42:57.600 --> 0:43:00.960
<v Speaker 1>like we are going to need this more powerful generation

0:43:01.000 --> 0:43:03.239
<v Speaker 1>of wireless connectivity if if that future is going to

0:43:03.320 --> 0:43:06.480
<v Speaker 1>be possible, right Otherwise, you know, you might be cursing

0:43:06.560 --> 0:43:09.320
<v Speaker 1>the fact that your neighbor's got a smart kitchen outfitted

0:43:09.320 --> 0:43:11.400
<v Speaker 1>in their home because now you can't get a decent

0:43:11.680 --> 0:43:16.160
<v Speaker 1>phone signal. Yeah. And and and also also, like we

0:43:16.239 --> 0:43:20.080
<v Speaker 1>were talking about, those self driving cars would be of

0:43:20.200 --> 0:43:23.520
<v Speaker 1>particular benefit to the system because you know, having faster

0:43:23.680 --> 0:43:26.680
<v Speaker 1>and less clogged communication across the network would allow for

0:43:26.960 --> 0:43:30.960
<v Speaker 1>for smoother route mapping and better traffic control and that

0:43:31.080 --> 0:43:33.960
<v Speaker 1>emergency response that we were talking about earlier, where where

0:43:34.040 --> 0:43:36.719
<v Speaker 1>you know, if an accident does happen, then every car

0:43:36.800 --> 0:43:38.880
<v Speaker 1>on the road could be told to break, preventing a

0:43:39.160 --> 0:43:44.760
<v Speaker 1>pile up. Yeah. Yeah, that These are all incredible applications

0:43:44.960 --> 0:43:49.160
<v Speaker 1>of this technology or potential applications. Uh one, what one

0:43:49.239 --> 0:43:53.480
<v Speaker 1>more is is remote activities. Um, so you know, imagine

0:43:53.560 --> 0:43:57.000
<v Speaker 1>the best surgeon for your personal needs being able to

0:43:57.200 --> 0:44:00.359
<v Speaker 1>uh not only teleconsult with you from anywhere the world,

0:44:00.440 --> 0:44:03.399
<v Speaker 1>but also being able to operate a robotic surgical tool

0:44:04.040 --> 0:44:06.959
<v Speaker 1>from anywhere. Yeah, definitely. I mean one of the big

0:44:07.200 --> 0:44:11.279
<v Speaker 1>problems with telesurgery has been the latency problem. Yeah. Yeah.

0:44:11.360 --> 0:44:13.960
<v Speaker 1>There have been some examples of telesurgery that have been

0:44:14.520 --> 0:44:17.920
<v Speaker 1>kind of a a scary proof of concept, you know,

0:44:18.040 --> 0:44:20.960
<v Speaker 1>like people proving that this is a possible thing, but

0:44:21.040 --> 0:44:24.400
<v Speaker 1>they were using very dedicated lines for a for a

0:44:24.560 --> 0:44:29.560
<v Speaker 1>predetermined specific purpose. This would potentially open up the opportunity

0:44:29.680 --> 0:44:32.520
<v Speaker 1>of using it on a more regular basis. Instead of

0:44:32.600 --> 0:44:35.680
<v Speaker 1>it being this like we're we're proving that this is possible.

0:44:36.080 --> 0:44:39.360
<v Speaker 1>This would make it practical or at least a potential

0:44:39.480 --> 0:44:43.360
<v Speaker 1>practical solution to what could otherwise be a life threatening problem.

0:44:44.080 --> 0:44:47.080
<v Speaker 1>So yeah, I mean, these are all great examples of

0:44:47.160 --> 0:44:50.080
<v Speaker 1>how five G could end up being a huge benefit

0:44:50.160 --> 0:44:52.080
<v Speaker 1>to us, assuming that it all works out. I mean,

0:44:52.760 --> 0:44:55.719
<v Speaker 1>we're still talking about something that's still in the kind

0:44:55.719 --> 0:44:58.600
<v Speaker 1>of brainstorming phase. Yeah. I guess one of the main

0:44:58.760 --> 0:45:01.960
<v Speaker 1>questions is just how realistic is this? I mean, we're

0:45:02.360 --> 0:45:08.560
<v Speaker 1>looking at these extremely crazy optimistic predictions and uh, and personally,

0:45:08.640 --> 0:45:10.200
<v Speaker 1>I don't really know what to make of it. I mean,

0:45:10.239 --> 0:45:13.560
<v Speaker 1>I guess I don't know enough about cellular and wireless

0:45:13.600 --> 0:45:17.480
<v Speaker 1>technology to know what's actually plausible and what's just sort

0:45:17.520 --> 0:45:21.080
<v Speaker 1>of you know, people setting ambitious goals. Well, and if

0:45:21.160 --> 0:45:23.719
<v Speaker 1>you were able to actually roll this out, I mean,

0:45:23.760 --> 0:45:27.600
<v Speaker 1>there's there's going to be a lot of investment that's

0:45:27.640 --> 0:45:30.600
<v Speaker 1>going to be necessary to make this reality, where the

0:45:30.719 --> 0:45:34.120
<v Speaker 1>carriers will have to invest in upgrading their infrastructure. So

0:45:34.200 --> 0:45:37.240
<v Speaker 1>in other words, either building new towers or adding antenna

0:45:37.360 --> 0:45:41.759
<v Speaker 1>to existing towers, whatever however that might turn out. Um,

0:45:42.320 --> 0:45:44.360
<v Speaker 1>And so it's not like everyone's going to get it

0:45:45.239 --> 0:45:47.279
<v Speaker 1>at the same time. It'll be like all the other

0:45:47.360 --> 0:45:52.279
<v Speaker 1>networks rolled out where some some uh some networks got

0:45:52.600 --> 0:45:56.000
<v Speaker 1>access to three G and four G speeds well before

0:45:56.080 --> 0:45:58.719
<v Speaker 1>other ones did. So we're gonna price see that again.

0:45:59.560 --> 0:46:02.560
<v Speaker 1>So that's to take some time. But once that does happen,

0:46:02.840 --> 0:46:07.719
<v Speaker 1>and once five G becomes more widely adopted, Uh, the

0:46:07.840 --> 0:46:11.000
<v Speaker 1>question I have is what happens to all the wired infrastructure,

0:46:11.200 --> 0:46:13.640
<v Speaker 1>Like do we keep it? I mean, it makes sense

0:46:13.719 --> 0:46:16.560
<v Speaker 1>to keep it as a backup anyway in case in

0:46:16.760 --> 0:46:19.279
<v Speaker 1>case something happens to the wireless network. But at the

0:46:19.320 --> 0:46:23.319
<v Speaker 1>same time, if you're talking about having wireless transmission rates

0:46:23.480 --> 0:46:28.160
<v Speaker 1>that dwarf you know, wired rates to the point where

0:46:28.760 --> 0:46:32.320
<v Speaker 1>it's it's a factor of ten or more, then you

0:46:32.400 --> 0:46:35.200
<v Speaker 1>start to question why do we even have these like

0:46:35.440 --> 0:46:38.560
<v Speaker 1>wires up? Should we take them down? Will it become

0:46:38.640 --> 0:46:41.640
<v Speaker 1>like the wired telephone in your house where you're like, oh,

0:46:41.800 --> 0:46:44.600
<v Speaker 1>don't answer any email from the wired internet connection. We

0:46:44.760 --> 0:46:48.719
<v Speaker 1>just know that's a yeah, I mean, it's it's an

0:46:48.840 --> 0:46:52.960
<v Speaker 1>interesting question. I expect that we will have for a

0:46:53.120 --> 0:46:57.719
<v Speaker 1>long time, will have all of these various infrastructures running concurrently,

0:46:57.840 --> 0:47:01.840
<v Speaker 1>because again, not every is going to magically get upgraded

0:47:02.239 --> 0:47:04.640
<v Speaker 1>and be able to take advantage of this kind of stuff.

0:47:04.760 --> 0:47:06.640
<v Speaker 1>So it's going to be one of those things that

0:47:07.480 --> 0:47:09.960
<v Speaker 1>if it's a transition, it will be a gradual transition.

0:47:10.040 --> 0:47:12.600
<v Speaker 1>Maybe we're talking ten or twenty years down the road

0:47:12.680 --> 0:47:16.440
<v Speaker 1>before enough people have gotten off the legacy systems for

0:47:16.520 --> 0:47:19.279
<v Speaker 1>those to be shut down. I mean, sometimes you just

0:47:19.480 --> 0:47:22.680
<v Speaker 1>have to pull the plug and you just say listen,

0:47:22.840 --> 0:47:26.839
<v Speaker 1>at X date this change is going to happen. Uh,

0:47:26.920 --> 0:47:29.839
<v Speaker 1>here are some programs to help you get caught up

0:47:30.280 --> 0:47:33.680
<v Speaker 1>if you are left behind. But we still have to

0:47:33.800 --> 0:47:36.960
<v Speaker 1>do this because, uh, it's it only makes sense for

0:47:37.080 --> 0:47:40.640
<v Speaker 1>us to to concentrate on these existing infrastructures and not

0:47:41.120 --> 0:47:45.600
<v Speaker 1>continue to support something that is technically obsolete. Okay, well,

0:47:45.640 --> 0:47:48.680
<v Speaker 1>I still be able to use all those promotional CDs

0:47:48.760 --> 0:47:50.800
<v Speaker 1>I got for a O L and Prodigy back And

0:47:51.440 --> 0:47:53.640
<v Speaker 1>if you had said compu Serve, I would have had

0:47:53.680 --> 0:47:58.360
<v Speaker 1>good news for you, Joe. But sadly, I'm going to

0:47:58.520 --> 0:48:00.759
<v Speaker 1>leave that question an answer to yes one more thing

0:48:00.800 --> 0:48:02.560
<v Speaker 1>before we leave real quick though, UHH And I do

0:48:02.640 --> 0:48:06.759
<v Speaker 1>want to mention that all of this also ties into

0:48:07.480 --> 0:48:11.840
<v Speaker 1>the infrastructural use of air waves, of radio waves, and

0:48:12.600 --> 0:48:16.120
<v Speaker 1>what the future holds for for various forms of communication

0:48:16.640 --> 0:48:18.920
<v Speaker 1>will have an impact on all of these systems that

0:48:19.000 --> 0:48:21.400
<v Speaker 1>we're trying to create exactly. Yeah, I mean, we have

0:48:21.640 --> 0:48:25.080
<v Speaker 1>to we have to make space available for this stuff.

0:48:25.320 --> 0:48:27.640
<v Speaker 1>And the question is do we take it away from

0:48:27.719 --> 0:48:30.800
<v Speaker 1>something else? Do we just go with the small gaps

0:48:30.880 --> 0:48:34.120
<v Speaker 1>that still exist between certain bandwidths? Uh? You know, there's

0:48:34.160 --> 0:48:37.880
<v Speaker 1>certain bandwidths that that stopped being used and the FCC

0:48:38.040 --> 0:48:40.640
<v Speaker 1>started auctioning them off here in the United States. Is

0:48:40.760 --> 0:48:43.880
<v Speaker 1>that potentially a use for this kind of technology? Uh?

0:48:44.000 --> 0:48:45.800
<v Speaker 1>There are a lot of questions that we don't have

0:48:45.920 --> 0:48:50.000
<v Speaker 1>the answers to, like practical questions, and uh, and some

0:48:50.160 --> 0:48:53.040
<v Speaker 1>of them are going to have some tough answers, because

0:48:53.120 --> 0:48:54.960
<v Speaker 1>eventually we're going to get to a point where we said,

0:48:54.960 --> 0:48:57.680
<v Speaker 1>all right, we've used all the frequencies that can we

0:48:57.760 --> 0:49:02.120
<v Speaker 1>can expect to usefully deliver data. Right beyond this, we

0:49:02.280 --> 0:49:04.480
<v Speaker 1>can't really either the data transmission is going to be

0:49:04.560 --> 0:49:07.320
<v Speaker 1>so low or the distance is going to be so short,

0:49:07.760 --> 0:49:10.440
<v Speaker 1>that's not a practical use anymore. At that point, we

0:49:10.520 --> 0:49:12.799
<v Speaker 1>have to start saying, all right, why do we get

0:49:12.880 --> 0:49:14.720
<v Speaker 1>rid of so that we can have this new shiny

0:49:14.840 --> 0:49:19.319
<v Speaker 1>thing the that's gonna be tough. Uh So, maybe that's

0:49:19.360 --> 0:49:22.160
<v Speaker 1>an excuse not to connect our toasters to the internet.

0:49:22.320 --> 0:49:28.120
<v Speaker 1>Maybe maybe you know, we can't let fear dictate our

0:49:28.400 --> 0:49:31.080
<v Speaker 1>our pathway to the future, and gosh darn it, I

0:49:31.160 --> 0:49:34.320
<v Speaker 1>want Internet connected toast all right. So, guys, if you

0:49:34.440 --> 0:49:37.480
<v Speaker 1>have any suggestions for future topics that we can talk

0:49:37.520 --> 0:49:40.320
<v Speaker 1>about here on forward Thinking. Maybe there's something you've always

0:49:40.320 --> 0:49:42.440
<v Speaker 1>wondered about, like how is that going to work in

0:49:42.480 --> 0:49:45.239
<v Speaker 1>the future, or you just have questions or comments about

0:49:45.239 --> 0:49:47.319
<v Speaker 1>stuff we've said, Get in touch with us. Send us

0:49:47.320 --> 0:49:51.240
<v Speaker 1>an email the addresses f W Thinking at how Stuff

0:49:51.280 --> 0:49:53.800
<v Speaker 1>Works dot com, or you can drop us a line

0:49:53.920 --> 0:49:57.640
<v Speaker 1>on Twitter, Google Plus or Facebook. At Twitter and Google Plus,

0:49:57.680 --> 0:50:00.480
<v Speaker 1>we are f W Thinking on Facebook US search f

0:50:00.640 --> 0:50:02.720
<v Speaker 1>W Thinking. We'll pop right up, leave us a message

0:50:03.040 --> 0:50:09.960
<v Speaker 1>and we'll talk to you again really soon. For more

0:50:10.000 --> 0:50:12.560
<v Speaker 1>on this topic in the future of technology, I'll visit

0:50:12.640 --> 0:50:25.080
<v Speaker 1>forward Thinking dot com. H brought to you by Toyota.

0:50:25.560 --> 0:50:26.520
<v Speaker 1>Let's go places