WEBVTT - How a medieval king influenced a modern technology

0:00:04.480 --> 0:00:12.360
<v Speaker 1>Welcome to tech Stuff, a production from iHeartRadio. He there,

0:00:12.400 --> 0:00:15.880
<v Speaker 1>and welcome to tech Stuff. I'm your host, Jonathan Strickland.

0:00:15.920 --> 0:00:19.360
<v Speaker 1>I'm an executive producer with iHeart Podcasts. And how the

0:00:19.440 --> 0:00:22.160
<v Speaker 1>tech are you? All right? I got a story for y'all.

0:00:22.880 --> 0:00:28.280
<v Speaker 1>In the mid tenth century, Harold, son of Gorm the Old,

0:00:28.760 --> 0:00:32.279
<v Speaker 1>took up the mission that his father had followed his

0:00:32.479 --> 0:00:35.919
<v Speaker 1>entire life, which was to unite his home country of

0:00:36.000 --> 0:00:40.560
<v Speaker 1>Denmark and then after that further conquer the neighboring regions.

0:00:40.920 --> 0:00:44.800
<v Speaker 1>He converted to Christianity, and then he made the rest

0:00:44.800 --> 0:00:47.120
<v Speaker 1>of the Danes do it too, And he actually went

0:00:47.200 --> 0:00:50.760
<v Speaker 1>so far as to give his father's tomb a Christian

0:00:50.880 --> 0:00:54.000
<v Speaker 1>glow up. Because daddy was a pagan and Mama was

0:00:54.040 --> 0:00:57.760
<v Speaker 1>a go go girl. His own son would eventually rise

0:00:57.880 --> 0:01:01.440
<v Speaker 1>up against him. But what does all this have to

0:01:01.480 --> 0:01:04.919
<v Speaker 1>do with tech, Well, it kind of has a little

0:01:04.920 --> 0:01:08.320
<v Speaker 1>bit to do with oral hygiene. See, back in the

0:01:08.400 --> 0:01:12.440
<v Speaker 1>dark age, is not everybody was fastidious about brushing their

0:01:12.480 --> 0:01:15.600
<v Speaker 1>teeth after every meal, and don't get me started un flossing,

0:01:16.000 --> 0:01:19.480
<v Speaker 1>either dental floss or the outdated meme dance. And Old

0:01:19.560 --> 0:01:22.440
<v Speaker 1>Harry got himself a gammy tooth, So it was a

0:01:22.480 --> 0:01:25.679
<v Speaker 1>dead tooth, you see, and it sort of had this grayish,

0:01:26.319 --> 0:01:29.720
<v Speaker 1>bluish hue. This gave rise to folks referring to him

0:01:29.800 --> 0:01:35.280
<v Speaker 1>as Bluetooth. And this is where the word bluetooth comes from.

0:01:35.360 --> 0:01:38.559
<v Speaker 1>The word we use to name a wireless communications technology

0:01:38.760 --> 0:01:43.360
<v Speaker 1>comes from a medieval Danish king with a gross dead tooth.

0:01:44.000 --> 0:01:47.119
<v Speaker 1>This is not a joke, this is real. So why

0:01:47.920 --> 0:01:52.640
<v Speaker 1>why is Bluetooth named after this? Well, it helps when

0:01:52.680 --> 0:01:57.280
<v Speaker 1>you know that the Swedish telecommunications company Ericsson developed the

0:01:57.280 --> 0:02:01.600
<v Speaker 1>Bluetooth standard. So Sweden has its own history of kings obviously,

0:02:01.840 --> 0:02:06.360
<v Speaker 1>and Sweden is nestled between Denmark and Norway, to countries

0:02:06.400 --> 0:02:09.840
<v Speaker 1>that old Harry stank Tooth ruled over, but Sweden was

0:02:10.120 --> 0:02:13.239
<v Speaker 1>more of a region of different provinces around this time.

0:02:13.600 --> 0:02:18.720
<v Speaker 1>It actually coalesced into a kingdom around nine seventy Common era,

0:02:18.960 --> 0:02:25.600
<v Speaker 1>which was late into Harry Stinkytooth's rain. So maybe none

0:02:25.600 --> 0:02:28.399
<v Speaker 1>of the Swedish kings had suitable nicknames that would work

0:02:28.440 --> 0:02:31.680
<v Speaker 1>as well for a technology. But the engineer leading the

0:02:31.720 --> 0:02:35.640
<v Speaker 1>development of Bluetooth was doctor Yop Hartsen, whose name I

0:02:35.960 --> 0:02:39.000
<v Speaker 1>know I have butchered and I apologize, but he was

0:02:39.040 --> 0:02:42.160
<v Speaker 1>born in the Netherlands. That's actually of no help whatsoever.

0:02:42.320 --> 0:02:45.799
<v Speaker 1>The Netherlands is on the other side of Germany from Denmark.

0:02:46.000 --> 0:02:48.799
<v Speaker 1>Plus the Netherlands didn't become a country of its own

0:02:48.840 --> 0:02:52.480
<v Speaker 1>until fifteen seventy nine, ages after Bluetooth was doing all

0:02:52.520 --> 0:02:55.520
<v Speaker 1>of his unifying and converting over in Denmark and Norway.

0:02:55.960 --> 0:02:58.960
<v Speaker 1>So the name actually came not from a Dane or

0:02:59.000 --> 0:03:02.520
<v Speaker 1>a Swede or a Dutch person. Instead, it came from

0:03:02.639 --> 0:03:07.919
<v Speaker 1>an American, specifically an electrical engineer named Jim Kardak, who

0:03:08.040 --> 0:03:12.880
<v Speaker 1>was working as part of a consortium on this technology. Now,

0:03:12.919 --> 0:03:15.960
<v Speaker 1>the story goes that Jim had been reading a great

0:03:16.000 --> 0:03:19.200
<v Speaker 1>deal about the Vikings and that he had come across

0:03:19.280 --> 0:03:23.080
<v Speaker 1>the story of King Harold Gormson and his Blue Tooth,

0:03:23.360 --> 0:03:26.359
<v Speaker 1>and he thought that Harold, who worked to unite Norway

0:03:26.400 --> 0:03:30.080
<v Speaker 1>and Denmark, was doing something similar to what this consortium

0:03:30.480 --> 0:03:32.960
<v Speaker 1>was trying to do, but on a tech level, which

0:03:33.040 --> 0:03:37.840
<v Speaker 1>was to unite PC and cellular devices through a short

0:03:37.960 --> 0:03:42.520
<v Speaker 1>range wireless communications protocol. Now, the story goes that Bluetooth

0:03:42.800 --> 0:03:45.120
<v Speaker 1>was just a code name. It was not supposed to

0:03:45.120 --> 0:03:49.240
<v Speaker 1>be the permanent name of the technology. But here we are,

0:03:49.480 --> 0:03:51.800
<v Speaker 1>and we'll talk more about that in a second, but

0:03:52.040 --> 0:03:54.560
<v Speaker 1>we got the fun name story out of the way.

0:03:55.480 --> 0:03:57.720
<v Speaker 1>It's kind of like the too long, didn't read version

0:03:57.760 --> 0:04:02.200
<v Speaker 1>of this episode. But let's talk talk about the technology itself. Well,

0:04:02.240 --> 0:04:05.240
<v Speaker 1>take another step back and we'll talk about what prompted

0:04:05.360 --> 0:04:08.400
<v Speaker 1>this idea in the first place, and what role bluetooth

0:04:08.560 --> 0:04:11.640
<v Speaker 1>plays in technology today and how it has evolved over

0:04:11.680 --> 0:04:15.560
<v Speaker 1>the last several years. So back in around nineteen ninety four,

0:04:15.680 --> 0:04:20.240
<v Speaker 1>doctor Hartson over at Ericson was working on developing technologies

0:04:20.279 --> 0:04:24.159
<v Speaker 1>and standards for short range radio communications, and the idea

0:04:24.279 --> 0:04:28.040
<v Speaker 1>was just to cut chords out of the equation, specifically

0:04:28.040 --> 0:04:32.200
<v Speaker 1>the RS two thirty two wired standard. You had all

0:04:32.200 --> 0:04:35.560
<v Speaker 1>these chords and cables that you needed when you had

0:04:35.600 --> 0:04:38.760
<v Speaker 1>a computer connecting to all these different devices. That's kind

0:04:38.800 --> 0:04:41.360
<v Speaker 1>of a hassle. Wouldn't it be nice if you could

0:04:41.400 --> 0:04:45.640
<v Speaker 1>eliminate all that tangled mess and have a wireless means

0:04:45.760 --> 0:04:49.320
<v Speaker 1>of having devices connect and synchronize with one another. That

0:04:49.400 --> 0:04:53.200
<v Speaker 1>would be great. I remember my very first MP three player.

0:04:53.440 --> 0:04:56.400
<v Speaker 1>That one actually required a wired connection to my PC

0:04:56.560 --> 0:04:58.920
<v Speaker 1>if I wanted to add more music to the device.

0:04:59.160 --> 0:05:03.000
<v Speaker 1>The same thing was true for personal Digital Assistance or PDAs.

0:05:03.240 --> 0:05:06.640
<v Speaker 1>You would create your schedule and your contacts list and

0:05:06.640 --> 0:05:09.080
<v Speaker 1>all that kind of stuff on your work computer. Then

0:05:09.120 --> 0:05:12.679
<v Speaker 1>you would connect your PDA to that work computer via

0:05:12.800 --> 0:05:16.080
<v Speaker 1>a cable and transfer the data over so that you

0:05:16.080 --> 0:05:18.600
<v Speaker 1>could have access to that information while you were on

0:05:18.680 --> 0:05:23.440
<v Speaker 1>the go. One potential alternative to wires was using infrared

0:05:23.480 --> 0:05:28.120
<v Speaker 1>transmitters and receivers, similar to how most TV remotes work,

0:05:28.240 --> 0:05:31.280
<v Speaker 1>although we've got Wi Fi TV remotes and Bluetooth ones too,

0:05:31.640 --> 0:05:33.919
<v Speaker 1>but you know, back in the day, it was all infrared,

0:05:34.240 --> 0:05:37.559
<v Speaker 1>and in fact, there are devices that used these kinds

0:05:37.560 --> 0:05:40.680
<v Speaker 1>of methods to transmit data between them. You would connect

0:05:40.720 --> 0:05:44.120
<v Speaker 1>a transmitter slash receiver a transceiver if you will, to

0:05:44.279 --> 0:05:47.120
<v Speaker 1>your computer and you would use, you know, whatever device

0:05:47.200 --> 0:05:50.159
<v Speaker 1>you had that also was outfitted with a transceiver to

0:05:50.440 --> 0:05:53.239
<v Speaker 1>transfer data back and forth. But this meant you needed

0:05:53.240 --> 0:05:56.560
<v Speaker 1>to have line of sight with the transceiver connected to

0:05:56.600 --> 0:05:58.720
<v Speaker 1>the PC in order to do this. So if you've

0:05:58.720 --> 0:06:02.120
<v Speaker 1>ever used an infrared based remote control, you know that

0:06:02.200 --> 0:06:04.799
<v Speaker 1>if you get too out of line with a television

0:06:04.880 --> 0:06:06.839
<v Speaker 1>or a cable bucks or whatever it is you're connected to,

0:06:07.080 --> 0:06:10.080
<v Speaker 1>the remote doesn't work anymore. Same thing if you're doing

0:06:10.120 --> 0:06:12.000
<v Speaker 1>that in the middle of the data transfer, you're not

0:06:12.120 --> 0:06:15.719
<v Speaker 1>gonna get a successful transfer of information. There was a

0:06:15.920 --> 0:06:20.080
<v Speaker 1>problem to be solved here how to manage data transfers

0:06:20.160 --> 0:06:24.479
<v Speaker 1>over short distances without the use of wires or line

0:06:24.480 --> 0:06:28.000
<v Speaker 1>of sight. You didn't need the communications to go very far,

0:06:28.480 --> 0:06:30.760
<v Speaker 1>which would in theory mean you could find solutions that

0:06:30.800 --> 0:06:33.800
<v Speaker 1>didn't require a great deal of power to operate. That

0:06:33.960 --> 0:06:36.839
<v Speaker 1>was important too. Now, batteries have a limited amount of

0:06:36.839 --> 0:06:40.159
<v Speaker 1>power storage, after all, and small batteries in particular have

0:06:40.320 --> 0:06:42.520
<v Speaker 1>very limited power storage. So if you want something that's

0:06:42.520 --> 0:06:45.400
<v Speaker 1>going to fit into like a mobile device form factor,

0:06:45.720 --> 0:06:49.080
<v Speaker 1>it can't require a lot of power or it's not

0:06:49.120 --> 0:06:51.800
<v Speaker 1>going to be useful. Rapid charging was not really a

0:06:51.839 --> 0:06:54.720
<v Speaker 1>thing yet, and you didn't want to drain all your

0:06:54.760 --> 0:06:57.600
<v Speaker 1>devices every time. You just needed to share data between them.

0:06:58.160 --> 0:07:01.159
<v Speaker 1>And so doctor Hartson got to work stone and experimenting

0:07:01.200 --> 0:07:05.200
<v Speaker 1>with short range wireless transmissions. His work led to him

0:07:05.720 --> 0:07:08.960
<v Speaker 1>experimenting in the two point four gigahertz band of radio

0:07:09.000 --> 0:07:12.640
<v Speaker 1>wave frequencies. So, just as a quick reminder, we typically

0:07:12.720 --> 0:07:16.800
<v Speaker 1>measure radio waves in wavelength and in frequency, and these

0:07:16.840 --> 0:07:20.640
<v Speaker 1>have an inverse relationship in that the smaller the wavelength,

0:07:21.120 --> 0:07:25.000
<v Speaker 1>the higher the frequency. A two point four gigahertz frequency

0:07:25.080 --> 0:07:29.040
<v Speaker 1>means that two point four billion wavelengths will pass a

0:07:29.120 --> 0:07:32.400
<v Speaker 1>given point of space in a second. A two point

0:07:32.440 --> 0:07:36.720
<v Speaker 1>four gigahertz signal is less capable than longer wavelength signals

0:07:36.880 --> 0:07:41.000
<v Speaker 1>to penetrate hard reflective surfaces like concrete or metal, so

0:07:41.040 --> 0:07:43.559
<v Speaker 1>they tend to bounce off of these surfaces. But doctor

0:07:43.600 --> 0:07:47.160
<v Speaker 1>Hartson was concerned with short range communications, so that wasn't

0:07:47.200 --> 0:07:51.240
<v Speaker 1>a deal breaker, right, Like if the Bluetooth signals or

0:07:51.280 --> 0:07:55.120
<v Speaker 1>what would become Bluetooth signals can't go through walls, not

0:07:55.240 --> 0:07:57.960
<v Speaker 1>that big a deal. It wasn't intended to be a

0:07:58.080 --> 0:08:02.240
<v Speaker 1>long range communications solution. He also wanted his solution to

0:08:02.240 --> 0:08:04.840
<v Speaker 1>be very power efficient, so it wasn't like the transmitters

0:08:04.880 --> 0:08:07.880
<v Speaker 1>were going to be blasting this out at high amplitudes.

0:08:08.320 --> 0:08:11.160
<v Speaker 1>One issue that he faced was that some Wi Fi

0:08:11.200 --> 0:08:13.920
<v Speaker 1>protocols were already making use of signals in the two

0:08:13.960 --> 0:08:17.120
<v Speaker 1>point four a gighertz band of frequencies, which meant any

0:08:17.200 --> 0:08:21.200
<v Speaker 1>other protocol would need to account for potential interference with

0:08:21.320 --> 0:08:23.960
<v Speaker 1>those signals, Like if you're all just broadcasting on the

0:08:24.000 --> 0:08:27.200
<v Speaker 1>same signal, things are going to get messy. They'll just

0:08:27.280 --> 0:08:31.440
<v Speaker 1>interfere with one another. So doctor Hartson implemented frequency hopping

0:08:31.480 --> 0:08:34.600
<v Speaker 1>practices so that Bluetooth devices could operate in the same

0:08:34.720 --> 0:08:38.080
<v Speaker 1>environment as Wi Fi without the signals actually getting crossed.

0:08:38.440 --> 0:08:41.120
<v Speaker 1>And I should also mention the name Bluetooth still was

0:08:41.160 --> 0:08:43.240
<v Speaker 1>not in use yet, that had not become a thing.

0:08:43.640 --> 0:08:46.360
<v Speaker 1>So while doctor Hartson was working on these protocols that

0:08:46.400 --> 0:08:49.760
<v Speaker 1>would become part of Bluetooth efforts, a few companies were

0:08:49.880 --> 0:08:53.000
<v Speaker 1>forming this consortium to create a technology that had the

0:08:53.040 --> 0:08:56.480
<v Speaker 1>same goals as what Hertson had over at Ericson, and

0:08:56.640 --> 0:09:00.400
<v Speaker 1>these companies created what was called the Bluetooth Special Interest Group,

0:09:00.520 --> 0:09:02.640
<v Speaker 1>or eventually it was called that it was a special

0:09:02.679 --> 0:09:05.520
<v Speaker 1>interest group that didn't have a name for the technology.

0:09:05.600 --> 0:09:10.720
<v Speaker 1>Initially this began with a collaboration between Ericsson and Nokia

0:09:11.240 --> 0:09:15.160
<v Speaker 1>and Intel. Around nineteen ninety six to nineteen ninety eight

0:09:15.240 --> 0:09:18.800
<v Speaker 1>is when this started to get moving. This was when

0:09:19.000 --> 0:09:22.880
<v Speaker 1>Jim Kardak first proposed the code name Bluetooth for the technology.

0:09:23.080 --> 0:09:27.640
<v Speaker 1>The Special Interest Group or SIG SIG would grow significantly,

0:09:27.840 --> 0:09:31.040
<v Speaker 1>so today SIG boasts a community made up of more

0:09:31.080 --> 0:09:36.040
<v Speaker 1>than forty thousand companies, Okay, the stage is set. We're

0:09:36.080 --> 0:09:38.160
<v Speaker 1>going to take a quick break to thank our sponsors,

0:09:38.200 --> 0:09:40.600
<v Speaker 1>and we'll be back to talk more about the origins

0:09:40.840 --> 0:09:55.400
<v Speaker 1>of Bluetooth. We're back. So SIG, this special interest group

0:09:55.480 --> 0:10:01.200
<v Speaker 1>surrounding this shortwave radio communications protocol, focuses on the task

0:10:01.240 --> 0:10:04.360
<v Speaker 1>at hand. They build on Hartson's work, and they get

0:10:04.400 --> 0:10:07.559
<v Speaker 1>closer to a point where they could launch a standard,

0:10:07.800 --> 0:10:09.840
<v Speaker 1>but they remained stuck on the problem of what they're

0:10:09.840 --> 0:10:12.800
<v Speaker 1>going to name it. So originally the thought was they

0:10:12.800 --> 0:10:16.679
<v Speaker 1>were going to call it Personal Area Networking in alignment

0:10:16.720 --> 0:10:21.520
<v Speaker 1>with Local Area Networking or LAN and Wide Area Networking

0:10:21.679 --> 0:10:26.680
<v Speaker 1>or WAN, but the acronym would be PAN for Personal

0:10:26.800 --> 0:10:29.319
<v Speaker 1>Area Networking, and has it turned out a whole lot

0:10:29.320 --> 0:10:32.880
<v Speaker 1>of folks were using PAN in other ways already lots

0:10:32.920 --> 0:10:36.119
<v Speaker 1>of other trademarks related to PAN out there, so establishing

0:10:36.120 --> 0:10:40.400
<v Speaker 1>brand identity would be really challenging and probably litigious. So

0:10:40.640 --> 0:10:44.320
<v Speaker 1>an alternative proposal was to call it radio wire, but

0:10:44.400 --> 0:10:47.160
<v Speaker 1>the deadline to launch was rapidly approaching, and the team

0:10:47.240 --> 0:10:49.360
<v Speaker 1>had not had the time to actually do a deep

0:10:49.440 --> 0:10:52.520
<v Speaker 1>dive on a trademark search to make sure that radio

0:10:52.600 --> 0:10:56.000
<v Speaker 1>wire wasn't going to conflict with any other existing trademarks,

0:10:56.200 --> 0:11:00.640
<v Speaker 1>so really having no other port in the storm. As

0:11:00.679 --> 0:11:03.920
<v Speaker 1>they were getting close to launch, they didn't have any

0:11:03.920 --> 0:11:06.960
<v Speaker 1>other option but to stick with the code name Bluetooth.

0:11:07.320 --> 0:11:10.960
<v Speaker 1>Harold's gross dental problem would become the official name for

0:11:11.000 --> 0:11:15.200
<v Speaker 1>this technology. Interestingly, it would also provide inspiration for the logo.

0:11:15.520 --> 0:11:17.880
<v Speaker 1>If you look at the logo of Bluetooth, it's actually

0:11:17.920 --> 0:11:21.720
<v Speaker 1>the merger of two different runs. So one of those runes,

0:11:21.720 --> 0:11:23.040
<v Speaker 1>if you were to look at it, kind of looks

0:11:23.040 --> 0:11:26.080
<v Speaker 1>like an asterisk if you had stretched it a little vertically,

0:11:26.400 --> 0:11:29.160
<v Speaker 1>and the other looks like an uppercase B. But the

0:11:29.240 --> 0:11:33.240
<v Speaker 1>bee has sharp bits instead of curves, and they actually

0:11:33.240 --> 0:11:36.960
<v Speaker 1>represent the initials of Hadrald Bluetooth. So it's a Viking

0:11:37.240 --> 0:11:40.160
<v Speaker 1>H and a B combined with one another to make

0:11:40.200 --> 0:11:43.320
<v Speaker 1>the logo, which I think is pretty cute. SIG released

0:11:43.320 --> 0:11:46.920
<v Speaker 1>the first Bluetooth standard, also known as Bluetooth one point zero,

0:11:46.920 --> 0:11:49.720
<v Speaker 1>in nineteen ninety nine. The standard at that time could

0:11:49.720 --> 0:11:52.959
<v Speaker 1>support a theoretical transmission throughput of around seven hundred and

0:11:52.960 --> 0:11:55.640
<v Speaker 1>twenty one kilobits per second, and it had a broadcast

0:11:55.720 --> 0:11:58.960
<v Speaker 1>range of just ten meters or right under thirty three

0:11:59.000 --> 0:12:02.080
<v Speaker 1>feet or so these limitations meant that Bluetooth one point

0:12:02.160 --> 0:12:04.880
<v Speaker 1>zero was not suitable for stuff like streaming audio. You

0:12:04.920 --> 0:12:07.680
<v Speaker 1>could send small packets of data between devices, but it

0:12:07.760 --> 0:12:10.160
<v Speaker 1>just really wasn't up to snuff for things like persistent

0:12:10.200 --> 0:12:14.640
<v Speaker 1>streaming connections between like a phone and some wireless earbuds. Also,

0:12:14.720 --> 0:12:17.600
<v Speaker 1>when I say seven hundred and twenty one kilobits per second,

0:12:17.920 --> 0:12:21.600
<v Speaker 1>that was just the theoretical throughput. In real world situations

0:12:21.640 --> 0:12:25.520
<v Speaker 1>you would typically get much smaller or lower throughputs. And

0:12:25.559 --> 0:12:29.680
<v Speaker 1>that's the case with any data transfer technology. You'll often

0:12:29.760 --> 0:12:34.240
<v Speaker 1>hear one figure advertised and then in practice you'll find

0:12:34.240 --> 0:12:38.439
<v Speaker 1>that you get something very different. And it's just because ideally,

0:12:38.679 --> 0:12:41.880
<v Speaker 1>if everything works exactly as it can at the best

0:12:41.880 --> 0:12:45.120
<v Speaker 1>of its ability, you'll get that theoretical top end. It's

0:12:45.160 --> 0:12:48.960
<v Speaker 1>just the real world rarely is ideal. Now, the first

0:12:48.960 --> 0:12:51.240
<v Speaker 1>device is to actually feature Bluetooth chips, and them came

0:12:51.240 --> 0:12:55.480
<v Speaker 1>out around two thousand. The very first phone to include it,

0:12:55.920 --> 0:12:59.400
<v Speaker 1>at least as as far as manufacturing is concerned, was

0:12:59.440 --> 0:13:03.040
<v Speaker 1>the Sony Ericson T thirty six mobile phone. Makes sense,

0:13:03.240 --> 0:13:06.320
<v Speaker 1>Ericson was behind this effort from the very beginning, but

0:13:06.600 --> 0:13:10.000
<v Speaker 1>that was not the first phone to actually hit store shelves.

0:13:10.400 --> 0:13:12.920
<v Speaker 1>That one would be the T thirty nine, and it

0:13:12.960 --> 0:13:15.360
<v Speaker 1>came out in early two thousand and one. The aim

0:13:15.400 --> 0:13:17.560
<v Speaker 1>of Bluetooth one point zero was just to serve as

0:13:17.600 --> 0:13:20.840
<v Speaker 1>a wireless alternative to that RS two thirty two standard.

0:13:20.960 --> 0:13:24.520
<v Speaker 1>Lots of computer devices relied on that standard, from printers

0:13:24.559 --> 0:13:28.600
<v Speaker 1>to computer mice, to external hard drives to modems, and

0:13:28.640 --> 0:13:30.960
<v Speaker 1>again that adds up to a whole bunch of cables.

0:13:31.120 --> 0:13:34.040
<v Speaker 1>So Bluetooth one point zero provided a chance to free

0:13:34.200 --> 0:13:38.240
<v Speaker 1>users from the tangled web. The technology wasn't an overnight

0:13:38.280 --> 0:13:41.640
<v Speaker 1>smash success though. For one thing, it was competing against

0:13:41.640 --> 0:13:46.720
<v Speaker 1>Wi Fi protocols. Wi Fi, however, was much more expensive. Bluetooth,

0:13:47.000 --> 0:13:50.559
<v Speaker 1>being a cheaper alternative could help manufacturers keep the cost

0:13:50.600 --> 0:13:54.200
<v Speaker 1>of production lower on their devices. The other big reason

0:13:54.240 --> 0:13:56.320
<v Speaker 1>it took a while for Bluetooth to really take off

0:13:56.440 --> 0:13:59.320
<v Speaker 1>is that it's rare that someone actually updates all of

0:13:59.360 --> 0:14:02.000
<v Speaker 1>their equipment and devices at the same time, and it

0:14:02.040 --> 0:14:04.520
<v Speaker 1>doesn't do you much good if only one half of

0:14:04.600 --> 0:14:07.920
<v Speaker 1>the devices you need to pair together supports Bluetooth, so

0:14:08.000 --> 0:14:11.640
<v Speaker 1>adoption took a little time. With the introduction of Bluetooth

0:14:11.720 --> 0:14:14.160
<v Speaker 1>one point one in two thousand and one, you could

0:14:14.200 --> 0:14:17.880
<v Speaker 1>hold a voice call over Bluetooth, but the fidelity requirement

0:14:17.920 --> 0:14:20.680
<v Speaker 1>for a voice call is lower than what you would

0:14:20.680 --> 0:14:23.640
<v Speaker 1>want for music, at least for most folks anyway, so

0:14:23.720 --> 0:14:27.040
<v Speaker 1>you still weren't really using Bluetooth to listen to music

0:14:27.120 --> 0:14:30.200
<v Speaker 1>off a device. The features introduced in this update included

0:14:30.240 --> 0:14:34.400
<v Speaker 1>Bluetooth Headset Profile and the hands Free Profile. In two

0:14:34.440 --> 0:14:37.360
<v Speaker 1>thousand and three, Bluetooth one point two would introduce the

0:14:37.520 --> 0:14:43.320
<v Speaker 1>Advanced Audio Distribution Profile aka A two DP, which sounds

0:14:43.360 --> 0:14:46.280
<v Speaker 1>like it's a Star Wars droid. This was the upgrade

0:14:46.280 --> 0:14:49.600
<v Speaker 1>that would allow for actual streaming music and other high

0:14:49.680 --> 0:14:53.320
<v Speaker 1>end audio to wireless speakers and headsets. So really it

0:14:53.400 --> 0:14:56.400
<v Speaker 1>was with one point two, which again launched in two

0:14:56.400 --> 0:14:58.680
<v Speaker 1>thousand and three, where we started to really kind of

0:14:58.720 --> 0:15:02.720
<v Speaker 1>see the true potential for Bluetooth as far as consumer

0:15:02.800 --> 0:15:06.760
<v Speaker 1>devices go. SIG continued to evolve the standard. They improved

0:15:06.800 --> 0:15:08.560
<v Speaker 1>it in two thousand and four with the release of

0:15:08.600 --> 0:15:11.520
<v Speaker 1>Bluetooth two point zero. The big advance here was improved

0:15:11.640 --> 0:15:15.160
<v Speaker 1>range of operation and data bandwidth. This version included support

0:15:15.200 --> 0:15:18.560
<v Speaker 1>for remote control devices for audio and visual technologies. An

0:15:18.600 --> 0:15:20.920
<v Speaker 1>update in two thousand and seven called Bluetooth two point

0:15:20.960 --> 0:15:25.240
<v Speaker 1>one included a much needed security update. So originally Bluetooth

0:15:25.280 --> 0:15:29.040
<v Speaker 1>would broadcast out a device's address just willy nilly, it

0:15:29.160 --> 0:15:31.760
<v Speaker 1>just it had to. That was part of the the standard,

0:15:32.000 --> 0:15:36.080
<v Speaker 1>and one early concern around Bluetooth implementations was that it

0:15:36.120 --> 0:15:39.240
<v Speaker 1>could be possible for an unauthorized individual to connect to

0:15:39.320 --> 0:15:42.920
<v Speaker 1>a Bluetooth transceiver that was in pairing mode, and that's

0:15:42.920 --> 0:15:45.320
<v Speaker 1>clearly not a great thing if you want really good

0:15:45.360 --> 0:15:48.240
<v Speaker 1>security and privacy. In two thousand and nine we got

0:15:48.240 --> 0:15:51.200
<v Speaker 1>Bluetooth three point zero. This allowed for high speed data

0:15:51.240 --> 0:15:54.560
<v Speaker 1>transfers between devices connected via Bluetooth, and by high speed,

0:15:54.600 --> 0:15:57.120
<v Speaker 1>I mean like twenty three megabits per second, which still

0:15:57.160 --> 0:15:59.200
<v Speaker 1>is not it's not super fast compared to Wi Fi,

0:15:59.480 --> 0:16:02.960
<v Speaker 1>but it was a huge step over earlier versions of Bluetooth.

0:16:03.000 --> 0:16:06.040
<v Speaker 1>And besides, Bluetooth's purpose was to fill a specific niche

0:16:06.040 --> 0:16:10.080
<v Speaker 1>in wireless communications. It wasn't to replace Wi Fi, it

0:16:10.160 --> 0:16:14.320
<v Speaker 1>was to augment what WiFi is already doing. In twenty thirteen,

0:16:14.720 --> 0:16:18.360
<v Speaker 1>we got a split with Bluetooth, so one branch of

0:16:18.400 --> 0:16:22.200
<v Speaker 1>the fork went with the longer range, higher bandwidth version

0:16:22.280 --> 0:16:25.040
<v Speaker 1>of Bluetooth that we've been talking about so this version

0:16:25.080 --> 0:16:27.880
<v Speaker 1>requires a little bit more power than the other branch

0:16:28.000 --> 0:16:30.840
<v Speaker 1>of the fork. This would become low energy or l

0:16:30.960 --> 0:16:35.320
<v Speaker 1>E Bluetooth. This alternative version was ideal for wearables devices

0:16:35.320 --> 0:16:38.680
<v Speaker 1>that had much smaller batteries. The LE Bluetooth protocol is

0:16:38.720 --> 0:16:41.080
<v Speaker 1>more energy efficient and thus doesn't put too much of

0:16:41.080 --> 0:16:44.360
<v Speaker 1>a strain on devices that have these small batteries. Both

0:16:44.360 --> 0:16:46.840
<v Speaker 1>branches would get an update in twenty seventeen with the

0:16:46.880 --> 0:16:50.320
<v Speaker 1>release of Bluetooth five, which added in more improvements both

0:16:50.320 --> 0:16:55.480
<v Speaker 1>in data transfer bandwidth and in range. Bluetooth, particularly l

0:16:55.560 --> 0:16:58.120
<v Speaker 1>E Bluetooth, is also used in a lot of Internet

0:16:58.120 --> 0:17:03.000
<v Speaker 1>of Things implementations. IoT devices communicate in small data transfers

0:17:03.040 --> 0:17:06.800
<v Speaker 1>and require frequent or persistent connections, so an energy efficient

0:17:06.840 --> 0:17:11.159
<v Speaker 1>protocol designed for small data transfers is ideal. Recently, in

0:17:11.240 --> 0:17:15.960
<v Speaker 1>twenty twenty two, SIG released new LEE Audio specifications allowing

0:17:15.960 --> 0:17:19.760
<v Speaker 1>for low energy Bluetooth implementations with quality improvements for audio,

0:17:20.119 --> 0:17:24.000
<v Speaker 1>and in twenty twenty three, Bluetooth five point four introduced

0:17:24.080 --> 0:17:28.679
<v Speaker 1>synchronized communication between devices in a particular area using periodic

0:17:28.760 --> 0:17:33.320
<v Speaker 1>broadcast control. Now this is ideal for IoT implementations. You

0:17:33.400 --> 0:17:37.080
<v Speaker 1>might have like a central control hub and hundreds or

0:17:37.080 --> 0:17:41.240
<v Speaker 1>even potentially thousands of low powered IoT sensors all forming

0:17:41.240 --> 0:17:43.720
<v Speaker 1>part of the network, and they might use this particular

0:17:43.840 --> 0:17:48.199
<v Speaker 1>version of Bluetooth to transfer information between them because it

0:17:48.280 --> 0:17:52.439
<v Speaker 1>has that very power efficient design to it, and throughout

0:17:52.440 --> 0:17:56.240
<v Speaker 1>the evolution, engineers made sure to keep Bluetooth backwards compatible,

0:17:56.320 --> 0:17:59.480
<v Speaker 1>so if one device supports Bluetooth five but the other

0:17:59.480 --> 0:18:02.800
<v Speaker 1>one is limited to Bluetooth three, these two devices can

0:18:02.840 --> 0:18:06.080
<v Speaker 1>still talk to each other, which is a gosh darn

0:18:06.160 --> 0:18:10.240
<v Speaker 1>good decision to make. So that's the skinny on Bluetooth,

0:18:10.320 --> 0:18:13.160
<v Speaker 1>a very high level look at it, and I really

0:18:13.200 --> 0:18:17.240
<v Speaker 1>think it's interesting to note that this thing was never

0:18:17.320 --> 0:18:20.159
<v Speaker 1>meant to be called Bluetooth permanently. That was just kind

0:18:20.200 --> 0:18:24.240
<v Speaker 1>of a code name, a funny little quirky thing to choose,

0:18:24.800 --> 0:18:31.200
<v Speaker 1>inspired by a medieval Danish king with a nasty tooth,

0:18:31.320 --> 0:18:35.639
<v Speaker 1>and that ends up becoming a formative wireless technology that

0:18:35.680 --> 0:18:39.600
<v Speaker 1>we use today. I love stories like that. I hope

0:18:39.880 --> 0:18:42.679
<v Speaker 1>you are all well, and I'll talk to you again

0:18:43.480 --> 0:18:53.120
<v Speaker 1>really soon. Tech Stuff is an iHeartRadio production. For more

0:18:53.160 --> 0:18:57.920
<v Speaker 1>podcasts from iHeartRadio, visit the iHeartRadio app, Apple Podcasts, or

0:18:57.920 --> 0:19:03.600
<v Speaker 1>wherever you listen to your favorite shows,