WEBVTT

00:00:00.000 --> 00:00:03.459
We are live with episode 219 of the G2 on 5G.

00:00:03.520 --> 00:00:05.780
It's the latest Insight Scoop on everything 5G.

00:00:06.200 --> 00:00:08.660
We cover six topics in about 20 minutes and it's

00:00:08.660 --> 00:00:10.080
brought to you by more insights and strategy.

00:00:10.720 --> 00:00:12.580
I'm Will Townsend and joining me again this week

00:00:12.580 --> 00:00:15.179
is fellow analyst Anshul Saag. Let's get started

00:00:15.179 --> 00:00:17.120
with my first topic and I wanna talk about T

00:00:17.120 --> 00:00:19.739
-Mobile and they are readying their plans for

00:00:19.739 --> 00:00:22.179
5G advance in the United States. And this is

00:00:22.179 --> 00:00:24.239
actually a light reading article that our friend

00:00:24.239 --> 00:00:28.820
Mike Dano wrote after speaking with Will. at

00:00:28.820 --> 00:00:32.219
T -Mobile. Now, one of the challenges is the

00:00:32.219 --> 00:00:34.460
whole definition of 5G advanced according to

00:00:34.460 --> 00:00:39.060
the 3GPP is pretty vague and ambiguous. Broad.

00:00:39.299 --> 00:00:43.060
Yeah, very broad. And so this is how Ulf and

00:00:43.060 --> 00:00:45.880
the team at T -Mobile define it. Not surprisingly,

00:00:46.020 --> 00:00:49.500
number one has to involve a standalone 5G core,

00:00:49.679 --> 00:00:53.359
which T -Mobile launched in 2020. T -Mobile also

00:00:53.359 --> 00:00:57.079
defines 5G advanced utilizing carrier aggregation.

00:00:57.740 --> 00:00:59.799
and today t -mobile currently aggregates four

00:00:59.799 --> 00:01:02.979
bands on the downlink and t on the uplink and

00:01:02.979 --> 00:01:05.659
they expect to increase that downlink to five

00:01:05.659 --> 00:01:08.879
in the near future we've talked about red cap

00:01:08.879 --> 00:01:12.980
reduced capacity 5g t -mobile includes that as

00:01:12.980 --> 00:01:15.579
part of what they're going to do with 5g advanced

00:01:15.579 --> 00:01:18.879
and then finally this is something new to me

00:01:18.879 --> 00:01:22.750
you may be aware of it l4s which is a technology,

00:01:23.010 --> 00:01:25.609
yeah, available on wired networks, but it's intended

00:01:25.609 --> 00:01:28.829
to reduce network latency and packet loss while

00:01:28.829 --> 00:01:31.030
maintaining high throughput, thereby improving

00:01:31.030 --> 00:01:33.709
real -time application performance. There's really

00:01:33.709 --> 00:01:35.950
not a timeframe on when this is going to occur,

00:01:36.290 --> 00:01:38.750
but T -Mobile has indicated that they've begun

00:01:38.750 --> 00:01:41.230
the process of deploying 5G Advanced. And from

00:01:41.230 --> 00:01:44.769
my perspective, this is their opportunity to

00:01:44.769 --> 00:01:47.969
put their foot on the accelerator, continue to

00:01:47.969 --> 00:01:51.069
leverage what they've done with standalone. to

00:01:51.069 --> 00:01:54.890
drive uh new value and and you know performance

00:01:54.890 --> 00:01:57.049
and flexibility within their network and i know

00:01:57.049 --> 00:01:59.329
you caught this my friend what are your thoughts

00:01:59.329 --> 00:02:02.189
about all this is this a true definition of what

00:02:02.189 --> 00:02:04.530
we would consider 5g advanced from your standpoint

00:02:04.530 --> 00:02:10.650
i think 5g advanced is going to actually carry

00:02:10.650 --> 00:02:14.330
a lot of weight in the future yeah i think there's

00:02:14.330 --> 00:02:15.669
going to be a lot of features that will be added

00:02:15.669 --> 00:02:18.449
in the future and it's really interesting because

00:02:18.969 --> 00:02:21.909
If you look at all the new 5G modems that are

00:02:21.909 --> 00:02:25.129
out, they're not release 18 modems. They're release

00:02:25.129 --> 00:02:27.889
17 modems with release 18 features. I think right

00:02:27.889 --> 00:02:30.909
now the problem with release 18 is it's not technically

00:02:30.909 --> 00:02:33.449
finished yet. It's a little bit nebulous still.

00:02:33.889 --> 00:02:38.289
And I think once the standard is like fully released,

00:02:38.550 --> 00:02:41.009
then I think it'll be a lot easier to talk about

00:02:41.009 --> 00:02:44.469
5G advanced a little bit more clearly. But yeah,

00:02:44.509 --> 00:02:46.129
I have no reason to believe that they don't have

00:02:46.129 --> 00:02:48.689
a release 18 network or they won't. They've been

00:02:48.689 --> 00:02:53.530
the fastest to deploy most new standards. And

00:02:53.530 --> 00:02:57.330
they probably have the largest standalone 5G

00:02:57.330 --> 00:03:00.710
network in the world. Yeah, for sure. So I wouldn't

00:03:00.710 --> 00:03:03.650
be surprised to see them leveraging that to deploy

00:03:03.650 --> 00:03:07.710
Release 18. In terms of steps, I see Release

00:03:07.710 --> 00:03:10.949
15 was a big one. Release 16 was a little bit

00:03:10.949 --> 00:03:14.129
less big. 17 was a little bit also incremental.

00:03:14.530 --> 00:03:17.270
And 18, I see, is a big jump. But the thing is...

00:03:17.439 --> 00:03:19.439
18 builds on everything in the previous releases.

00:03:19.460 --> 00:03:22.259
So you have to be up to date to be able to do

00:03:22.259 --> 00:03:24.280
release 18. And I think that's one thing to consider.

00:03:24.400 --> 00:03:27.060
And maybe some networks are going to skip. We've

00:03:27.060 --> 00:03:29.979
seen things happen where Geo, they just skipped

00:03:29.979 --> 00:03:33.099
NSA entirely and went full SA, right? And I could

00:03:33.099 --> 00:03:36.039
see Geo being a release 18 network fairly soon

00:03:36.039 --> 00:03:40.000
as well. I have no reason to question T -Mobile's

00:03:40.000 --> 00:03:43.060
aspirations here. And their definition seems

00:03:43.060 --> 00:03:45.599
pretty on point. And we are seeing a lot of use

00:03:45.599 --> 00:03:50.379
of L4S specifically in a lot of trials and tests.

00:03:50.680 --> 00:03:53.439
The T -Mobile XR trial with Qualcomm and Ericsson

00:03:53.439 --> 00:03:56.240
that utilize L4S network slicing. I think we're

00:03:56.240 --> 00:03:59.020
on the right path. And I think we'll probably

00:03:59.020 --> 00:04:02.960
see more release 18 networks or release 18 -ish

00:04:02.960 --> 00:04:05.939
networks in the next year or two, especially

00:04:05.939 --> 00:04:08.180
since we're seeing a lot of Chinese operators

00:04:08.180 --> 00:04:10.560
talk about that as well. Yeah, the L4S thing

00:04:10.560 --> 00:04:12.800
was an education point for me. Obviously, you're

00:04:12.800 --> 00:04:14.939
very aware of it. You're Mr. Technical. I'm technical

00:04:14.939 --> 00:04:17.660
too. But yeah, it was interesting to learn about

00:04:17.660 --> 00:04:20.220
that. And I think from my perspective, what T

00:04:20.220 --> 00:04:23.540
-Mobile is focused on is finding their own focus

00:04:23.540 --> 00:04:27.240
on 5G advanced. It's straight up from my perspective.

00:04:27.279 --> 00:04:29.000
It makes a lot of sense. So it'll be interesting

00:04:29.000 --> 00:04:32.319
to see how things progress and how the actual

00:04:32.319 --> 00:04:35.360
release standard comes to fruition. But let's

00:04:35.360 --> 00:04:36.939
go to your first topic. And this is pretty big

00:04:36.939 --> 00:04:40.990
news. So late breaking news. Intel has appointed

00:04:40.990 --> 00:04:44.490
its permanent CEO. And you want to talk a little

00:04:44.490 --> 00:04:47.029
bit. I wasn't very familiar with this particular

00:04:47.029 --> 00:04:49.389
person. I know that he was formerly on the board.

00:04:49.790 --> 00:04:51.870
Obviously, you're much more knowledgeable about

00:04:51.870 --> 00:04:55.329
the new CEO. But you want to talk about how his

00:04:55.329 --> 00:04:59.430
appointment might affect the future of 5G and

00:04:59.430 --> 00:05:02.449
what Intel is doing. And by the way, at Mobile

00:05:02.449 --> 00:05:05.129
World Congress, I did sit down with Intel. I

00:05:05.129 --> 00:05:07.189
think we talked about that on a prior podcast.

00:05:08.269 --> 00:05:11.529
Got an understanding of what Intel is doing with

00:05:11.529 --> 00:05:17.170
Xeon 6, that SoC, to drive not only CPCing with

00:05:17.170 --> 00:05:20.470
that, but also managing a whole host of virtualized

00:05:20.470 --> 00:05:23.550
network functionality with that. But hey, let

00:05:23.550 --> 00:05:27.069
me let you take it away there. Yes, Liputan was

00:05:27.069 --> 00:05:32.870
previously on Intel's board from 2022 to 2024.

00:05:33.269 --> 00:05:35.329
So he was on the board for about two years. Yeah.

00:05:35.509 --> 00:05:38.879
And he actually resigned. about seven months

00:05:38.879 --> 00:05:42.560
ago, there wasn't a clear indication of why,

00:05:42.860 --> 00:05:49.420
but the timing was very close to when Intel's

00:05:49.420 --> 00:05:53.779
former CEO, Pat Gelsinger, was, I guess, asked

00:05:53.779 --> 00:05:55.959
to retire. I'm not really sure what the clear

00:05:55.959 --> 00:05:58.639
terminology there is, but did not finish the

00:05:58.639 --> 00:06:00.339
job. And I think a lot of people would have liked

00:06:00.339 --> 00:06:02.759
to have seen him finish the job. And Liputan

00:06:02.759 --> 00:06:06.750
actually left before that. It's very interesting

00:06:06.750 --> 00:06:09.370
that Lipu Tan is now the replacement for Pat

00:06:09.370 --> 00:06:11.709
Gelsinger. He's actually a little bit older than

00:06:11.709 --> 00:06:15.589
Pat. Yeah, 65, right? Yeah, I looked at his age.

00:06:15.769 --> 00:06:17.870
And the reason why that's relevant is actually

00:06:17.870 --> 00:06:21.310
because before Pat Gelsinger, Intel had a policy

00:06:21.310 --> 00:06:25.910
of forced retirement at 65. So it's interesting

00:06:25.910 --> 00:06:29.910
that this is beginning at 65. But other than

00:06:29.910 --> 00:06:32.620
that. I would say he's one of the few people

00:06:32.620 --> 00:06:36.519
in the industry that has the experience of turning

00:06:36.519 --> 00:06:39.860
around a semiconductor company like he did with

00:06:39.860 --> 00:06:43.879
Cadence, but also having the ability to understand

00:06:43.879 --> 00:06:47.480
foundry and chip design, which he's very uniquely.

00:06:47.699 --> 00:06:51.420
He served at Cadence as CEO from 2009 to 2021.

00:06:51.839 --> 00:06:54.860
He was able to help that company recover its

00:06:54.860 --> 00:06:57.519
share price and its place in the market. And

00:06:57.519 --> 00:07:00.459
yeah, I just think that. When you look at what's

00:07:00.459 --> 00:07:02.439
possible, I think there's very few people who

00:07:02.439 --> 00:07:03.899
have the experience and knowledge that he does.

00:07:04.220 --> 00:07:06.699
So I think he's the most qualified person for

00:07:06.699 --> 00:07:09.519
this job. And honestly, he was at the top of

00:07:09.519 --> 00:07:11.759
the list for most people, including myself and

00:07:11.759 --> 00:07:16.019
our boss, Pat. Pat knows him well, right? Yeah.

00:07:16.120 --> 00:07:19.180
Yeah. And I just think that I'm more inclined

00:07:19.180 --> 00:07:21.360
to believe that he knows that Intel needs to

00:07:21.360 --> 00:07:24.100
stay the course. And if you look at where Foundry

00:07:24.100 --> 00:07:26.129
and Product are today, they're actually... pretty

00:07:26.129 --> 00:07:28.670
good place. I think the biggest weakness that

00:07:28.670 --> 00:07:32.490
Intel has is on AI, specifically with AI in the

00:07:32.490 --> 00:07:35.430
data center, not so much on client. And that's

00:07:35.430 --> 00:07:37.629
actually where he has a lot of experience. He's

00:07:37.629 --> 00:07:40.290
on the board of a lot of companies and has lots

00:07:40.290 --> 00:07:43.970
of experience in AI investment as well. So I

00:07:43.970 --> 00:07:46.089
just think that he's the right person for this

00:07:46.089 --> 00:07:48.970
job. My biggest concern is like whether or not

00:07:48.970 --> 00:07:52.910
he has the time before he needs to retire because

00:07:52.910 --> 00:07:56.110
65 is already. up there that's considered retirement

00:07:56.110 --> 00:07:59.009
age in most places right so it'll be interesting

00:07:59.009 --> 00:08:01.610
to see how long he sticks around there's a serious

00:08:01.610 --> 00:08:03.629
revamp that needs to happen in the data center

00:08:03.629 --> 00:08:06.529
for intel and they might be on the right path

00:08:06.529 --> 00:08:09.569
but it's still unclear about accelerators and

00:08:09.569 --> 00:08:12.750
maybe they have to acquire or event joint venture

00:08:12.750 --> 00:08:14.589
with some companies and make that happen but

00:08:14.589 --> 00:08:18.069
regardless i i think that this is the right move

00:08:18.069 --> 00:08:21.220
and i think Intel stock popped 12 % on the news.

00:08:21.300 --> 00:08:24.399
So it was very clearly a vote of confidence from

00:08:24.399 --> 00:08:27.459
investors. And Intel will be having its big vision

00:08:27.459 --> 00:08:32.080
conference in Las Vegas, I believe, April 1st

00:08:32.080 --> 00:08:33.899
and 2nd. I think there will be some opportunities

00:08:33.899 --> 00:08:36.600
there to get an update from the company and hear

00:08:36.600 --> 00:08:40.639
from Liputan himself about the direction. He

00:08:40.639 --> 00:08:45.100
did publish a long letter to the employees. talking

00:08:45.100 --> 00:08:47.399
about remaking the future of the company and

00:08:47.399 --> 00:08:49.980
how they want to be engineering focused. And

00:08:49.980 --> 00:08:51.639
it'll be really interesting to see where the

00:08:51.639 --> 00:08:54.039
company moves under his leadership. But there's

00:08:54.039 --> 00:08:56.080
definitely changes that need to be made. And

00:08:56.080 --> 00:08:58.600
I think that's quite obvious to everyone. It's

00:08:58.600 --> 00:09:00.419
just important to see how those changes are made

00:09:00.419 --> 00:09:03.250
and what direction they go in. Yeah, I'm reading

00:09:03.250 --> 00:09:05.909
between the lines, but I did read some excerpts

00:09:05.909 --> 00:09:08.330
from that employee letter. And certainly he wants

00:09:08.330 --> 00:09:12.070
to bring Intel back into its engineering prowess.

00:09:12.090 --> 00:09:14.370
That's what Intel has been known for. And I read

00:09:14.370 --> 00:09:16.250
between the lines that I think one of the reasons

00:09:16.250 --> 00:09:18.309
why he departed the board was that he fundamentally

00:09:18.309 --> 00:09:22.350
disagreed with some of the direction on outsourcing

00:09:22.350 --> 00:09:25.789
engineering work and that sort of thing. So I

00:09:25.789 --> 00:09:28.129
feel like he's the right person for the role.

00:09:28.549 --> 00:09:31.149
He's got the pedigree. He brings the engineering.

00:09:32.199 --> 00:09:35.440
background to your point he has a record of with

00:09:35.440 --> 00:09:37.799
cadence and bringing him back to profitability

00:09:37.799 --> 00:09:39.679
as well so i think it's a strong move into your

00:09:39.679 --> 00:09:43.299
point after hours the stock was up 12 so that's

00:09:43.299 --> 00:09:47.580
a very positive indication and then not not that

00:09:47.580 --> 00:09:50.740
i that i put a lot of credence in what a lot

00:09:50.740 --> 00:09:52.639
of the the financial analysts on wall street

00:09:52.639 --> 00:09:56.200
say but in general i think it was very well received

00:09:56.200 --> 00:09:58.080
that the news was very well received on wall

00:09:58.080 --> 00:10:00.129
street and that's important for info Because

00:10:00.129 --> 00:10:01.990
it's been a roller coaster there. They've had

00:10:01.990 --> 00:10:04.690
their ups and downs. And engineering execution

00:10:04.690 --> 00:10:08.549
has been a big issue for Intel. So it'll be interesting

00:10:08.549 --> 00:10:11.570
to see what transpires. But on the surface, this

00:10:11.570 --> 00:10:15.309
is very positive. I will add that as of today,

00:10:15.429 --> 00:10:17.929
the market was down like 5 % or 10%, depending

00:10:17.929 --> 00:10:22.450
on the company. Intel's up 15 % after the additional

00:10:22.450 --> 00:10:26.210
on top of the after hours growth. So it popped

00:10:26.210 --> 00:10:30.279
a total of 15 % on this news. Excellent. Interesting.

00:10:30.600 --> 00:10:33.759
Cool. Well, we'll keep our eyes and ears peeled

00:10:33.759 --> 00:10:36.500
to all of this and see how things progress. But

00:10:36.500 --> 00:10:38.639
let's go to my second topic. And I want to talk

00:10:38.639 --> 00:10:40.799
about Broadcom. And this is an announcement that

00:10:40.799 --> 00:10:42.659
I did not catch during Mobile World Congress,

00:10:42.759 --> 00:10:44.940
but this was something I found on the Fierce

00:10:44.940 --> 00:10:48.620
Wireless Network. But Broadcom apparently announced

00:10:48.620 --> 00:10:51.279
a converged 5G fiber and satellite appliance,

00:10:51.519 --> 00:10:56.220
and it's called VeloSky. And what's interesting

00:10:56.220 --> 00:10:59.980
is that Broadcom is targeting this particular

00:10:59.980 --> 00:11:03.700
solution to help mobile network operators, communication

00:11:03.700 --> 00:11:07.059
service providers, supposedly recoup their investments

00:11:07.059 --> 00:11:10.960
in 5G and satellite. And it's targeting the enterprise

00:11:10.960 --> 00:11:14.419
needs for a converged architecture that can feed

00:11:14.419 --> 00:11:17.360
AI applications. And I read through the article

00:11:17.360 --> 00:11:22.519
and from my perspective, I think the value. in

00:11:22.519 --> 00:11:24.759
providing a single link for multiple network

00:11:24.759 --> 00:11:28.519
types could be potentially very compelling. This

00:11:28.519 --> 00:11:31.340
plays really well into Broadcom silicon strings

00:11:31.340 --> 00:11:34.919
within networking. And so I think it's interesting,

00:11:35.179 --> 00:11:40.610
basically. What the Fierce Network article summarizes

00:11:40.610 --> 00:11:43.230
is that given the shift with AI applications,

00:11:43.389 --> 00:11:46.309
the cloud, the whole notion of hybrid deployment,

00:11:46.389 --> 00:11:48.850
and then the notion of software -defined networks

00:11:48.850 --> 00:11:51.769
has just created additional complexities. And

00:11:51.769 --> 00:11:54.049
when you're managing multiple connectivity links,

00:11:54.250 --> 00:11:57.330
it complicates things, especially for enterprises.

00:11:57.429 --> 00:12:00.450
So this seems to me to be the Broadcom's easy

00:12:00.450 --> 00:12:02.789
button for the enterprise. And the timing is

00:12:02.789 --> 00:12:06.399
great, obviously, given... ai workloads and the

00:12:06.399 --> 00:12:08.600
the challenges and demands that those create

00:12:08.600 --> 00:12:11.620
on on network infrastructure in general so i

00:12:11.620 --> 00:12:13.100
don't know if you caught this but any thoughts

00:12:13.100 --> 00:12:16.019
before we move to your next topic no i think

00:12:16.019 --> 00:12:20.080
it's interesting the converged nature of it i

00:12:20.080 --> 00:12:23.259
think will potentially save money but it's unclear

00:12:23.259 --> 00:12:26.720
whether or not this requires a re -architecting

00:12:26.720 --> 00:12:29.769
of the rest of the network So I think it's probably

00:12:29.769 --> 00:12:32.629
beneficial to companies that are already utilizing

00:12:32.629 --> 00:12:36.190
Broadcom infrastructure. But yeah, I think it's

00:12:36.190 --> 00:12:38.629
interesting that it's a clever name. And yeah,

00:12:38.710 --> 00:12:40.690
I think it's definitely interesting, especially

00:12:40.690 --> 00:12:42.929
since they talk about faster monetization of

00:12:42.929 --> 00:12:45.610
5G. Yeah, and that's the classic rub, right?

00:12:45.750 --> 00:12:48.690
For operators that invest billions of dollars

00:12:48.690 --> 00:12:51.690
in license spectrum and infrastructure for each

00:12:51.690 --> 00:12:57.080
of these generational network. topologies and

00:12:57.080 --> 00:12:59.919
finding opportunities to monetize beyond just

00:12:59.919 --> 00:13:02.379
simply access is super important. And there's

00:13:02.379 --> 00:13:04.519
tremendous potential, obviously, with AI as a

00:13:04.519 --> 00:13:06.840
news hybrid. But I think the timing is great,

00:13:06.899 --> 00:13:09.220
plays very well into Broadcom strengths. And

00:13:09.220 --> 00:13:10.799
so it'll be interesting to see how things play

00:13:10.799 --> 00:13:13.360
out here. But let's move to your second topic.

00:13:13.440 --> 00:13:15.320
And this is pretty interesting. I didn't catch

00:13:15.320 --> 00:13:17.220
it. So I'm interested to learn more from you

00:13:17.220 --> 00:13:19.559
about it. But you want to talk about Vodafone

00:13:19.559 --> 00:13:24.309
UK and Ericsson and the use of AI. to actually

00:13:24.309 --> 00:13:26.889
reduce the energy consumption on 5G networks.

00:13:27.809 --> 00:13:30.610
Yes. So this actually, I'm surprised you didn't

00:13:30.610 --> 00:13:32.649
see this because every publication wrote about

00:13:32.649 --> 00:13:36.029
it. But basically they did a trial in the UK

00:13:36.029 --> 00:13:40.470
using Ericsson Advanced AI and ML powered software.

00:13:41.269 --> 00:13:45.309
And they were able to lower the power usage of

00:13:45.309 --> 00:13:48.309
5G radio units by as much as 30 select sites

00:13:48.309 --> 00:13:52.399
in London. That's crazy. And this was... Using

00:13:52.399 --> 00:13:56.379
Ericsson's advanced AI and machine learning -based

00:13:56.379 --> 00:13:59.679
software solutions, the Ericsson Service Continuity

00:13:59.679 --> 00:14:04.679
AI App Suite with intelligent energy efficiency

00:14:04.679 --> 00:14:08.360
dynamically adjusts the network power consumption

00:14:08.360 --> 00:14:12.379
based on demand. Say that fast three times. I

00:14:12.379 --> 00:14:16.179
know. It's way too many words. But they said

00:14:16.179 --> 00:14:18.039
that they implemented three key energy -saving

00:14:18.039 --> 00:14:23.389
features, 5G deep sleep. 4g cell sleep mode orchestration

00:14:23.389 --> 00:14:27.190
and radio power efficiency heat map and erickson

00:14:27.190 --> 00:14:29.809
further explained that 5g deep sleep uses ai

00:14:29.809 --> 00:14:32.169
driven predictive algorithms to allow radios

00:14:32.169 --> 00:14:34.970
to enter an ultra low energy hybridization state

00:14:34.970 --> 00:14:38.789
reducing power usage by up to 70 during off peak

00:14:38.789 --> 00:14:42.470
hours and then that 4g cell sleep mode orchestration

00:14:42.470 --> 00:14:46.429
does a behavioral model of network cells to fine

00:14:46.429 --> 00:14:50.429
-tune sleep parameters to ensure that power savings

00:14:50.429 --> 00:14:53.389
doesn't affect performance and then the radio

00:14:53.389 --> 00:14:56.389
power efficiency map uses ml to create a visual

00:14:56.389 --> 00:14:58.730
representation of all the network cells identifying

00:14:58.730 --> 00:15:01.409
and ranking underperforming sites for targeted

00:15:01.409 --> 00:15:03.529
efficiency improvements so those are like the

00:15:03.529 --> 00:15:06.230
big three things that they were able to implement

00:15:06.230 --> 00:15:08.529
and that's how they achieved these capabilities

00:15:08.529 --> 00:15:11.590
they used ericsson's antenna integrated radio

00:15:11.590 --> 00:15:18.029
530 5322 and baseband 6651 and they use a snapdragon

00:15:18.029 --> 00:15:22.750
x65 modem to rf system in the devices yeah my

00:15:22.750 --> 00:15:26.409
god like a third energy efficiency that's huge

00:15:26.409 --> 00:15:30.769
man it is yeah it's operators some of their biggest

00:15:30.769 --> 00:15:34.409
costs oh it's the number one operational expense

00:15:34.409 --> 00:15:36.690
line is your power bill when chris sambar was

00:15:36.690 --> 00:15:38.850
running networks at at &t he told me it was like

00:15:38.850 --> 00:15:42.120
their power bills like in the billions We were

00:15:42.120 --> 00:15:44.100
just complaining before we got started on our

00:15:44.100 --> 00:15:46.179
podcast about your power bill and your double

00:15:46.179 --> 00:15:49.639
payment. Yes, of course. Yeah, think about the

00:15:49.639 --> 00:15:51.500
power bill that these mobile network operators

00:15:51.500 --> 00:15:54.139
have to fit. Super compelling. Hey, man, let's

00:15:54.139 --> 00:15:55.460
hit my third and final. I'm going to be really

00:15:55.460 --> 00:15:58.320
quick on this one before the cold medication

00:15:58.320 --> 00:16:01.720
wears off. But I caught this on, where was this?

00:16:01.799 --> 00:16:04.019
This was also, this was on the Fierce Electronics

00:16:04.019 --> 00:16:06.860
website, and I didn't catch this, but Qualcomm

00:16:06.860 --> 00:16:09.120
recently acquired a company called Edge Impulse

00:16:09.120 --> 00:16:11.379
to accelerate its drive. Dragonwing IoT design

00:16:11.379 --> 00:16:14.340
one. So we've talked about Dragonwing. We've

00:16:14.340 --> 00:16:16.679
talked about how that's Qualcomm's new brand

00:16:16.679 --> 00:16:19.620
for its infrastructure extension. What's really

00:16:19.620 --> 00:16:22.799
interesting about Edge Impulse, apparently they

00:16:22.799 --> 00:16:25.120
were already working with them. And this is typical,

00:16:25.240 --> 00:16:27.059
right? I think Qualcomm works with these really

00:16:27.059 --> 00:16:29.320
cool companies and then they figure out, wow,

00:16:29.480 --> 00:16:31.379
the IP is awesome. We ought to integrate it.

00:16:31.460 --> 00:16:34.220
But Edge Impulse already supports Dragonwing,

00:16:34.360 --> 00:16:40.309
two processors, the QCS6490 and 5430. But what's

00:16:40.309 --> 00:16:43.789
interesting about Edge Impulse is that it provides

00:16:43.789 --> 00:16:47.309
a developer toolset that allows applications

00:16:47.309 --> 00:16:49.470
to be built for asset tracking and monitoring,

00:16:49.750 --> 00:16:52.549
manufacturing, anomaly detection, predictive

00:16:52.549 --> 00:16:56.450
maintenance, and other things, including the

00:16:56.450 --> 00:16:59.759
use of AI with computer vision. audio and speech

00:16:59.759 --> 00:17:02.299
recognitions. And this complements what obviously

00:17:02.299 --> 00:17:06.259
Qualcomm is doing, integrating NPE and XPE functionality

00:17:06.259 --> 00:17:09.640
into its ASICs. And also, I think on a prior

00:17:09.640 --> 00:17:11.640
podcast, it was probably last year, you and I

00:17:11.640 --> 00:17:14.339
talked about how Qualcomm launched its AI Hub.

00:17:14.880 --> 00:17:17.359
which is designed to provide better inference

00:17:17.359 --> 00:17:19.779
performance with reduced model sizes and memory.

00:17:20.019 --> 00:17:22.900
So this is highly complementary to their overall

00:17:22.900 --> 00:17:25.900
IoT strategy. And from my perspective, Qualcomm

00:17:25.900 --> 00:17:29.099
dabbled there for a while, but now they're super

00:17:29.099 --> 00:17:33.000
serious. New branding, a recent acquisition to

00:17:33.000 --> 00:17:36.609
really double down on IoT. compete with the likes

00:17:36.609 --> 00:17:39.009
of MediaTek and others in this space. So I don't

00:17:39.009 --> 00:17:40.589
know if you caught the news, but what do you

00:17:40.589 --> 00:17:42.529
think about all that? Sorry, I had to run quickly.

00:17:42.750 --> 00:17:46.029
I think it really integrates well into Qualcomm's

00:17:46.029 --> 00:17:48.710
IoT growth strategy. They've been making lots

00:17:48.710 --> 00:17:50.910
of acquisitions in the IoT space. It naturally

00:17:50.910 --> 00:17:52.609
makes sense that they would go after someone

00:17:52.609 --> 00:17:55.549
like Edge Impulse. And it seemed like our colleague,

00:17:55.650 --> 00:17:57.670
Bill, really thought this was a good fit for

00:17:57.670 --> 00:18:00.130
a lot of reasons. Yeah. And in general, I think,

00:18:00.150 --> 00:18:03.150
yeah. And I think the market in general kind

00:18:03.150 --> 00:18:06.140
of received it pretty positively. Yeah, I know.

00:18:06.200 --> 00:18:08.539
I agree with that as well. Qualcomm is just a

00:18:08.539 --> 00:18:12.519
machine. They continue to execute and be very

00:18:12.519 --> 00:18:15.640
laser focused on all of these adjacencies within

00:18:15.640 --> 00:18:17.799
their wheelhouse. Let's hit your third and final.

00:18:18.039 --> 00:18:21.859
And you want to talk about NTN and VSAT and Space

00:18:21.859 --> 00:18:25.660
42 have signed an MOU. So what's that all about?

00:18:26.250 --> 00:18:29.150
I didn't catch that either. So like I. So Viasat

00:18:29.150 --> 00:18:32.009
is a San Diego satellite company and Space 42

00:18:32.009 --> 00:18:38.369
is a Emirati space company. And they are they've

00:18:38.369 --> 00:18:41.130
signed an MOU to try to figure out how they're

00:18:41.130 --> 00:18:44.609
going to serve the direct to device satellite

00:18:44.609 --> 00:18:50.170
connectivity market and implement 5G NTN as a

00:18:50.170 --> 00:18:55.039
technology and. have the two companies work together

00:18:55.039 --> 00:18:57.900
because Viasat's already partnered with the European

00:18:57.900 --> 00:19:01.819
Safety Agency to also work with NTN direct -to

00:19:01.819 --> 00:19:05.440
-device systems. So there's a lot of synergy

00:19:05.440 --> 00:19:08.299
here for Viasat. They're a big satellite provider.

00:19:08.779 --> 00:19:11.720
They provide the connectivity services on American

00:19:11.720 --> 00:19:13.720
Airlines, I know, because I've been living on

00:19:13.720 --> 00:19:17.440
an airplane the last six weeks. So they're working

00:19:17.440 --> 00:19:21.660
together to... deploy these technologies. Space42

00:19:21.660 --> 00:19:25.519
is a startup in the space tech space, and they

00:19:25.519 --> 00:19:28.859
are working hard to make these partnerships work

00:19:28.859 --> 00:19:31.839
together. But yeah, it's really cool, and it's

00:19:31.839 --> 00:19:33.839
interesting to see more competition coming. I

00:19:33.839 --> 00:19:35.279
was wondering when Biosat was going to enter

00:19:35.279 --> 00:19:37.460
this space, but they've already announced some

00:19:37.460 --> 00:19:39.220
partnerships with the European Space Agency as

00:19:39.220 --> 00:19:41.279
well. Yeah, that's it. That's the click of it.

00:19:41.539 --> 00:19:44.579
Yeah, and boy, this is the whole notion of it's

00:19:44.579 --> 00:19:46.420
just going to continue to heat up. I think you're

00:19:46.420 --> 00:19:48.980
going to continue to see more entrants. I think

00:19:48.980 --> 00:19:52.420
I mentioned this on our last podcast when Abel

00:19:52.420 --> 00:19:54.720
Avillian and I met sort of towards the end of

00:19:54.720 --> 00:19:57.019
Mobile World Congress. And I'll be publishing

00:19:57.019 --> 00:19:59.180
a Forbes article, by the way, that sort of captures

00:19:59.180 --> 00:20:01.240
my highlights and insights from the show. And

00:20:01.240 --> 00:20:03.819
I'm hoping I get that posted by the end of this

00:20:03.819 --> 00:20:06.460
week or very early next week. But one of the

00:20:06.460 --> 00:20:08.480
things that I go into a lot of detail about are

00:20:08.480 --> 00:20:13.039
the edge use cases that are beyond what's considered

00:20:13.039 --> 00:20:16.420
the standard fare for low Earth orbit satellite,

00:20:16.640 --> 00:20:19.829
which is. terrestrial network gap coverage and

00:20:19.829 --> 00:20:22.029
so and one of the things that about i talked

00:20:22.029 --> 00:20:25.869
about was the ability to improve the whole broadband

00:20:25.869 --> 00:20:29.069
connectivity experience on aircraft because it's

00:20:29.069 --> 00:20:32.630
today right i saw our illustrious leader patrick

00:20:32.630 --> 00:20:34.750
moorhead sharing something about a you know terrible

00:20:34.750 --> 00:20:37.619
experience he had on a on a flight i don't know

00:20:37.619 --> 00:20:40.160
if it was american or delta and i popped for

00:20:40.160 --> 00:20:42.559
the internet on my way back from barcelona it

00:20:42.559 --> 00:20:44.859
was less than ideal we don't want people doing

00:20:44.859 --> 00:20:47.779
video calls on airplanes obviously but there

00:20:47.779 --> 00:20:49.940
there's a tremendous opportunity to improve that

00:20:49.940 --> 00:20:52.279
overall experience and just a host of other use

00:20:52.279 --> 00:20:54.099
cases i'm going to say it one more time i've

00:20:54.099 --> 00:20:55.980
said it a million times on this podcast over

00:20:55.980 --> 00:20:59.259
the last nearly five years innovation Competition

00:20:59.259 --> 00:21:01.599
breeds innovation, and it's a good thing, I think,

00:21:01.660 --> 00:21:03.940
for the industry. But, my friend, it was another

00:21:03.940 --> 00:21:06.200
great podcast. I got through it without coughing

00:21:06.200 --> 00:21:08.779
once. I think I'm over the hump here. I'm over

00:21:08.779 --> 00:21:11.599
the Spanish flu that I caught in Barcelona last

00:21:11.599 --> 00:21:13.559
week, but why don't you take us home? Absolutely.

00:21:13.720 --> 00:21:15.559
We hope our viewers and listeners found this

00:21:15.559 --> 00:21:17.599
week's topics interesting. If anyone out there

00:21:17.599 --> 00:21:18.980
would like to provide insights for a specific

00:21:18.980 --> 00:21:21.660
5G topic for a future podcast, please reach out

00:21:21.660 --> 00:21:24.119
to us on social media. Will is at WillTownTech,

00:21:24.220 --> 00:21:26.460
and I'm at Anshul Saag. We hope you have a great

00:21:26.460 --> 00:21:28.119
weekend, and please tune in again next week.

00:21:28.940 --> 00:21:30.759
And rate and subscribe. And yeah, don't forget

00:21:30.759 --> 00:21:31.460
to rate and subscribe.
