WEBVTT - Shedding Light on Li-Fi

0:00:00.160 --> 0:00:07.160
<v Speaker 1>Brought to you by Toyota. Let's go places. Welcome to

0:00:07.360 --> 0:00:15.720
<v Speaker 1>Forward Thinking. Hey guys, it's Forward Thinking. I'm Jonathan Strickland, Obama,

0:00:15.760 --> 0:00:19.400
<v Speaker 1>and we are still back. If you listen to the

0:00:19.440 --> 0:00:22.280
<v Speaker 1>previous episode Water on Mars, you know that we were

0:00:22.320 --> 0:00:24.799
<v Speaker 1>on hiatus for a while. We are now back and

0:00:24.920 --> 0:00:28.320
<v Speaker 1>this is the second of two episodes we recorded before

0:00:28.400 --> 0:00:31.600
<v Speaker 1>we were officially on hiatus, but we back in October,

0:00:33.240 --> 0:00:35.280
<v Speaker 1>so we're gonna tell you the future of the past.

0:00:36.040 --> 0:00:38.080
<v Speaker 1>Um yeah, this is this is something that we recorded

0:00:38.080 --> 0:00:41.920
<v Speaker 1>back in October two fifteen. It's all about LiFi and

0:00:42.120 --> 0:00:44.760
<v Speaker 1>uh so some of the references maybe a tad dated

0:00:45.000 --> 0:00:48.159
<v Speaker 1>because we were recording a few months ago, but we

0:00:48.240 --> 0:00:50.239
<v Speaker 1>wanted to release it because we were really proud of it.

0:00:50.280 --> 0:00:52.160
<v Speaker 1>I thought it was a good episode, and we've got

0:00:52.200 --> 0:00:55.080
<v Speaker 1>lots of new episodes coming up in the next year,

0:00:55.200 --> 0:00:57.960
<v Speaker 1>so we wanted to get back onto on track, get

0:00:58.000 --> 0:01:01.639
<v Speaker 1>things going. And I hope you enjoy this now classic

0:01:01.760 --> 0:01:08.160
<v Speaker 1>new episode of Forward Thinking. Hey there, and welcome to

0:01:08.280 --> 0:01:11.399
<v Speaker 1>Forward Thinking, the podcast that looks at the future and

0:01:11.440 --> 0:01:15.160
<v Speaker 1>says there's a light over at the Frankenstein Place. I'm

0:01:15.280 --> 0:01:20.200
<v Speaker 1>Jonathan Strickland and I'm Joe McCormick. Hey, so guys, you know,

0:01:20.640 --> 0:01:24.240
<v Speaker 1>we talked about something, uh a year ago or so.

0:01:24.319 --> 0:01:28.399
<v Speaker 1>We're recording this in October two thousand and fifteen, but

0:01:28.680 --> 0:01:33.520
<v Speaker 1>about a year ago September, we talked about a problem

0:01:33.560 --> 0:01:38.040
<v Speaker 1>that's happening, and it's happening across the developed world places

0:01:38.080 --> 0:01:42.160
<v Speaker 1>where the Internet has reached real penetration. And that problem

0:01:42.280 --> 0:01:45.119
<v Speaker 1>is that a lot of the devices we use rely

0:01:45.400 --> 0:01:50.040
<v Speaker 1>on radio signals to communicate with the infrastructure that connects

0:01:50.080 --> 0:01:55.320
<v Speaker 1>to the Internet backbone. The spectrum crunch exactly, the spectrum crunch.

0:01:55.760 --> 0:01:58.200
<v Speaker 1>That's a real issue. And the issue is not something

0:01:58.240 --> 0:02:00.480
<v Speaker 1>where like you have an a limit that amount of

0:02:00.560 --> 0:02:03.240
<v Speaker 1>radio in the entire world and it's all gonna go away.

0:02:03.320 --> 0:02:06.760
<v Speaker 1>It's very much a a kind of a congestion. Think

0:02:06.760 --> 0:02:10.040
<v Speaker 1>of it like a traffic jam in a particular region. Yeah.

0:02:10.080 --> 0:02:12.200
<v Speaker 1>For the same reason that they ask you to put

0:02:12.240 --> 0:02:15.480
<v Speaker 1>your phone on airplane mode when you're in an airplane,

0:02:15.960 --> 0:02:19.360
<v Speaker 1>is this thing that we're talking about, because signal interference

0:02:19.440 --> 0:02:22.880
<v Speaker 1>can become a very serious issue in that case. Well,

0:02:22.919 --> 0:02:24.919
<v Speaker 1>not only just signal interference, but if you've got too

0:02:24.919 --> 0:02:27.480
<v Speaker 1>many Like have you ever been in let's say a

0:02:28.040 --> 0:02:30.320
<v Speaker 1>really crowded coffee shop and you want to connect to

0:02:30.320 --> 0:02:33.239
<v Speaker 1>the WiFi there, but you occasionally find that you're being

0:02:33.280 --> 0:02:36.200
<v Speaker 1>bumped off the WiFi or things are really slowing down

0:02:36.200 --> 0:02:40.240
<v Speaker 1>and clogging up. Often it's because whatever WiFi router the

0:02:40.440 --> 0:02:43.480
<v Speaker 1>coffee shop is using has a lower capacity than what

0:02:43.639 --> 0:02:46.840
<v Speaker 1>is being demanded of it. So, in other words, there

0:02:46.919 --> 0:02:50.200
<v Speaker 1>are the devices we use have a limited ability to

0:02:50.320 --> 0:02:53.880
<v Speaker 1>deal with the demand that we are placing upon them,

0:02:53.919 --> 0:02:56.280
<v Speaker 1>and it's getting worse by the day because not only

0:02:56.320 --> 0:02:59.679
<v Speaker 1>are we getting more smartphones and tablets and smart watches

0:02:59.720 --> 0:03:02.160
<v Speaker 1>and all this other stuff that's using those radio waves,

0:03:02.400 --> 0:03:05.880
<v Speaker 1>were also entering the era of the Internet of Things,

0:03:05.960 --> 0:03:08.960
<v Speaker 1>which is requiring even more stuff to connect to the

0:03:09.000 --> 0:03:13.239
<v Speaker 1>Your fridge in your car, tires and your cube, connect

0:03:13.280 --> 0:03:17.840
<v Speaker 1>to the internet, your cuff links, your dog's color, your hatchet. Yes,

0:03:18.360 --> 0:03:21.960
<v Speaker 1>our mystical acts is um not WiFi enabled, but we're

0:03:21.960 --> 0:03:26.760
<v Speaker 1>getting an upgrade, sobe is on the internet. Joe failed

0:03:26.800 --> 0:03:29.840
<v Speaker 1>to solve me again, that would essentially it would just

0:03:29.880 --> 0:03:31.919
<v Speaker 1>be a message like that for me all the time.

0:03:32.360 --> 0:03:37.800
<v Speaker 1>Jonathan has has low spatial awareness. H so uh. The

0:03:37.880 --> 0:03:39.600
<v Speaker 1>interesting thing here is that this problem is not going

0:03:39.640 --> 0:03:41.520
<v Speaker 1>to go away. It's not gonna it's not gonna get

0:03:41.560 --> 0:03:44.000
<v Speaker 1>any easier. In fact, there are places like here in

0:03:44.000 --> 0:03:49.920
<v Speaker 1>the United States that have recently declared broadband access as

0:03:49.960 --> 0:03:53.120
<v Speaker 1>being a necessity not a luxury. There was a White

0:03:53.120 --> 0:03:57.800
<v Speaker 1>House report that came out earlier in that's specifically called

0:03:57.840 --> 0:04:02.920
<v Speaker 1>out broadband access as a necessity, and they defined broadband

0:04:02.920 --> 0:04:05.160
<v Speaker 1>as I think twenty five megabits per second are faster,

0:04:05.960 --> 0:04:09.160
<v Speaker 1>mean saying like electricity, right, yeah, yeah, Well because because

0:04:09.200 --> 0:04:14.200
<v Speaker 1>knowledge and interconnectivity is critical in this our modern world. Yes,

0:04:14.280 --> 0:04:17.359
<v Speaker 1>we we rely on it for communication, we rely on

0:04:17.440 --> 0:04:23.080
<v Speaker 1>it for commerce. So we have this this problem, and

0:04:23.160 --> 0:04:28.320
<v Speaker 1>we have this, uh more, this increasing urgency to find

0:04:28.320 --> 0:04:30.720
<v Speaker 1>a way of dealing with it. Um And there are

0:04:30.720 --> 0:04:34.560
<v Speaker 1>other issues with WiFi. Besides the fact that they you

0:04:34.640 --> 0:04:38.960
<v Speaker 1>can have a capacity crunch in any given time and place,

0:04:39.000 --> 0:04:42.520
<v Speaker 1>depending upon demand. Another is that they're not always that

0:04:42.720 --> 0:04:46.320
<v Speaker 1>efficient to use these radio waves. In fact, that's all

0:04:46.360 --> 0:04:50.440
<v Speaker 1>they do, and so you're dedicating them to this one purpose.

0:04:50.920 --> 0:04:55.520
<v Speaker 1>And I think the um the percentage I saw was

0:04:55.560 --> 0:04:58.039
<v Speaker 1>that they are essentially five percent efficient in the amount

0:04:58.040 --> 0:04:59.919
<v Speaker 1>of energy you're using them and the amount of actual

0:05:00.040 --> 0:05:03.880
<v Speaker 1>work they're doing. Yeah, energy you're pouring into these things

0:05:04.600 --> 0:05:09.760
<v Speaker 1>is just being bled away. Also, like you were saying, Lauren,

0:05:09.920 --> 0:05:12.480
<v Speaker 1>you've got the problem with interference. You know. That's why

0:05:12.600 --> 0:05:18.080
<v Speaker 1>you aren't allowed to use devices in on airplanes unless

0:05:18.120 --> 0:05:21.599
<v Speaker 1>you've switched it to WiFi. You can't use the cellular data. Um,

0:05:21.640 --> 0:05:24.600
<v Speaker 1>you can't use them in places like hospitals where it

0:05:24.680 --> 0:05:28.680
<v Speaker 1>might interfere with medical equipment. That's another issue. I've got

0:05:28.680 --> 0:05:32.040
<v Speaker 1>a complaint. When I wrap my computer up in aluminum foil,

0:05:32.120 --> 0:05:34.559
<v Speaker 1>it can't get a WiFi signal, right, But they also

0:05:34.680 --> 0:05:38.839
<v Speaker 1>can't I can't see what you're doing anymore, right, So

0:05:39.320 --> 0:05:41.320
<v Speaker 1>that is the important part. That's we call it our

0:05:41.640 --> 0:05:44.720
<v Speaker 1>essay protection case. And you can't see what you're doing

0:05:44.760 --> 0:05:49.080
<v Speaker 1>anymore either, so your fragile sanity. He's trying to come

0:05:49.160 --> 0:05:52.800
<v Speaker 1>up with some transparent aluminum foil. I've got a movie

0:05:52.880 --> 0:05:57.440
<v Speaker 1>for you to watch. Uh So another issue, and I

0:05:57.440 --> 0:05:59.680
<v Speaker 1>didn't even put this in our notes, but another one

0:06:00.279 --> 0:06:03.200
<v Speaker 1>needs to be addressed is the notion of security. I mean,

0:06:03.240 --> 0:06:07.560
<v Speaker 1>obviously there's the you've always heard. I'm sure you guys

0:06:07.600 --> 0:06:10.880
<v Speaker 1>out there have heard that things like like open WiFi

0:06:10.960 --> 0:06:15.080
<v Speaker 1>networks are risky because you never know who else is

0:06:15.120 --> 0:06:18.520
<v Speaker 1>on that network and who might be intercepting your data? Right, Jonathan,

0:06:18.560 --> 0:06:21.080
<v Speaker 1>Earlier you were like, you go to a coffee shop

0:06:21.120 --> 0:06:24.800
<v Speaker 1>and use their WiFi. I'm like, no, you don't. Well,

0:06:25.520 --> 0:06:27.560
<v Speaker 1>it depends on the coffee shop too, right, I mean

0:06:27.560 --> 0:06:30.360
<v Speaker 1>it depends on It depends on multiple things, like is

0:06:30.400 --> 0:06:33.000
<v Speaker 1>the is the WiFi protected in the coffee shop. Even

0:06:33.040 --> 0:06:35.760
<v Speaker 1>if it is, there's still the chance it's unsecured. But

0:06:35.880 --> 0:06:39.320
<v Speaker 1>if it's secured, the password is coffee, right, or or

0:06:39.480 --> 0:06:42.040
<v Speaker 1>one to three coffee or something along those lines. But

0:06:42.279 --> 0:06:44.839
<v Speaker 1>you know, even with all those things, Uh, if you're

0:06:45.880 --> 0:06:48.440
<v Speaker 1>not doing your banking or whatever, maybe you're not too

0:06:48.480 --> 0:06:54.719
<v Speaker 1>concerned about it. But one potential solution to all of

0:06:54.720 --> 0:06:59.360
<v Speaker 1>these problems is to replace the radio part of this communication,

0:06:59.480 --> 0:07:05.000
<v Speaker 1>the the communication between devices and the infrastructure that connects

0:07:05.000 --> 0:07:07.919
<v Speaker 1>to the Internet backbone, with something besides radio. So a

0:07:08.040 --> 0:07:11.240
<v Speaker 1>guy standing up on a table in the room holding

0:07:11.320 --> 0:07:15.240
<v Speaker 1>flags up, uh, well, similar in that the communication would

0:07:15.280 --> 0:07:18.760
<v Speaker 1>depend upon light. And if we wanted to use flags,

0:07:18.800 --> 0:07:20.920
<v Speaker 1>then obviously light as necessary because I don't know if

0:07:20.960 --> 0:07:25.160
<v Speaker 1>you've tried to communicate via semaphore and pitch darkness with

0:07:25.360 --> 0:07:30.200
<v Speaker 1>unlit flags not terribly productive. What if the flags are

0:07:30.200 --> 0:07:32.600
<v Speaker 1>glow in the dark, that's different then you've got but

0:07:32.640 --> 0:07:35.440
<v Speaker 1>there's some blurring issues too. I guess the flags probably

0:07:35.440 --> 0:07:37.920
<v Speaker 1>would mean it would take a long time to download

0:07:37.960 --> 0:07:41.080
<v Speaker 1>a file. So what's something that we're talking about like

0:07:41.280 --> 0:07:47.400
<v Speaker 1>the bond modem days, So what's something that would be

0:07:47.440 --> 0:07:49.920
<v Speaker 1>a little bit faster than a guy holding up flag signals?

0:07:50.000 --> 0:07:53.920
<v Speaker 1>Actual light, I mean actually using light in place of

0:07:54.080 --> 0:07:58.160
<v Speaker 1>radio waves, like pulses of light kind of yeah, like

0:07:58.160 --> 0:08:03.080
<v Speaker 1>like changing the amplitude of light, so the intensity of light, uh,

0:08:03.120 --> 0:08:07.080
<v Speaker 1>in order to communicate, which is not the unusual. Yeah, yeah, well,

0:08:07.120 --> 0:08:08.720
<v Speaker 1>I mean we we've been doing it for a very

0:08:08.840 --> 0:08:11.160
<v Speaker 1>very long time. But we're talking about something that would

0:08:11.160 --> 0:08:16.880
<v Speaker 1>have to move a little bit faster than for example, uh, beacons, right, yes,

0:08:16.920 --> 0:08:20.240
<v Speaker 1>like the old days where you know the you're you,

0:08:20.240 --> 0:08:24.520
<v Speaker 1>you are a messenger and you see that there are

0:08:25.000 --> 0:08:27.880
<v Speaker 1>invaders coming in at the northern border of the country

0:08:27.920 --> 0:08:29.800
<v Speaker 1>you live in, so you light the beacon to alert

0:08:29.840 --> 0:08:31.760
<v Speaker 1>everybody else. It's that's seen in the Lord of the

0:08:31.800 --> 0:08:34.280
<v Speaker 1>Rings where they like the beacon to U to call

0:08:34.400 --> 0:08:38.560
<v Speaker 1>the who are the writers of rowan? Yes, don't test me, buddy,

0:08:39.400 --> 0:08:41.720
<v Speaker 1>I was actually just playing the Shadows of mortor game,

0:08:41.800 --> 0:08:44.200
<v Speaker 1>and the Orcs use beacons in that came a boy,

0:08:44.200 --> 0:08:48.160
<v Speaker 1>are they irritating anyway? Uh? Greeks and Romans were using

0:08:48.240 --> 0:08:51.640
<v Speaker 1>mirrored plates to send messages using light. They would flash

0:08:51.720 --> 0:08:55.080
<v Speaker 1>light in in a series of flashes to indicate one

0:08:55.120 --> 0:08:58.920
<v Speaker 1>thing or another. Uh. There's the famous story in American

0:08:59.040 --> 0:09:02.439
<v Speaker 1>history during the Revolutionary War in which the Old North

0:09:02.559 --> 0:09:06.040
<v Speaker 1>Church in Boston was used to alert messengers to the

0:09:06.240 --> 0:09:09.640
<v Speaker 1>troop movements of British troops. The whole one if by

0:09:09.720 --> 0:09:13.679
<v Speaker 1>land too, if by sea, referred to in Longfellow's poem

0:09:13.720 --> 0:09:17.479
<v Speaker 1>Paul Revere's Ride, which may or may not be apocryphal.

0:09:17.520 --> 0:09:23.000
<v Speaker 1>There's some arguments historically speaking about what exactly happened. Essentially,

0:09:23.040 --> 0:09:25.599
<v Speaker 1>people say that yes, lights were used. Whether or not

0:09:25.760 --> 0:09:27.600
<v Speaker 1>was the Old North Church is still the matter of

0:09:27.640 --> 0:09:30.560
<v Speaker 1>some debate. But at any rate, we've been using lights

0:09:30.559 --> 0:09:33.120
<v Speaker 1>like this for ages. Yeah, and that that is definitely

0:09:33.400 --> 0:09:37.320
<v Speaker 1>encoding data in light. But right, it's pretty limited that

0:09:37.400 --> 0:09:40.839
<v Speaker 1>The fancy word which Jonathan just mentioned earlier actually is semaphore,

0:09:41.400 --> 0:09:43.840
<v Speaker 1>which just means an object that can be placed in

0:09:43.880 --> 0:09:48.240
<v Speaker 1>different positions or conditions to convey different messages, like like

0:09:48.320 --> 0:09:50.600
<v Speaker 1>flag signals. Yeah, if you think about it, you could

0:09:50.640 --> 0:09:53.960
<v Speaker 1>even have set up a semaphour type of signaling system

0:09:54.280 --> 0:09:57.720
<v Speaker 1>with office mates where you just have a quietly like

0:09:57.760 --> 0:10:00.800
<v Speaker 1>a little cabal who all know that the placement of

0:10:00.880 --> 0:10:05.760
<v Speaker 1>certain office equipment or or or a coutrement in certain locations,

0:10:05.760 --> 0:10:09.000
<v Speaker 1>on certain desks conveys a meaning. And from your blank stairs,

0:10:09.040 --> 0:10:10.719
<v Speaker 1>I can tell neither of you are in it. Never mind,

0:10:10.720 --> 0:10:14.360
<v Speaker 1>I didn't say anything. So. By the early eighteen hundreds,

0:10:14.360 --> 0:10:18.080
<v Speaker 1>the United States was experimenting with a technology called helio graphs.

0:10:18.840 --> 0:10:23.040
<v Speaker 1>These were solar telegraphs. They actually used sunlight and mirrors

0:10:23.080 --> 0:10:27.000
<v Speaker 1>to try and send messages from signal towers. That sounds

0:10:27.040 --> 0:10:29.920
<v Speaker 1>like some steam punk stuff, It does, doesn't It also

0:10:30.000 --> 0:10:33.200
<v Speaker 1>reminds me of a Terry Pratchett novel in which there

0:10:33.280 --> 0:10:37.079
<v Speaker 1>was a whole system set up that was competing with

0:10:37.280 --> 0:10:40.880
<v Speaker 1>mail on discworld. But at any rate, they would use

0:10:40.920 --> 0:10:43.520
<v Speaker 1>morse code and flash out messages to one another and

0:10:43.520 --> 0:10:47.640
<v Speaker 1>send messages down the line of signal towers to get

0:10:47.640 --> 0:10:50.160
<v Speaker 1>the message to where it needs to go. Then there

0:10:50.240 --> 0:10:52.359
<v Speaker 1>was a guy, you may have heard of him, Alexander

0:10:52.400 --> 0:10:56.360
<v Speaker 1>Graham Bell. Yeah, uh so, he and see the guy

0:10:56.360 --> 0:11:01.040
<v Speaker 1>who invented Graham crackers. Uh, it was close friend to

0:11:01.040 --> 0:11:05.000
<v Speaker 1>the Kellogg's. No, he invented a device called the photo

0:11:05.200 --> 0:11:09.400
<v Speaker 1>phone in and it used a vibrating mirror to encode

0:11:09.640 --> 0:11:13.719
<v Speaker 1>voice transmissions on a beam of light. And then you

0:11:13.720 --> 0:11:16.319
<v Speaker 1>would have a selenium photo cell that could pick up

0:11:16.360 --> 0:11:19.440
<v Speaker 1>that light and convert it back into sound. And it

0:11:19.559 --> 0:11:22.120
<v Speaker 1>only worked in sun light. You had to have some

0:11:22.320 --> 0:11:24.800
<v Speaker 1>light blasting down on this thing in order for you

0:11:24.840 --> 0:11:27.360
<v Speaker 1>to get enough light to send the message. But it

0:11:27.440 --> 0:11:31.160
<v Speaker 1>was really neat, and he invented this just four years

0:11:31.160 --> 0:11:34.400
<v Speaker 1>after he patented the telephone. He had so much hope

0:11:34.400 --> 0:11:37.360
<v Speaker 1>for this thing. Supposedly he wanted to name one of

0:11:37.440 --> 0:11:40.040
<v Speaker 1>his daughters after it. He was so fond of it.

0:11:40.559 --> 0:11:45.000
<v Speaker 1>Uh that wanted to name her Photo Photophone. Yeah, didn't

0:11:45.080 --> 0:11:48.160
<v Speaker 1>didn't work out good thing for her. Um, maybe he

0:11:48.280 --> 0:11:54.160
<v Speaker 1>could have named her photo Phoenicia. Pretty Yeah, I'm not sure,

0:11:54.280 --> 0:11:57.240
<v Speaker 1>but but but it was really really cool. Uh it was.

0:11:57.320 --> 0:11:59.720
<v Speaker 1>It was the series of mirrors and lenses that would

0:11:59.760 --> 0:12:02.320
<v Speaker 1>dire act a beam of sunlight. And yeah, they tried

0:12:02.360 --> 0:12:04.840
<v Speaker 1>it with kerosene lamp light, but it didn't work well enough.

0:12:05.360 --> 0:12:07.880
<v Speaker 1>Uh so so it would direct a beam of sunlight

0:12:07.920 --> 0:12:11.280
<v Speaker 1>to a mirror attached to the mouthpiece that you spoke into,

0:12:11.640 --> 0:12:14.600
<v Speaker 1>which would the mirror would then bounce the light off

0:12:14.880 --> 0:12:18.120
<v Speaker 1>through more lenses and onto a receiver. So when you spoke,

0:12:18.160 --> 0:12:21.079
<v Speaker 1>the mirror would vibrate, thus changing the intensity of the

0:12:21.160 --> 0:12:25.120
<v Speaker 1>light that was hitting the receiver. And yeah, it worked.

0:12:25.120 --> 0:12:29.400
<v Speaker 1>It worked real well, very clear uh sound effects coming through.

0:12:29.720 --> 0:12:32.679
<v Speaker 1>But it also would pick up noises like a like

0:12:32.840 --> 0:12:36.000
<v Speaker 1>like clouds passing across the sun right because you have

0:12:36.080 --> 0:12:39.600
<v Speaker 1>an interruption in the signal. So so if you've ever

0:12:39.679 --> 0:12:44.199
<v Speaker 1>been wondering what that sounds like, it's probably something akin

0:12:44.320 --> 0:12:48.360
<v Speaker 1>to weird static, I would imagine. But now I really

0:12:48.360 --> 0:12:51.760
<v Speaker 1>want to know. This is getting cooler and cooler. Well,

0:12:51.800 --> 0:12:54.160
<v Speaker 1>it keeps getting cooler. By the nineteen fifties, we have

0:12:54.200 --> 0:12:57.360
<v Speaker 1>researchers who are looking into using light through cabling systems

0:12:57.360 --> 0:13:00.959
<v Speaker 1>to create new communication technologies. So to get around this

0:13:01.080 --> 0:13:04.679
<v Speaker 1>problem of only being able to use sunlight or some

0:13:04.760 --> 0:13:09.480
<v Speaker 1>other visible light within uh the area to communicate, they

0:13:09.480 --> 0:13:12.320
<v Speaker 1>wanted to be able to pass light through cabling, essentially

0:13:12.320 --> 0:13:16.200
<v Speaker 1>creating very reflective cables that could pass a light signal

0:13:16.240 --> 0:13:19.160
<v Speaker 1>down them. We're talking about the birth of fiber optics here,

0:13:19.559 --> 0:13:22.400
<v Speaker 1>and in April nineteen seven we had the first optic

0:13:22.440 --> 0:13:25.240
<v Speaker 1>telephone cable put into service. It was owned by General

0:13:25.280 --> 0:13:29.960
<v Speaker 1>Telephone and Electronics. Soon afterwards, other telephone companies were installing

0:13:30.000 --> 0:13:33.200
<v Speaker 1>fiber optic cables and those are really the backbone of

0:13:33.240 --> 0:13:36.679
<v Speaker 1>our telecommunications infrastructure at this point. Like we think of

0:13:36.679 --> 0:13:39.839
<v Speaker 1>copper as a as a signal carrier quite often, but

0:13:39.880 --> 0:13:43.800
<v Speaker 1>really fiber optics are that's that's the true backbone for

0:13:43.920 --> 0:13:48.320
<v Speaker 1>most of the telecommunications around the world. Now, all that's cool,

0:13:48.360 --> 0:13:50.040
<v Speaker 1>but what if we were able to go back to

0:13:50.200 --> 0:13:53.720
<v Speaker 1>Bell's idea of using visible light to communicate? So, in

0:13:53.760 --> 0:13:55.480
<v Speaker 1>other words, what if we were to use light to

0:13:55.480 --> 0:13:59.120
<v Speaker 1>transmit data through the air and not through cables, So

0:13:59.400 --> 0:14:02.240
<v Speaker 1>not a system that you hook up to your computer

0:14:02.679 --> 0:14:07.120
<v Speaker 1>with a physical cord, but rather light, ambient light in

0:14:07.280 --> 0:14:10.920
<v Speaker 1>your environment being able to communicate data. And then that

0:14:10.920 --> 0:14:13.040
<v Speaker 1>would mean we could open up the entire spectrum of

0:14:13.120 --> 0:14:18.160
<v Speaker 1>visible light for communication. Is that possible? I mean, that

0:14:18.200 --> 0:14:21.680
<v Speaker 1>sounds very interesting. One of the things that I often

0:14:21.800 --> 0:14:26.320
<v Speaker 1>think about is all of the data that's passing through

0:14:26.360 --> 0:14:29.560
<v Speaker 1>and around us all the time. Yeah, everywhere you go,

0:14:30.200 --> 0:14:33.400
<v Speaker 1>there are signals bounding around. I mean they're you're walking

0:14:33.480 --> 0:14:36.120
<v Speaker 1>through the range of WiFi routers, but there are also

0:14:36.200 --> 0:14:40.600
<v Speaker 1>cell towers, radio broadcast towers. Yes, stuff is going through

0:14:40.600 --> 0:14:43.720
<v Speaker 1>you all the time, and it's very bizarre to think,

0:14:43.720 --> 0:14:46.480
<v Speaker 1>what if you could see all of that? Right, And

0:14:46.480 --> 0:14:48.280
<v Speaker 1>then of course there are people who believe that they

0:14:48.320 --> 0:14:51.400
<v Speaker 1>are their health is affected by these things, not that

0:14:51.440 --> 0:14:54.560
<v Speaker 1>we've seen any real medical evidence to support such things,

0:14:54.600 --> 0:14:57.760
<v Speaker 1>but there are people who truly believe, Yeah, who won't

0:14:57.800 --> 0:15:00.840
<v Speaker 1>be around WiFi routers at all, Yeah, because they say

0:15:00.880 --> 0:15:03.680
<v Speaker 1>that it it impacts their health in a negative way. Yeah,

0:15:03.840 --> 0:15:07.200
<v Speaker 1>it really doesn't. These things very much are in the

0:15:07.280 --> 0:15:10.040
<v Speaker 1>kind of between the microwave and the radio frequency on

0:15:10.360 --> 0:15:15.560
<v Speaker 1>the spectrum the electromagnetic spectrum, and they're they're very safe there.

0:15:15.680 --> 0:15:19.680
<v Speaker 1>There's a very very low probability, uh, that that they

0:15:19.680 --> 0:15:22.000
<v Speaker 1>are in any way affecting anyone's health, especially from a

0:15:22.000 --> 0:15:24.680
<v Speaker 1>distance of more than like two centimeters. Yeah, I mean,

0:15:24.760 --> 0:15:27.800
<v Speaker 1>it's non ionizing radiation. It's just not that part of

0:15:27.840 --> 0:15:30.720
<v Speaker 1>the spectrum that's going to knock molecules loose and up

0:15:30.760 --> 0:15:35.040
<v Speaker 1>set your DNA. What it could possibly do is maybe

0:15:35.160 --> 0:15:38.880
<v Speaker 1>heat up your skin possibly. Yeah, there there can be

0:15:38.920 --> 0:15:42.800
<v Speaker 1>electromagnetic interference that can cause other issues, and we'll talk

0:15:42.800 --> 0:15:44.360
<v Speaker 1>about that. And I think I think the World Health

0:15:44.440 --> 0:15:50.600
<v Speaker 1>Organization has listed it as a potential carcinogen now that

0:15:51.280 --> 0:15:53.600
<v Speaker 1>so you can say that. But another thing to note

0:15:53.640 --> 0:15:59.760
<v Speaker 1>would be that the sun is a known carcinogen, absolutely accurate.

0:16:00.120 --> 0:16:03.240
<v Speaker 1>If you're okay going out in the sun, you should

0:16:03.280 --> 0:16:06.880
<v Speaker 1>probably be okay getting around a WiFi router every now

0:16:06.880 --> 0:16:08.640
<v Speaker 1>and then. You might not want to sleep with your

0:16:08.640 --> 0:16:11.760
<v Speaker 1>head resting on one every day. But yeah, well, the

0:16:11.760 --> 0:16:13.840
<v Speaker 1>only reason I even brought it up, and I was

0:16:13.880 --> 0:16:18.400
<v Speaker 1>hesitant to bring it up because pills so comfy. Because

0:16:18.400 --> 0:16:22.200
<v Speaker 1>I am very skeptical of the thought that WiFi and

0:16:22.320 --> 0:16:27.480
<v Speaker 1>other radio frequency communication can have a a physical effect

0:16:27.560 --> 0:16:32.120
<v Speaker 1>on people, uh, particularly at the intensities of our you know,

0:16:32.520 --> 0:16:35.720
<v Speaker 1>our WiFi routers things of that nature. I'm very skeptical

0:16:35.760 --> 0:16:37.560
<v Speaker 1>of that. However, the reason, one of the reasons I

0:16:37.560 --> 0:16:41.320
<v Speaker 1>brought it up is because it was one of the

0:16:41.360 --> 0:16:46.520
<v Speaker 1>benefits that was being touted by LiFi using light instead

0:16:46.520 --> 0:16:50.320
<v Speaker 1>of radio signals to transmit this data at this last

0:16:50.400 --> 0:16:54.160
<v Speaker 1>segment between the backbone of the Internet and whatever device

0:16:54.240 --> 0:16:58.600
<v Speaker 1>you want to use. That well, One of the many

0:16:58.640 --> 0:17:03.120
<v Speaker 1>benefits is that you and complain about the wireless signals

0:17:03.200 --> 0:17:05.520
<v Speaker 1>hurting you because it's using visible light. If if if

0:17:05.560 --> 0:17:07.480
<v Speaker 1>that hurts you, then just being in a room with

0:17:07.520 --> 0:17:10.800
<v Speaker 1>a lamp would hurt you. But at any rate, let's

0:17:10.800 --> 0:17:13.520
<v Speaker 1>talk about what. So one of the benefits is that

0:17:13.640 --> 0:17:18.720
<v Speaker 1>it counteracts something that is probably not a problem. Yes, yes,

0:17:19.320 --> 0:17:22.080
<v Speaker 1>and that was actually my very reaction that you just had.

0:17:22.080 --> 0:17:25.800
<v Speaker 1>But really, let's talk about Life I. So super cool idea.

0:17:26.440 --> 0:17:29.320
<v Speaker 1>You know, it's an offshoot of a broader category called

0:17:29.359 --> 0:17:32.879
<v Speaker 1>optical wireless Communications or o w C, which does not

0:17:33.000 --> 0:17:36.400
<v Speaker 1>necessarily have to deal with a visible light. It could

0:17:36.400 --> 0:17:38.400
<v Speaker 1>be anything in the light spectrum, so they could also

0:17:38.440 --> 0:17:42.200
<v Speaker 1>involve infrared or ultra violet, something along those lines. Uh.

0:17:42.280 --> 0:17:45.320
<v Speaker 1>So there is another branch, a smaller one, called visible

0:17:45.400 --> 0:17:47.880
<v Speaker 1>light Communications or v l C, and Life I would

0:17:47.880 --> 0:17:51.360
<v Speaker 1>be part of that. The term was coined by Harold

0:17:51.440 --> 0:17:54.920
<v Speaker 1>has who is a professor and also has worked with

0:17:55.560 --> 0:17:59.720
<v Speaker 1>um a company called Pure Life I to develop a system. Yeah,

0:17:59.760 --> 0:18:03.000
<v Speaker 1>he's their chief science officer. Yeah. Uh, and so this

0:18:03.080 --> 0:18:05.760
<v Speaker 1>is all about using light within the visible spectrum, and

0:18:05.800 --> 0:18:08.880
<v Speaker 1>the reason being that he's concentrated on that is that

0:18:09.040 --> 0:18:11.760
<v Speaker 1>other types of light, like infrared, can be harmful to

0:18:11.760 --> 0:18:14.879
<v Speaker 1>your eyes, and ultra violet, as we know, can cause

0:18:15.000 --> 0:18:17.400
<v Speaker 1>things like skin cancer if you have too much exposure

0:18:17.440 --> 0:18:20.639
<v Speaker 1>to ultra violet. Uh. So he presented a TED talk

0:18:20.720 --> 0:18:23.639
<v Speaker 1>on this subject, and in that talk he called it

0:18:23.840 --> 0:18:28.399
<v Speaker 1>d light, which I thought was delightful. I put it

0:18:28.440 --> 0:18:30.159
<v Speaker 1>in the notes and I had to say it too,

0:18:30.720 --> 0:18:34.199
<v Speaker 1>uh and he wanted He used a system that was

0:18:34.240 --> 0:18:38.600
<v Speaker 1>called orthogonal frequency division multiplexing or o f d M,

0:18:39.200 --> 0:18:42.359
<v Speaker 1>which sounds pretty fancy, but honestly, it gets really simple.

0:18:43.040 --> 0:18:46.080
<v Speaker 1>It's all about amplifying the signal from an l e

0:18:46.200 --> 0:18:49.879
<v Speaker 1>ED light source, and you do that by varying the

0:18:49.920 --> 0:18:53.040
<v Speaker 1>electric current that's flowing through the l e ED And

0:18:53.119 --> 0:18:55.280
<v Speaker 1>that's all you need to do is just vary that current.

0:18:55.560 --> 0:18:58.080
<v Speaker 1>By varying the current, you've you change the amplification of

0:18:58.080 --> 0:19:00.320
<v Speaker 1>that light. If you have a receiver that can pick

0:19:00.400 --> 0:19:05.680
<v Speaker 1>up these minute, subtle variations, then they can then decode

0:19:05.720 --> 0:19:08.480
<v Speaker 1>that as the information that you had intended to send.

0:19:08.480 --> 0:19:10.240
<v Speaker 1>So you could do this like you could send a

0:19:10.240 --> 0:19:13.320
<v Speaker 1>movie this way. You could have a lightbulb that has

0:19:13.359 --> 0:19:17.800
<v Speaker 1>a little microprocessor attached to it and it is pulling

0:19:17.800 --> 0:19:21.640
<v Speaker 1>the signal from whatever feed is coming into your home

0:19:21.960 --> 0:19:24.080
<v Speaker 1>from the Internet. So let's say that you've got the

0:19:24.160 --> 0:19:27.399
<v Speaker 1>internet backbone, you've got fiber optic. Let's say that runs

0:19:27.440 --> 0:19:31.000
<v Speaker 1>to your house. From there, you would have a system

0:19:31.080 --> 0:19:34.920
<v Speaker 1>that would take that signal converted into the language that

0:19:34.960 --> 0:19:37.439
<v Speaker 1>would be picked up by this microprocessor in a light bulb.

0:19:37.840 --> 0:19:41.919
<v Speaker 1>The light bulb would then flash at the frequency the

0:19:42.000 --> 0:19:45.760
<v Speaker 1>amplitude changes according to whatever data was being sent, but

0:19:45.840 --> 0:19:50.080
<v Speaker 1>do so so rapidly that your human eyes would be

0:19:50.119 --> 0:19:52.720
<v Speaker 1>incapable of detecting it. So we just looked like the

0:19:52.800 --> 0:19:55.959
<v Speaker 1>light bulbs on. It wouldn't look like the lightbulbs. It

0:19:56.000 --> 0:19:58.240
<v Speaker 1>wasn't Yeah, it wouldn't be a disco. It wouldn't be

0:19:58.240 --> 0:20:02.200
<v Speaker 1>like a ghostly light bulb. Now, it would be very subtle,

0:20:02.240 --> 0:20:04.879
<v Speaker 1>to the point where, because of it it's such a

0:20:04.960 --> 0:20:07.320
<v Speaker 1>high frequency, it would just seem like a steady light

0:20:07.359 --> 0:20:12.119
<v Speaker 1>source to us. And meanwhile, any devices outfitted with a

0:20:12.160 --> 0:20:15.680
<v Speaker 1>sensor that could pick up these subtle variations in light

0:20:15.720 --> 0:20:20.520
<v Speaker 1>amplitude would be able to accept that information. So with

0:20:20.640 --> 0:20:23.840
<v Speaker 1>the movie example, you could have a home theater where

0:20:23.880 --> 0:20:27.640
<v Speaker 1>you've got very dim lights on and you've got a

0:20:27.680 --> 0:20:32.440
<v Speaker 1>receiver of some sort that can take it has that

0:20:32.440 --> 0:20:34.800
<v Speaker 1>that sensor on it that can detect the changes in light.

0:20:35.040 --> 0:20:38.920
<v Speaker 1>It's connected to your entertainment system, and you are beaming

0:20:39.359 --> 0:20:43.920
<v Speaker 1>the film you're watching through light. There's no physical connection

0:20:44.000 --> 0:20:47.560
<v Speaker 1>to the entertainment system. There's no radio connection. There no

0:20:47.720 --> 0:20:51.000
<v Speaker 1>radio waves going on at all. It's just light beaming

0:20:51.000 --> 0:20:54.840
<v Speaker 1>that information down, which is pretty awesome, and it can

0:20:54.880 --> 0:20:59.480
<v Speaker 1>do it pretty effectively. At the TED talk he demonstrated this.

0:20:59.520 --> 0:21:02.560
<v Speaker 1>He had an a desk lamp set up that had

0:21:02.600 --> 0:21:05.439
<v Speaker 1>a light bulb with one of these microprocessors attached to it,

0:21:06.359 --> 0:21:09.879
<v Speaker 1>and the lamp was hooked up through a system that

0:21:10.040 --> 0:21:13.479
<v Speaker 1>fed it the data it needed and was set on

0:21:13.520 --> 0:21:15.960
<v Speaker 1>the table. And the table had a little hole drilled

0:21:16.080 --> 0:21:19.800
<v Speaker 1>into it and through that hole light would go through

0:21:19.800 --> 0:21:21.920
<v Speaker 1>that little hole, and on the underside of the table

0:21:22.080 --> 0:21:25.000
<v Speaker 1>was a sensor that was then connected to a projector.

0:21:25.640 --> 0:21:28.440
<v Speaker 1>So he turned on the lamp and the lamp sent

0:21:28.520 --> 0:21:31.680
<v Speaker 1>information to the sensor that started a video, a high

0:21:31.720 --> 0:21:35.560
<v Speaker 1>definition video playing behind him as he gave his talk,

0:21:35.960 --> 0:21:39.320
<v Speaker 1>And then he demonstrated by interrupting the light source. In

0:21:39.320 --> 0:21:42.480
<v Speaker 1>other words, he stuck his hand over the whole and

0:21:42.560 --> 0:21:46.480
<v Speaker 1>it interrupted the data stream, so the video paused. It

0:21:46.560 --> 0:21:50.040
<v Speaker 1>was as if your wireless had dropped. And if you've

0:21:50.040 --> 0:21:52.399
<v Speaker 1>ever had that experience where suddenly, uh, you know, it

0:21:52.400 --> 0:21:54.639
<v Speaker 1>starts to buffer or it's going through like trying to

0:21:54.680 --> 0:21:56.840
<v Speaker 1>search for a signal, same sort of thing. He moved

0:21:56.880 --> 0:22:00.199
<v Speaker 1>his hand and it started up again. So it was

0:22:00.480 --> 0:22:02.800
<v Speaker 1>an example of yes, this is live. This is a

0:22:02.840 --> 0:22:07.600
<v Speaker 1>live feed of information from a lightbulb to a computer

0:22:07.680 --> 0:22:10.720
<v Speaker 1>system and showing you how that information can be transferred

0:22:10.800 --> 0:22:15.080
<v Speaker 1>just using light. Pretty awesome. Now, the reason you used

0:22:15.200 --> 0:22:18.800
<v Speaker 1>L E. D S was specifically because L E Ed's

0:22:19.000 --> 0:22:23.000
<v Speaker 1>work on their semiconductors and you can easily control them

0:22:23.000 --> 0:22:26.640
<v Speaker 1>by varying that electric frequent are the electric current that

0:22:26.840 --> 0:22:30.760
<v Speaker 1>goes to the semiconductors, so you can make minute changes

0:22:31.320 --> 0:22:35.040
<v Speaker 1>very very quickly. And this is different from other types

0:22:35.040 --> 0:22:36.919
<v Speaker 1>of light bulbs. Oh yeah, you cannot do this with

0:22:36.960 --> 0:22:40.440
<v Speaker 1>an incandescent bulb, right, because incandescent bulbs what they do

0:22:40.520 --> 0:22:43.520
<v Speaker 1>is you have they're essentially resistors. Right, You have this

0:22:43.760 --> 0:22:47.159
<v Speaker 1>filament that resists the flow of electricity. As a result,

0:22:47.240 --> 0:22:49.520
<v Speaker 1>it heats up. Eventually, it heats up to a temperature

0:22:49.520 --> 0:22:54.120
<v Speaker 1>that allows it to incandesse or to glow up. Yeah, yeah,

0:22:54.200 --> 0:22:57.200
<v Speaker 1>it needs that time, So that would be a rave that. Yes,

0:22:57.800 --> 0:22:59.720
<v Speaker 1>if you try to use it incandescent bulbs, yes, it

0:22:59.760 --> 0:23:02.639
<v Speaker 1>would not be able to transmit at near the speed

0:23:02.840 --> 0:23:04.720
<v Speaker 1>of an l AED bulb. And then, of course if

0:23:04.760 --> 0:23:07.160
<v Speaker 1>you wanted to do this with fluorescent lights, you might

0:23:07.200 --> 0:23:09.840
<v Speaker 1>as well do the guy with the flags on the table. Yeah,

0:23:09.960 --> 0:23:12.960
<v Speaker 1>same thing, because fluorescent lights, they use a gas that

0:23:12.960 --> 0:23:17.320
<v Speaker 1>gets excited by electricity that then amixites another gas that

0:23:17.400 --> 0:23:20.480
<v Speaker 1>then emits photons. Yeah, and those photons are usually in

0:23:20.560 --> 0:23:22.359
<v Speaker 1>the ultra violet range, so you have to actually have,

0:23:22.560 --> 0:23:26.720
<v Speaker 1>you know, put a a um, a substance on the

0:23:26.760 --> 0:23:30.240
<v Speaker 1>inside of the fluorescent bulbs that will fluoresce in the

0:23:30.359 --> 0:23:33.600
<v Speaker 1>visible spectrum once it's hit by ultra violet photons. It's

0:23:33.680 --> 0:23:35.760
<v Speaker 1>kind of a weird chain reaction. Yeah, it's like it's

0:23:35.760 --> 0:23:38.840
<v Speaker 1>like a it's like a bucket brigade for for people

0:23:38.840 --> 0:23:42.000
<v Speaker 1>who fight fires. So when they first started showing this

0:23:42.119 --> 0:23:44.800
<v Speaker 1>off back in the TED Talk, it was pretty much

0:23:44.840 --> 0:23:47.440
<v Speaker 1>at a speed of around ten megabits per second, which

0:23:47.440 --> 0:23:50.960
<v Speaker 1>is that's okay, I mean it's not it's no longer

0:23:51.040 --> 0:23:53.280
<v Speaker 1>what broadband is considered here in the U S No.

0:23:53.600 --> 0:23:56.440
<v Speaker 1>I just for for an example of how that compares

0:23:56.520 --> 0:23:59.679
<v Speaker 1>to say, my WiFi on my computer from about a

0:23:59.720 --> 0:24:04.160
<v Speaker 1>minute and a half ago. I'm currently registering download speeds

0:24:04.240 --> 0:24:08.240
<v Speaker 1>about forty three negabets per second and upload speeds of

0:24:08.280 --> 0:24:13.440
<v Speaker 1>about fourteen per second, so much faster. But those that

0:24:13.520 --> 0:24:17.040
<v Speaker 1>was just the starting off point, and the hass himself

0:24:17.160 --> 0:24:21.040
<v Speaker 1>is working on systems that are much more advanced than that,

0:24:21.240 --> 0:24:24.680
<v Speaker 1>including ones that would be using not LEDs but lasers,

0:24:24.720 --> 0:24:27.000
<v Speaker 1>low powered lasers. So it's not like they're going to

0:24:27.600 --> 0:24:29.359
<v Speaker 1>blind you. You know, It's not like you're going to

0:24:29.400 --> 0:24:31.200
<v Speaker 1>be have a bunch of laser pointers going crazy in

0:24:31.200 --> 0:24:33.240
<v Speaker 1>your house. It would be hard to sell something that

0:24:33.400 --> 0:24:37.560
<v Speaker 1>blinded people. Yeah, if it as long as I hold on,

0:24:37.600 --> 0:24:40.479
<v Speaker 1>what if it blinds somebody else instead of you? Right,

0:24:40.480 --> 0:24:42.560
<v Speaker 1>if it's the blind o Tron two thousand, like it's

0:24:42.560 --> 0:24:46.600
<v Speaker 1>specifically marketed to blind people at any rate, these lasers

0:24:46.640 --> 0:24:49.240
<v Speaker 1>are not of that nature and gave a sad story

0:24:49.280 --> 0:24:54.159
<v Speaker 1>fast well. But the neat thing about the laser system

0:24:54.200 --> 0:24:56.320
<v Speaker 1>is that it might be able to achieve a throughput

0:24:56.400 --> 0:24:59.639
<v Speaker 1>of around a hundred gigabits per second, which is in

0:25:00.000 --> 0:25:03.280
<v Speaker 1>mainly fast, right, And when we say fast, obviously once

0:25:03.280 --> 0:25:06.159
<v Speaker 1>again we don't necessarily mean that the data is moving

0:25:06.320 --> 0:25:09.800
<v Speaker 1>at a faster speed, more like more data can move

0:25:09.920 --> 0:25:13.080
<v Speaker 1>through that pathway. At the same time, it's it's not

0:25:13.160 --> 0:25:15.399
<v Speaker 1>how fast the cars on the highway are driving, but

0:25:15.480 --> 0:25:18.480
<v Speaker 1>how many lanes there are. Ye. So in this case,

0:25:18.520 --> 0:25:20.560
<v Speaker 1>a hundred gigabits per second means that you would be

0:25:20.600 --> 0:25:25.400
<v Speaker 1>able to have really high quality video, for example, beaming

0:25:25.440 --> 0:25:28.400
<v Speaker 1>through at this with no buffering necessary. It would be

0:25:28.680 --> 0:25:31.560
<v Speaker 1>pretty phenomenal. So so that process it's still in or

0:25:31.600 --> 0:25:34.920
<v Speaker 1>that technology rather is still in development. Yes, the led

0:25:35.119 --> 0:25:38.280
<v Speaker 1>s i've heard are closer to around UH one between

0:25:38.280 --> 0:25:41.320
<v Speaker 1>one and ten gigabits per second at their current level,

0:25:42.240 --> 0:25:45.440
<v Speaker 1>which still I mean one gigabit per second. We're talking

0:25:45.480 --> 0:25:49.560
<v Speaker 1>about Google fiber speeds around there, right, ten gigabits per second,

0:25:49.720 --> 0:25:54.120
<v Speaker 1>it's ten times what's considered ultra fast UH download speeds

0:25:54.160 --> 0:25:56.320
<v Speaker 1>according to the current state of the art here in

0:25:56.359 --> 0:25:59.560
<v Speaker 1>the United States. UM and his ted talk has actually

0:25:59.560 --> 0:26:01.439
<v Speaker 1>said that one of the reasons they looked at this

0:26:02.080 --> 0:26:05.199
<v Speaker 1>is really that radio frequency capacity crunch. That was a

0:26:05.280 --> 0:26:08.000
<v Speaker 1>real big reason to look at it. We're adding more

0:26:08.040 --> 0:26:12.080
<v Speaker 1>and more devices, and we're having more issues with local

0:26:12.119 --> 0:26:15.240
<v Speaker 1>access points getting bogged down with traffic. So what if

0:26:15.240 --> 0:26:17.239
<v Speaker 1>we were able to relieve some of that traffic by

0:26:17.280 --> 0:26:20.760
<v Speaker 1>switching to this light method. And he pointed out that

0:26:20.840 --> 0:26:23.320
<v Speaker 1>with the visible light spectrum you have about ten thousand

0:26:23.359 --> 0:26:28.080
<v Speaker 1>times more capacity than within the entire radio band spectrum.

0:26:28.720 --> 0:26:30.920
<v Speaker 1>Keeping in mind that lots of the radio band spectrum

0:26:30.920 --> 0:26:34.399
<v Speaker 1>are already they're already earmarked for other things that we

0:26:34.480 --> 0:26:38.760
<v Speaker 1>can't touch, right, right, they're regulated by governments of various

0:26:38.760 --> 0:26:40.719
<v Speaker 1>countries to say that like, oh, we we're setting this

0:26:40.760 --> 0:26:43.920
<v Speaker 1>aside for this type of official communication, and this aside

0:26:43.960 --> 0:26:47.680
<v Speaker 1>for television, in this aside for the right terrestrial radio

0:26:47.840 --> 0:26:50.800
<v Speaker 1>or radar or whatever you know. So there there are

0:26:50.800 --> 0:26:53.760
<v Speaker 1>certain sections that you just can't do anything with because

0:26:53.760 --> 0:26:57.960
<v Speaker 1>they're already dedicated for other uses. This would allow us

0:26:58.040 --> 0:27:01.600
<v Speaker 1>to use a band of quency in the electromagnetic spectrum

0:27:01.600 --> 0:27:04.840
<v Speaker 1>that is unregulated and has ten thousand times more capacity

0:27:05.080 --> 0:27:08.199
<v Speaker 1>crently unregulated. Yes, if we were to start using it,

0:27:08.280 --> 0:27:10.920
<v Speaker 1>you could be sure that sooner or later regulation would

0:27:10.960 --> 0:27:14.280
<v Speaker 1>probably have to follow just to make certain that you

0:27:14.320 --> 0:27:18.679
<v Speaker 1>didn't have a bunch of competing communications. Uh, systems in

0:27:18.840 --> 0:27:23.200
<v Speaker 1>a similar place that we're just going to cause confusion. Uh. So,

0:27:23.320 --> 0:27:25.920
<v Speaker 1>for example, imagine that you're in a mall and the

0:27:26.040 --> 0:27:29.399
<v Speaker 1>lights are all outfitted with this stuff, but they have

0:27:29.480 --> 0:27:33.119
<v Speaker 1>been installed over various different times and are all working

0:27:33.160 --> 0:27:38.280
<v Speaker 1>on different um different proprietary approaches, and meanwhile your device

0:27:38.520 --> 0:27:42.520
<v Speaker 1>is going crazy because it's receiving all these different signals simultaneously.

0:27:42.520 --> 0:27:44.600
<v Speaker 1>It's would be like everyone's yelling at the same time.

0:27:45.080 --> 0:27:48.240
<v Speaker 1>Another neat thing is that this would eliminate the possibility

0:27:48.240 --> 0:27:50.320
<v Speaker 1>of someone snooping in on your WiFi as long as

0:27:50.320 --> 0:27:52.760
<v Speaker 1>they're not in the same room. You are inca right

0:27:52.840 --> 0:27:56.239
<v Speaker 1>because light doesn't go through walls, right, as long as

0:27:56.240 --> 0:27:59.000
<v Speaker 1>you're not, like you know, in a big glass cube,

0:27:59.720 --> 0:28:01.720
<v Speaker 1>or people could just walk up and hold of a

0:28:01.760 --> 0:28:05.280
<v Speaker 1>device outside of your your giant glass cube. Uh, then

0:28:05.359 --> 0:28:07.480
<v Speaker 1>you'd be fine. You you wouldn't have you know. It

0:28:07.520 --> 0:28:11.240
<v Speaker 1>would allow for some secure communications protocols that could be

0:28:11.280 --> 0:28:14.160
<v Speaker 1>really useful in lots of different places. I mean imagine

0:28:14.200 --> 0:28:19.719
<v Speaker 1>just from business standpoint, imagine having a business, um like

0:28:19.760 --> 0:28:23.119
<v Speaker 1>an office outfitted with this stuff, so that way proprietary

0:28:23.200 --> 0:28:27.720
<v Speaker 1>secrets would remain more secure. If someone got access to

0:28:27.800 --> 0:28:29.679
<v Speaker 1>that then you would know they have access to your people,

0:28:29.840 --> 0:28:33.040
<v Speaker 1>not to your technology or the access to your space.

0:28:33.240 --> 0:28:35.560
<v Speaker 1>Yeah yeah, or that you've been posting things on Google docs,

0:28:36.080 --> 0:28:38.680
<v Speaker 1>right yeah, if they they found it through some other

0:28:38.880 --> 0:28:42.040
<v Speaker 1>like some other loophole but not within your your actual

0:28:42.120 --> 0:28:46.600
<v Speaker 1>like wireless system. Um and you could, uh, you could

0:28:46.640 --> 0:28:50.240
<v Speaker 1>even use this to transmit information if you have other

0:28:50.400 --> 0:28:53.240
<v Speaker 1>lights active in the area. When he was demonstrating it

0:28:53.280 --> 0:28:56.880
<v Speaker 1>as ted talk, Hause showed that this lamp was on

0:28:56.880 --> 0:28:59.239
<v Speaker 1>a lit stage. It wasn't as if they turn all

0:28:59.280 --> 0:29:02.120
<v Speaker 1>the lights off in lamp. Still the lamp worked. They

0:29:02.160 --> 0:29:06.520
<v Speaker 1>had ambient light from other lighting sources. But because the

0:29:06.520 --> 0:29:10.800
<v Speaker 1>sensor is really just looking for those those subtle modulations,

0:29:11.360 --> 0:29:13.840
<v Speaker 1>it doesn't matter whether the light sources you have, assuming

0:29:13.880 --> 0:29:16.320
<v Speaker 1>they're not also modulating at a super high frequency. That

0:29:16.360 --> 0:29:19.520
<v Speaker 1>could throw in some interference, especially at the same frequency

0:29:19.520 --> 0:29:23.040
<v Speaker 1>of light that your sources at, because theoretically you could

0:29:23.360 --> 0:29:26.800
<v Speaker 1>set the receiver to only look at a certain frequency

0:29:26.840 --> 0:29:30.120
<v Speaker 1>of light and ignore everything else, in which case that

0:29:30.120 --> 0:29:32.320
<v Speaker 1>would really, you know, free you up quite a bit.

0:29:32.360 --> 0:29:35.960
<v Speaker 1>In fact, it would allow you to have multiple devices

0:29:36.000 --> 0:29:39.040
<v Speaker 1>all getting information from a single source as long as

0:29:39.040 --> 0:29:41.320
<v Speaker 1>that single source had multiple l ed s that could

0:29:41.320 --> 0:29:45.720
<v Speaker 1>all use slightly different frequencies, which is a pretty interesting

0:29:45.800 --> 0:29:49.280
<v Speaker 1>in my opinion. H and he said that you could

0:29:49.320 --> 0:29:52.120
<v Speaker 1>even turn down the lights low enough so that it

0:29:52.120 --> 0:29:54.680
<v Speaker 1>wouldn't be perceptible to humans, like it would be at

0:29:54.680 --> 0:29:56.360
<v Speaker 1>a low enough level where it would seem as if

0:29:56.360 --> 0:29:59.320
<v Speaker 1>the lights are off, but would still admit enough light

0:29:59.560 --> 0:30:03.080
<v Speaker 1>for a sensitive receiver to pick up those modulations. So,

0:30:03.120 --> 0:30:04.880
<v Speaker 1>in other words, you don't always have to have the

0:30:04.960 --> 0:30:07.120
<v Speaker 1>lights on full blast in order for you to get

0:30:07.160 --> 0:30:10.080
<v Speaker 1>the data from your light bulb to your computer or whatever.

0:30:10.280 --> 0:30:14.160
<v Speaker 1>I'm just imagining this as the premise to a movie

0:30:14.400 --> 0:30:19.040
<v Speaker 1>about the electronics source that drives people crazy and so

0:30:19.160 --> 0:30:22.680
<v Speaker 1>like the signal, but instead of radio frequencies, it's light YEA,

0:30:23.240 --> 0:30:26.600
<v Speaker 1>or or the premise behind Chuck where he sees a

0:30:26.640 --> 0:30:29.640
<v Speaker 1>series of images and that somehow imprints all of the N, S,

0:30:29.680 --> 0:30:32.440
<v Speaker 1>A and C I A secrets into his brain. Not

0:30:32.640 --> 0:30:35.960
<v Speaker 1>Chuck Bryant, No, no, no, the television series Chuck, which

0:30:36.000 --> 0:30:39.280
<v Speaker 1>I just started rewatching, which is the only reason why

0:30:39.280 --> 0:30:42.080
<v Speaker 1>it was fresh in my mind. Um, But that that

0:30:42.200 --> 0:30:44.200
<v Speaker 1>I thought was pretty interesting was that, you know, again,

0:30:44.360 --> 0:30:46.840
<v Speaker 1>you can play around with the levels of human perception

0:30:46.960 --> 0:30:50.080
<v Speaker 1>so that you can still transmit this information without having

0:30:50.080 --> 0:30:52.960
<v Speaker 1>to have all your lights on UH like full blast

0:30:53.480 --> 0:30:55.800
<v Speaker 1>UM and then like I said, pure Life. I that's

0:30:55.840 --> 0:30:57.720
<v Speaker 1>the one of the companies working on this, and one

0:30:57.720 --> 0:31:00.560
<v Speaker 1>that has works with UH is working on systems that

0:31:00.600 --> 0:31:03.480
<v Speaker 1>could be deployed in the real world, and they're also

0:31:03.640 --> 0:31:05.880
<v Speaker 1>looking at how do you make this practical, how do

0:31:05.880 --> 0:31:08.560
<v Speaker 1>you make it in a way where if you were

0:31:08.600 --> 0:31:12.840
<v Speaker 1>on the move between one area serviced by LiFi into another,

0:31:13.280 --> 0:31:17.640
<v Speaker 1>you can have a seamless um experience because you know,

0:31:17.720 --> 0:31:19.680
<v Speaker 1>like the way we use cell phones, if you're using

0:31:19.680 --> 0:31:22.080
<v Speaker 1>a cell phone, if you're on the phone and you're

0:31:22.160 --> 0:31:26.240
<v Speaker 1>traveling and you move from one cell tower service area

0:31:26.320 --> 0:31:30.120
<v Speaker 1>into another's, there's a handshake that goes on that has

0:31:30.200 --> 0:31:33.000
<v Speaker 1>a handoff from one cell tower to the other, which

0:31:33.000 --> 0:31:35.479
<v Speaker 1>allows you to continue your continue your phone call. If

0:31:35.520 --> 0:31:38.840
<v Speaker 1>we didn't have this technology, once you left that first

0:31:39.080 --> 0:31:41.720
<v Speaker 1>broadcast area, you're you would drop a call, you would

0:31:41.760 --> 0:31:43.920
<v Speaker 1>not be able to continue that conversation. And I'm sure

0:31:43.920 --> 0:31:46.480
<v Speaker 1>that everyone has had the experience of driving through an

0:31:46.520 --> 0:31:51.440
<v Speaker 1>area that's kind of slightly between two different cell towers

0:31:51.920 --> 0:31:54.480
<v Speaker 1>and and therefore you miss a little bit of a

0:31:54.600 --> 0:31:56.760
<v Speaker 1>I mean, maybe your call drops off in the middle.

0:31:57.600 --> 0:32:00.640
<v Speaker 1>But yeah. So they're working on creating technology that will

0:32:00.680 --> 0:32:03.000
<v Speaker 1>that will let that be justice seamless with their with

0:32:03.040 --> 0:32:06.080
<v Speaker 1>their life Eye products, and they demonstrated one of these

0:32:06.080 --> 0:32:09.440
<v Speaker 1>products called live Flame at the Mobile World Congress in March,

0:32:10.960 --> 0:32:15.840
<v Speaker 1>which was in China somewhere I forget where, but uh,

0:32:15.880 --> 0:32:19.040
<v Speaker 1>it's on the market supposedly has been shipped to a

0:32:19.080 --> 0:32:23.520
<v Speaker 1>few commercial buyers already and I and I think the

0:32:23.600 --> 0:32:27.320
<v Speaker 1>numbers that I've read for that particular version of live

0:32:27.400 --> 0:32:29.800
<v Speaker 1>Flame are are that it has a ten megabit per

0:32:29.840 --> 0:32:33.840
<v Speaker 1>second uplink and down link. That's still pretty impressive, especially,

0:32:33.880 --> 0:32:35.800
<v Speaker 1>I mean, imagine that you could have this on two

0:32:35.840 --> 0:32:40.360
<v Speaker 1>devices and allow those two devices to communicate securely without

0:32:40.480 --> 0:32:43.040
<v Speaker 1>using radio frequencies. So, in other words, let's say that

0:32:43.040 --> 0:32:45.080
<v Speaker 1>we're sitting at this table and I wanted to send

0:32:45.360 --> 0:32:48.000
<v Speaker 1>a large file to Joe but didn't want to go

0:32:48.080 --> 0:32:52.320
<v Speaker 1>over the WiFi. If both of our computers had cameras

0:32:52.560 --> 0:32:55.920
<v Speaker 1>and lights attached to them so that I could beam

0:32:56.040 --> 0:32:58.720
<v Speaker 1>that directly to Joe, you know, it would just looked

0:32:58.760 --> 0:33:02.160
<v Speaker 1>like the little led on my my computer was just lit.

0:33:02.600 --> 0:33:05.040
<v Speaker 1>To us, it would just seem like it was on

0:33:05.440 --> 0:33:07.520
<v Speaker 1>and that's it, but it would actually be beaming that

0:33:07.560 --> 0:33:11.200
<v Speaker 1>information with those very tiny modulations. That's another reason why

0:33:11.280 --> 0:33:15.040
<v Speaker 1>people have been touting life I as a good example,

0:33:15.040 --> 0:33:18.120
<v Speaker 1>a good replacement for WiFi in certain applications, because it

0:33:18.120 --> 0:33:22.959
<v Speaker 1>will allow for that secure communication assuming that whomever is

0:33:23.000 --> 0:33:25.080
<v Speaker 1>wanting to spy on you is not within line of sight.

0:33:25.200 --> 0:33:26.600
<v Speaker 1>If they could get line of sight to a point

0:33:26.640 --> 0:33:28.920
<v Speaker 1>where they could also have a receiver getting that light,

0:33:29.400 --> 0:33:32.760
<v Speaker 1>then obviously they could intercept that information as well. But

0:33:33.560 --> 0:33:36.320
<v Speaker 1>I mean just a second here, I would think that

0:33:36.440 --> 0:33:40.640
<v Speaker 1>you could just as easily encrypt an optical light signal

0:33:40.760 --> 0:33:43.960
<v Speaker 1>and the visible spectrum as you could encrypt a radio signal. So,

0:33:44.000 --> 0:33:47.000
<v Speaker 1>in other words, have an encryption so that the data

0:33:47.080 --> 0:33:49.880
<v Speaker 1>is meaningless unless you have the key. Yeah, I mean,

0:33:49.920 --> 0:33:52.840
<v Speaker 1>I don't see any reason why encryption would be dependent

0:33:52.880 --> 0:33:55.600
<v Speaker 1>on the spectrum. Now, you absolutely could do that. You

0:33:55.680 --> 0:33:57.840
<v Speaker 1>absolutely could do that. It's just the question of whether

0:33:57.920 --> 0:34:01.240
<v Speaker 1>or not you would have the direct access to the

0:34:01.360 --> 0:34:06.440
<v Speaker 1>encrypted data because again, like we've said before, encryption gives

0:34:06.440 --> 0:34:08.360
<v Speaker 1>you a certain level of security, but there is no

0:34:08.440 --> 0:34:12.440
<v Speaker 1>such things so far as perfect encryption. If someone is

0:34:12.440 --> 0:34:17.080
<v Speaker 1>determined enough and has an access to enough processors, even

0:34:17.080 --> 0:34:19.879
<v Speaker 1>just using brute force, they can eventually break encryption. Yeah,

0:34:19.920 --> 0:34:23.319
<v Speaker 1>I mean assuming that, assuming the person doesn't have a

0:34:23.360 --> 0:34:26.319
<v Speaker 1>quantum computer or something. Well, I mean, I'm thinking of

0:34:26.360 --> 0:34:29.800
<v Speaker 1>this in the use of things like high level government

0:34:29.800 --> 0:34:33.000
<v Speaker 1>officials who need to be able to send an information

0:34:33.080 --> 0:34:35.840
<v Speaker 1>secretly to one another, where you're you know, that's a

0:34:35.880 --> 0:34:38.320
<v Speaker 1>case where you're talking about there's enough of an incentive

0:34:38.400 --> 0:34:41.600
<v Speaker 1>to go through the trouble of trying to break that encryption. Now,

0:34:41.640 --> 0:34:45.040
<v Speaker 1>if it's me sending you a file of a bunch

0:34:45.160 --> 0:34:48.920
<v Speaker 1>of actors from Miami connection, it's probably not going to

0:34:49.000 --> 0:34:52.600
<v Speaker 1>be as big a deal. That interesting. Yeah, uh so,

0:34:53.200 --> 0:34:57.200
<v Speaker 1>um forward thinking not that interesting. It's one of the

0:34:57.360 --> 0:35:00.920
<v Speaker 1>many slogans that we ultimately de and not to use

0:35:01.000 --> 0:35:04.120
<v Speaker 1>for this show. Uh. We also we also want to

0:35:04.120 --> 0:35:08.200
<v Speaker 1>point out that this this life I technology would really

0:35:08.239 --> 0:35:12.520
<v Speaker 1>be more about replacing that WiFi point of connection, right,

0:35:12.560 --> 0:35:16.279
<v Speaker 1>It's not about turning the Internet into just light. Right.

0:35:16.360 --> 0:35:19.040
<v Speaker 1>The the backbone of the Internet would remain. The backbone

0:35:19.040 --> 0:35:22.800
<v Speaker 1>of the Internet infrastructure would not change because partially because

0:35:22.800 --> 0:35:24.799
<v Speaker 1>of the range of this kind of thing like it's

0:35:24.840 --> 0:35:27.200
<v Speaker 1>it's really only going to go about three ms before

0:35:27.200 --> 0:35:31.920
<v Speaker 1>it starts becoming less than effective. Yeah, and it's really

0:35:32.200 --> 0:35:34.960
<v Speaker 1>it's about ten feet. Yeah, that the thank you. It's

0:35:35.000 --> 0:35:40.720
<v Speaker 1>really also just good for one way communication for most applications,

0:35:41.160 --> 0:35:44.080
<v Speaker 1>especially if you're thinking about like in your home, and

0:35:44.160 --> 0:35:46.360
<v Speaker 1>let's say that you want to use Life I instead

0:35:46.360 --> 0:35:50.480
<v Speaker 1>of WiFi. Well, unless you have all of your devices

0:35:50.920 --> 0:35:55.719
<v Speaker 1>with bright lights that can communicate back up through the receivers,

0:35:56.080 --> 0:35:58.880
<v Speaker 1>and you have receivers all over your home, this is

0:35:58.880 --> 0:36:01.960
<v Speaker 1>not that know, that's not that useful. Like if you

0:36:02.040 --> 0:36:04.239
<v Speaker 1>move out from one room to another room, you would

0:36:04.280 --> 0:36:06.000
<v Speaker 1>have to have these receivers in every room. It's not

0:36:06.040 --> 0:36:09.160
<v Speaker 1>like WiFi where you could in theory, set up a

0:36:09.280 --> 0:36:11.640
<v Speaker 1>router in one part of your house and it serves

0:36:11.680 --> 0:36:14.440
<v Speaker 1>the whole house. Right, So, like, for example, I live

0:36:14.440 --> 0:36:17.400
<v Speaker 1>in a house that has multiple floors. It's it's kind

0:36:17.400 --> 0:36:21.320
<v Speaker 1>of like in a flat style. Ironically it's flat but

0:36:21.360 --> 0:36:23.920
<v Speaker 1>has multiple floors. Anyway, I put it in the middle

0:36:24.600 --> 0:36:27.280
<v Speaker 1>level of this of my house, and I get service

0:36:27.320 --> 0:36:30.000
<v Speaker 1>both in the bottom floor and the top floor. It

0:36:30.000 --> 0:36:31.759
<v Speaker 1>wouldn't work that way with life I would have to

0:36:31.800 --> 0:36:34.359
<v Speaker 1>have the light bulbs and receivers in all those rooms.

0:36:34.360 --> 0:36:36.480
<v Speaker 1>In order to have two way communication, you must have

0:36:36.480 --> 0:36:38.799
<v Speaker 1>a good router, right, I have a hard time getting

0:36:38.840 --> 0:36:41.360
<v Speaker 1>a signal in the next room. Well. Also, my the

0:36:41.400 --> 0:36:44.520
<v Speaker 1>way my house is designed, it's like it's almost like

0:36:44.560 --> 0:36:47.279
<v Speaker 1>a chimney, and that it has a stairway, an open

0:36:47.320 --> 0:36:49.319
<v Speaker 1>stairway that goes all the way from the bottom all

0:36:49.320 --> 0:36:51.399
<v Speaker 1>the way to the top. So it's not like there

0:36:51.400 --> 0:36:55.759
<v Speaker 1>are doorways or anything. You you pretty much have a

0:36:55.880 --> 0:36:59.680
<v Speaker 1>big chamber that's that's divided by floors. But yeah, it's

0:36:59.680 --> 0:37:01.680
<v Speaker 1>it's a really quite a It seems to be a

0:37:01.719 --> 0:37:04.680
<v Speaker 1>pretty decent router. I do get fine service in whatever

0:37:04.760 --> 0:37:07.560
<v Speaker 1>rooms I happen to be in, but uh, Life I

0:37:07.560 --> 0:37:09.319
<v Speaker 1>would be different for that. It would be really good

0:37:09.320 --> 0:37:11.840
<v Speaker 1>for one way communication where you want to beam something

0:37:11.920 --> 0:37:17.560
<v Speaker 1>like movies or pictures, sound files, that kind of stuff. So, um,

0:37:17.600 --> 0:37:20.480
<v Speaker 1>if you look at the pure life I page, for example,

0:37:21.320 --> 0:37:24.600
<v Speaker 1>they say, well, one of the places where we're seeing

0:37:24.640 --> 0:37:28.080
<v Speaker 1>a lot of WiFi crunch is in consumption. The fact

0:37:28.120 --> 0:37:31.080
<v Speaker 1>that people want to use their Internet connections to watch

0:37:31.120 --> 0:37:34.239
<v Speaker 1>stuff like Netflix, or they want to use it to

0:37:34.600 --> 0:37:37.200
<v Speaker 1>uh to watch YouTube. You know, these things that require

0:37:37.200 --> 0:37:41.640
<v Speaker 1>a lot of data throughput video games, stuff like that. Yeah. Yeah,

0:37:41.800 --> 0:37:44.719
<v Speaker 1>so it might be better to use Life I to

0:37:44.840 --> 0:37:47.680
<v Speaker 1>take some of that, uh that load off of the

0:37:47.719 --> 0:37:51.120
<v Speaker 1>wireless spectrum. But you would still use WiFi in your

0:37:51.120 --> 0:37:54.839
<v Speaker 1>devices to communicate back up through the the Internet, So

0:37:55.080 --> 0:37:57.120
<v Speaker 1>it would be kind of a tag team. And part

0:37:57.160 --> 0:37:59.239
<v Speaker 1>of that is because you know, you mentioned you know,

0:37:59.400 --> 0:38:02.920
<v Speaker 1>up link for this down link. In most data plans,

0:38:03.080 --> 0:38:06.560
<v Speaker 1>you'll see that your down link data, your data rate

0:38:06.600 --> 0:38:09.360
<v Speaker 1>tends to be much higher down link than uplink. And

0:38:09.400 --> 0:38:14.520
<v Speaker 1>it's because largely that most of us end up consuming

0:38:14.560 --> 0:38:17.839
<v Speaker 1>more than we upload. Uh. The people in this room

0:38:18.120 --> 0:38:20.680
<v Speaker 1>kind of an exception because we do lots of audio

0:38:20.719 --> 0:38:24.000
<v Speaker 1>and video, But for most people, they're consuming more than

0:38:24.000 --> 0:38:27.360
<v Speaker 1>their generating, so to them, they're more they're more interested

0:38:27.400 --> 0:38:29.640
<v Speaker 1>in getting a very fast rate getting the stuff to

0:38:29.840 --> 0:38:33.279
<v Speaker 1>their computers than to upload because most of the time

0:38:33.280 --> 0:38:38.520
<v Speaker 1>they're uploading relatively small files. Um so this would not

0:38:38.719 --> 0:38:40.719
<v Speaker 1>be that big of a difference between those kind of

0:38:40.719 --> 0:38:45.160
<v Speaker 1>plans and Life Life I. Uh So that's kind of interesting.

0:38:45.160 --> 0:38:49.040
<v Speaker 1>But another potential use of LiFi that Hass pointed out

0:38:49.080 --> 0:38:51.839
<v Speaker 1>actually in his TED talk was imagine that you have

0:38:52.040 --> 0:38:55.719
<v Speaker 1>a system where all the headlights and cars have this

0:38:55.760 --> 0:38:59.040
<v Speaker 1>technology outfitted them, and the traffic signals do too, and

0:38:59.080 --> 0:39:01.439
<v Speaker 1>then you could have cars and even their brake lights

0:39:01.480 --> 0:39:04.160
<v Speaker 1>could have this too. All the cars could communicate with

0:39:04.200 --> 0:39:07.760
<v Speaker 1>one another. They could also communicate with the traffic system.

0:39:07.800 --> 0:39:11.800
<v Speaker 1>You could have a real time, interactive dynamic traffic system

0:39:11.880 --> 0:39:16.000
<v Speaker 1>that responds to changing conditions based upon the communication that's

0:39:16.000 --> 0:39:18.560
<v Speaker 1>going through when people are driving. Now, granted, this would

0:39:18.600 --> 0:39:21.720
<v Speaker 1>require headlights to be on in order for this to work. Obviously,

0:39:21.800 --> 0:39:23.880
<v Speaker 1>if you didn't have your headlines on, then you're not

0:39:23.920 --> 0:39:26.680
<v Speaker 1>transmitting any information. You could receive it, but you wouldn't

0:39:26.719 --> 0:39:28.680
<v Speaker 1>be able to transmit it. So we're saying that the

0:39:28.719 --> 0:39:32.000
<v Speaker 1>incredible feature involves a lot of cars all having their

0:39:32.040 --> 0:39:35.400
<v Speaker 1>headlights on all the time, but never getting stuck at

0:39:35.400 --> 0:39:38.440
<v Speaker 1>stop lights when nobody is going the other way. Possibly,

0:39:38.719 --> 0:39:43.160
<v Speaker 1>possibly at least we would have a robust dynamic traffic

0:39:43.160 --> 0:39:47.239
<v Speaker 1>system at night, at the very least, like if it's

0:39:47.239 --> 0:39:49.080
<v Speaker 1>not during the day, they would at least be at night,

0:39:49.640 --> 0:39:52.759
<v Speaker 1>which is kind of cool. It's an interesting idea, and

0:39:52.840 --> 0:39:54.359
<v Speaker 1>it was one that I had to think about for

0:39:54.400 --> 0:39:57.640
<v Speaker 1>a while because I was trying to, you know, what

0:39:57.800 --> 0:40:00.279
<v Speaker 1>applications would I see this being a PRAC to call

0:40:00.360 --> 0:40:03.480
<v Speaker 1>for and when it comes down to my smartphone, I'm

0:40:03.520 --> 0:40:05.520
<v Speaker 1>not sure that would be that practical because I could

0:40:05.520 --> 0:40:07.879
<v Speaker 1>I could again watch stuff on my phone, I could

0:40:07.960 --> 0:40:10.040
<v Speaker 1>pull stuff down well, as long as you were very

0:40:10.040 --> 0:40:13.320
<v Speaker 1>carefully standing in a place where you were receiving the

0:40:13.440 --> 0:40:17.640
<v Speaker 1>light transmission, because if you moved, if you like, shifted

0:40:17.719 --> 0:40:20.399
<v Speaker 1>so that your head was blocking right and I would

0:40:20.400 --> 0:40:24.040
<v Speaker 1>block the signal. Yeah. That so this definitely has its limitations.

0:40:24.640 --> 0:40:27.080
<v Speaker 1>So I think it's really important to note that right

0:40:27.120 --> 0:40:29.560
<v Speaker 1>to take that into account saying all right, light is

0:40:29.560 --> 0:40:33.400
<v Speaker 1>not going to completely replace WiFi and all applications everywhere.

0:40:33.400 --> 0:40:37.880
<v Speaker 1>It's not practical, but there's some that makes sense. For example, underwater,

0:40:38.400 --> 0:40:41.719
<v Speaker 1>if you want to do uh like a scientific survey

0:40:41.760 --> 0:40:46.040
<v Speaker 1>of an area and you're using multiple underwater rovers, then

0:40:46.160 --> 0:40:48.960
<v Speaker 1>you need a way to communicate with those, and light

0:40:49.080 --> 0:40:52.720
<v Speaker 1>might be better than radio because radio signals attenuate underwater.

0:40:52.760 --> 0:40:55.280
<v Speaker 1>It's why we don't use radar. We use sonar underwater,

0:40:55.400 --> 0:40:58.520
<v Speaker 1>not radar. But light would be very useful in that case.

0:40:58.560 --> 0:41:03.040
<v Speaker 1>You could use this uh amplification modulation to communicate between

0:41:03.480 --> 0:41:06.839
<v Speaker 1>various vehicles or tools to be able to do more

0:41:06.880 --> 0:41:12.360
<v Speaker 1>effective surveys underwater, all sorts of different applications there. So

0:41:12.520 --> 0:41:15.200
<v Speaker 1>it maybe that when we have our underwater hotels that

0:41:15.239 --> 0:41:18.080
<v Speaker 1>we talked about many many moons ago, this is how

0:41:18.120 --> 0:41:22.600
<v Speaker 1>we end up communicating with each other. Um, but you know,

0:41:22.719 --> 0:41:28.040
<v Speaker 1>I'm not gonna hold my breath. I see what you

0:41:28.080 --> 0:41:31.280
<v Speaker 1>did there, Jonathan, I'm almost ashamed of that. And getting

0:41:31.320 --> 0:41:34.919
<v Speaker 1>back to the idea of using light instead of radio

0:41:34.960 --> 0:41:38.840
<v Speaker 1>frequencies in environments where radio frequencies might not be safe,

0:41:39.000 --> 0:41:43.000
<v Speaker 1>so hospitals or potentially planes, although there's a lot of

0:41:43.040 --> 0:41:45.279
<v Speaker 1>people who argue that the whole plane thing is is

0:41:46.480 --> 0:41:53.400
<v Speaker 1>greatly exaggerated, or in areas where electromagnetic interference could potentially

0:41:53.440 --> 0:41:58.120
<v Speaker 1>cause a catastrophic event, like a petrochemical manufacturing plant, where

0:41:58.239 --> 0:42:01.840
<v Speaker 1>if you had electro magnetic interference in part of the system,

0:42:01.840 --> 0:42:06.640
<v Speaker 1>it could cause an explosion. UM, light is harmless in

0:42:06.640 --> 0:42:10.320
<v Speaker 1>that scenario, you could use light instead to transmit information

0:42:11.000 --> 0:42:15.960
<v Speaker 1>and get around that electromagnetic frequency interference and uh, and

0:42:16.040 --> 0:42:20.800
<v Speaker 1>so it could be really useful in those applications. UM,

0:42:20.880 --> 0:42:22.640
<v Speaker 1>I don't know if we're going to see that, because

0:42:22.680 --> 0:42:25.520
<v Speaker 1>I mean, at least for airplanes, obviously it would require

0:42:25.640 --> 0:42:30.960
<v Speaker 1>that people have devices that are compatible with this technology. Um.

0:42:31.160 --> 0:42:35.280
<v Speaker 1>And unless it becomes so widespread that everything comes with it,

0:42:35.280 --> 0:42:37.520
<v Speaker 1>it may that may never happen, but it might end

0:42:37.600 --> 0:42:40.840
<v Speaker 1>up being something that is used to transmit information directly

0:42:40.840 --> 0:42:43.480
<v Speaker 1>to an entertainment system that's embedded in the plane itself.

0:42:43.920 --> 0:42:46.399
<v Speaker 1>That's a possibility. UM. So I thought that was all

0:42:46.480 --> 0:42:50.440
<v Speaker 1>very interesting, and you know, it's a neat idea. It's

0:42:50.440 --> 0:42:53.920
<v Speaker 1>a neat way to get around this radio frequency spectrum crunch,

0:42:54.160 --> 0:42:57.799
<v Speaker 1>at least in specific applications. And obviously it's this kind

0:42:57.800 --> 0:43:00.920
<v Speaker 1>of thinking that is required for us to continue on

0:43:00.960 --> 0:43:05.279
<v Speaker 1>this path of UM evolution as we add more and

0:43:05.360 --> 0:43:09.399
<v Speaker 1>more demands to this internet infrastructure we've built. Yeah, I'm

0:43:09.400 --> 0:43:12.359
<v Speaker 1>really excited to see whether or not it picks up. Yeah,

0:43:12.480 --> 0:43:15.920
<v Speaker 1>me too. I been interested in in reading about it

0:43:15.960 --> 0:43:19.600
<v Speaker 1>over the past year, and it's recently popped up again

0:43:19.719 --> 0:43:23.560
<v Speaker 1>as as people have uh kind of rediscovered it or

0:43:23.640 --> 0:43:26.479
<v Speaker 1>some people have discovered it for the first time. And um,

0:43:26.600 --> 0:43:28.800
<v Speaker 1>I would love to see a demonstration of this personally,

0:43:28.840 --> 0:43:32.520
<v Speaker 1>like an actual demonstration. I'm so. I kicked myself that

0:43:32.640 --> 0:43:36.200
<v Speaker 1>there was apparently a demonstration of a smartphone outfitted with

0:43:36.320 --> 0:43:38.799
<v Speaker 1>a receiver that would allow it to take in this

0:43:38.920 --> 0:43:42.040
<v Speaker 1>information at C E HAS two thousand and fourteen. You

0:43:42.080 --> 0:43:45.840
<v Speaker 1>were there. I was there, and I didn't know about it.

0:43:45.920 --> 0:43:48.319
<v Speaker 1>I'm kicking myself. There's so much it's c ES. It's

0:43:48.320 --> 0:43:49.960
<v Speaker 1>not like you can see every single thing on the ship.

0:43:50.280 --> 0:43:53.080
<v Speaker 1>There are upwards of a dozen booths at C E

0:43:53.360 --> 0:43:58.319
<v Speaker 1>S every couple of square feet. Yeah. No, C E

0:43:58.480 --> 0:44:00.200
<v Speaker 1>S has a lot stuff, a lot of stuff going on.

0:44:00.239 --> 0:44:01.480
<v Speaker 1>But this would have been one of those things that

0:44:01.520 --> 0:44:03.439
<v Speaker 1>I wish I had known about going into it, because

0:44:03.440 --> 0:44:05.680
<v Speaker 1>it would have been I clearly would have covered it.

0:44:06.160 --> 0:44:09.240
<v Speaker 1>This would have been a great story for forward thinking.

0:44:09.560 --> 0:44:11.840
<v Speaker 1>But here's hoping that I might see something similar to

0:44:11.880 --> 0:44:16.400
<v Speaker 1>that next C E S. So hope springs eternal. But

0:44:16.760 --> 0:44:19.520
<v Speaker 1>this was really fun to kind of talk about this technology.

0:44:19.560 --> 0:44:24.680
<v Speaker 1>We don't often focus on a specific tech like this.

0:44:25.360 --> 0:44:27.719
<v Speaker 1>We tend to look at more broad topics, but this

0:44:27.840 --> 0:44:30.239
<v Speaker 1>was kind of fun to look at a specific implementation.

0:44:30.280 --> 0:44:33.359
<v Speaker 1>If you guys have anything futuristic that you want us

0:44:33.360 --> 0:44:36.319
<v Speaker 1>to talk about, whether it's a specific type of technology

0:44:36.400 --> 0:44:38.600
<v Speaker 1>or it's just an idea, you know, what will X

0:44:38.640 --> 0:44:40.360
<v Speaker 1>be like in the future, You need to get in

0:44:40.400 --> 0:44:42.279
<v Speaker 1>touch with us. Let us know we love to hear

0:44:42.320 --> 0:44:45.879
<v Speaker 1>from you. Our email addresses f w Thinking at how

0:44:45.960 --> 0:44:48.360
<v Speaker 1>Stuff Works dot com, or you can drop us a

0:44:48.360 --> 0:44:51.880
<v Speaker 1>line on Facebook, Twitter, or Google Plus. At Twitter and

0:44:51.920 --> 0:44:55.160
<v Speaker 1>Google Plus, we're FW Thinking, or a Facebook just search

0:44:55.200 --> 0:44:57.560
<v Speaker 1>fw thinking. Our profile will pop up. You can leave

0:44:57.640 --> 0:44:59.680
<v Speaker 1>us a message there and we will talk to you

0:44:59.719 --> 0:45:07.759
<v Speaker 1>a ends really soon. For more on this topic and

0:45:07.800 --> 0:45:12.480
<v Speaker 1>the future of technology, I visit Forward Thinking dot Com

0:45:12.480 --> 0:45:24.680
<v Speaker 1>Problem brought to you by Toyota. Let's Go Places,