WEBVTT

1
00:00:00.080 --> 00:00:02.960
<v Speaker 1>Welcome pill and knowledge seekers to the deep dive. We've

2
00:00:02.960 --> 00:00:05.679
<v Speaker 1>all heard the buzz about five G. You know, faster speed,

3
00:00:05.719 --> 00:00:08.359
<v Speaker 1>super low latency, this whole connected future thing. But what

4
00:00:08.400 --> 00:00:11.640
<v Speaker 1>does that really mean when you look under the hood.

5
00:00:11.679 --> 00:00:14.240
<v Speaker 1>What's actually powering this leap, the one that's meant to

6
00:00:14.320 --> 00:00:18.960
<v Speaker 1>change well everything. Today we're taking a fascinating deep dive

7
00:00:19.000 --> 00:00:21.839
<v Speaker 1>into the very heart of it, the five G mobile

8
00:00:21.879 --> 00:00:24.440
<v Speaker 1>core network, and we're really lucky today we've got some

9
00:00:24.480 --> 00:00:27.960
<v Speaker 1>incredibly insightful material to guide us. It's five G Mobile

10
00:00:28.000 --> 00:00:32.759
<v Speaker 1>Core Network design, deployment, automation and testing strategies by Rogenie

11
00:00:32.799 --> 00:00:36.280
<v Speaker 1>Studecar Shetty. Now this author, mister Shetty, he's an industry

12
00:00:36.359 --> 00:00:39.200
<v Speaker 1>expert over two decades of experience, co author to four

13
00:00:39.240 --> 00:00:41.320
<v Speaker 1>G book, holds five G core patents.

14
00:00:41.479 --> 00:00:44.200
<v Speaker 2>Yeah, definitely someone who knows the stuff inside and out.

15
00:00:44.240 --> 00:00:46.280
<v Speaker 2>We're tapping into real authority here.

16
00:00:46.240 --> 00:00:49.520
<v Speaker 1>Exactly so we can understand these shifts from someone who

17
00:00:49.600 --> 00:00:52.759
<v Speaker 1>you know, helped build them. Our mission today, let's pull

18
00:00:52.799 --> 00:00:55.560
<v Speaker 1>back the curtain on that core architecture, shed light on

19
00:00:55.600 --> 00:00:58.719
<v Speaker 1>the key functions, and really reveal the shifts that make

20
00:00:58.880 --> 00:01:03.799
<v Speaker 1>five G a genuine game changer. By the end, you'll

21
00:01:03.799 --> 00:01:06.799
<v Speaker 1>have a clear shortcut to understanding its power, not just

22
00:01:06.840 --> 00:01:09.879
<v Speaker 1>as a phone user, but appreciating the engineering behind it. All.

23
00:01:09.959 --> 00:01:12.000
<v Speaker 2>Okay, sounds great, let's dig in.

24
00:01:12.159 --> 00:01:16.120
<v Speaker 1>You know, looking back, each mobile G brought something really new,

25
00:01:16.159 --> 00:01:16.519
<v Speaker 1>didn't it.

26
00:01:16.560 --> 00:01:17.560
<v Speaker 2>Oh? Absolutely?

27
00:01:17.599 --> 00:01:20.040
<v Speaker 1>One G was that analog voice, amazing for its time.

28
00:01:20.519 --> 00:01:23.719
<v Speaker 1>Then two G the nineties, that was digital SMS, messages

29
00:01:23.959 --> 00:01:27.359
<v Speaker 1>ziconic texts. Yeah. Then three G mobile internet video calls,

30
00:01:27.400 --> 00:01:28.040
<v Speaker 1>email on the.

31
00:01:28.000 --> 00:01:29.000
<v Speaker 2>Move at big step.

32
00:01:29.159 --> 00:01:31.560
<v Speaker 1>And four G well that's the word we basically live

33
00:01:31.599 --> 00:01:34.200
<v Speaker 1>in now, high speed streaming, gaming, right, hailing apps.

34
00:01:34.280 --> 00:01:38.120
<v Speaker 2>Yeah, four G really enabled the modern smartphone experience.

35
00:01:38.159 --> 00:01:40.680
<v Speaker 1>So calling five G just another G, just faster, That

36
00:01:40.719 --> 00:01:43.079
<v Speaker 1>feels like saying a rocket is just a faster car.

37
00:01:43.319 --> 00:01:44.879
<v Speaker 1>It's more fundamental, it is.

38
00:01:45.480 --> 00:01:48.680
<v Speaker 2>What's truly fascinating is how five G isn't just an evolution.

39
00:01:49.560 --> 00:01:54.519
<v Speaker 2>It's designed as a fundamental technology enabler. It's engineered really

40
00:01:54.760 --> 00:01:57.840
<v Speaker 2>to bring things to life that felt like science fiction,

41
00:01:58.200 --> 00:02:00.439
<v Speaker 2>you know, just a few years back. Right, we're talking

42
00:02:00.480 --> 00:02:03.719
<v Speaker 2>about more than just speed boosts. We're seeing totally new

43
00:02:03.760 --> 00:02:08.000
<v Speaker 2>capabilities emerge, groundwork for a future we couldn't quite grasp before.

44
00:02:08.360 --> 00:02:10.719
<v Speaker 1>So what are these core capabilities driving it. The source

45
00:02:10.759 --> 00:02:11.479
<v Speaker 1>highlights three.

46
00:02:11.639 --> 00:02:16.520
<v Speaker 2>Exactly three key ones, each targeting very distinct needs. First,

47
00:02:16.520 --> 00:02:20.240
<v Speaker 2>there's eMBB Enhanced Mobile Broadband.

48
00:02:19.800 --> 00:02:20.960
<v Speaker 1>AH, the speed one.

49
00:02:21.000 --> 00:02:23.800
<v Speaker 2>That's the one everyone talks about. Up to ten gigabits

50
00:02:23.800 --> 00:02:27.560
<v Speaker 2>per second potentially and latency under one millisecond. Think ultra

51
00:02:27.800 --> 00:02:31.560
<v Speaker 2>HD screens, immersive three D video working entirely in the cloud.

52
00:02:31.680 --> 00:02:34.479
<v Speaker 1>Okay, seamless high bandwidth stuff precisely.

53
00:02:34.680 --> 00:02:37.879
<v Speaker 2>Then there's URLLC ultra reliable low latency communication.

54
00:02:38.000 --> 00:02:38.759
<v Speaker 1>That sounds critical.

55
00:02:39.039 --> 00:02:43.400
<v Speaker 2>It absolutely is for mission critical applications where any delay,

56
00:02:43.479 --> 00:02:46.960
<v Speaker 2>any drop could be catastrophic. Imagine autonomous cars needing split

57
00:02:46.960 --> 00:02:49.280
<v Speaker 2>second decisions talking to each other. That's V two V

58
00:02:49.599 --> 00:02:51.520
<v Speaker 2>or the road infrastructure V two X.

59
00:02:51.639 --> 00:02:53.520
<v Speaker 1>Or remote surgery exactly.

60
00:02:53.639 --> 00:02:58.759
<v Speaker 2>A surgeon operating remotely needs flawless real time feedback. URLLC

61
00:02:58.919 --> 00:03:01.879
<v Speaker 2>aims to guarantee that animal delay and maximum uptime.

62
00:03:02.120 --> 00:03:02.879
<v Speaker 1>Wow. Okay.

63
00:03:02.879 --> 00:03:08.319
<v Speaker 2>And the third, and finally, MMTC Massive machine type communication,

64
00:03:08.599 --> 00:03:12.120
<v Speaker 2>so Internet of Things. That's the focus, connecting a staggering

65
00:03:12.199 --> 00:03:17.400
<v Speaker 2>number of IoT devices billions potentially, sensors, actuators, smart gadgets,

66
00:03:17.599 --> 00:03:21.319
<v Speaker 2>think smart surveillance drones over huge areas, or tracking systems

67
00:03:21.360 --> 00:03:23.240
<v Speaker 2>for logistics across a whole city.

68
00:03:23.479 --> 00:03:26.360
<v Speaker 1>So it's designed for efficiency even for tiny bits of

69
00:03:26.439 --> 00:03:28.120
<v Speaker 1>data from loads of devices.

70
00:03:28.240 --> 00:03:32.159
<v Speaker 2>Yes, exactly, efficiency for low power devices sending small bursts.

71
00:03:32.240 --> 00:03:34.879
<v Speaker 1>So yeah, definitely, not just faster phones. That market projection

72
00:03:34.960 --> 00:03:36.319
<v Speaker 1>you mentioned, it really puts.

73
00:03:36.080 --> 00:03:38.599
<v Speaker 2>The scale into perspective, doesn't it. From around five point

74
00:03:38.639 --> 00:03:40.599
<v Speaker 2>five billion dollars in twenty twenty.

75
00:03:40.400 --> 00:03:42.919
<v Speaker 1>To it projected what was it, six hundred and sixty

76
00:03:42.919 --> 00:03:44.639
<v Speaker 1>seven billion dollars by twenty twenty.

77
00:03:44.439 --> 00:03:47.599
<v Speaker 2>Six, six hundred and sixty seven point nine zero billion dollars.

78
00:03:47.639 --> 00:03:48.800
<v Speaker 2>It's an exponential leap.

79
00:03:48.960 --> 00:03:51.439
<v Speaker 1>That's massive. I like your analogy. Four G was like

80
00:03:51.479 --> 00:03:54.240
<v Speaker 1>building faster highways for everyone, but five G is like

81
00:03:54.240 --> 00:03:57.120
<v Speaker 1>building a whole new smart city. The traffic flowsn't just faster,

82
00:03:57.199 --> 00:03:59.840
<v Speaker 1>it's dynamically changed, purpose built.

83
00:03:59.639 --> 00:04:03.680
<v Speaker 2>Right dedicated lanes for critical data, maybe slower efficient routes

84
00:04:03.680 --> 00:04:06.719
<v Speaker 2>for IoT, super fast lanes for your browsing.

85
00:04:07.039 --> 00:04:09.919
<v Speaker 1>It's reimagining the whole city plan for data, not just

86
00:04:09.960 --> 00:04:10.680
<v Speaker 1>an upgrade.

87
00:04:10.800 --> 00:04:12.919
<v Speaker 2>That's a great way to put it, because what truly

88
00:04:12.960 --> 00:04:16.680
<v Speaker 2>defines this leap beyond those capabilities is how the network

89
00:04:16.720 --> 00:04:21.040
<v Speaker 2>is built fundamentally, Unlike four G which used let's say

90
00:04:21.439 --> 00:04:25.399
<v Speaker 2>more traditional tightly coupled telecom protocols.

91
00:04:24.959 --> 00:04:27.560
<v Speaker 1>Right, things like GTP and diameter exactly.

92
00:04:27.639 --> 00:04:30.959
<v Speaker 2>Five G takes this huge leap, drawing inspiration from modern

93
00:04:31.000 --> 00:04:32.959
<v Speaker 2>cloud computing web services.

94
00:04:33.120 --> 00:04:36.199
<v Speaker 1>Ah okay, and that changes things operational frownly.

95
00:04:36.600 --> 00:04:40.759
<v Speaker 2>The five G core embraces a service based architecture SBA

96
00:04:40.920 --> 00:04:41.959
<v Speaker 2>service based architecture.

97
00:04:42.360 --> 00:04:45.560
<v Speaker 1>So instead of these rigid monolithic blocks with fixed.

98
00:04:45.240 --> 00:04:48.000
<v Speaker 2>Connections like big single purpose machines.

99
00:04:47.800 --> 00:04:51.839
<v Speaker 1>Sort of yeah, Now, network functionality comes from discrete independent

100
00:04:51.920 --> 00:04:57.040
<v Speaker 1>network functions and fs. These nfs act like individual micro services. Really,

101
00:04:57.439 --> 00:05:02.079
<v Speaker 1>they provide capabilities to other authorized nis through open APIs.

102
00:05:01.759 --> 00:05:05.399
<v Speaker 2>API's application programming interfaces like how websites talk to each other,

103
00:05:05.560 --> 00:05:10.720
<v Speaker 2>very similar concept. It fundamentally changes the design distributed applications

104
00:05:10.839 --> 00:05:13.519
<v Speaker 2>much more agile, modular, resilient.

105
00:05:13.240 --> 00:05:14.759
<v Speaker 1>And the core principle making this work.

106
00:05:14.839 --> 00:05:18.279
<v Speaker 2>It's the widespread use of REST representational state transfer, that

107
00:05:18.439 --> 00:05:21.240
<v Speaker 2>architectural style, along with HTTP two methods for.

108
00:05:21.160 --> 00:05:23.959
<v Speaker 1>Communication REST and HTTP two. Okay.

109
00:05:24.040 --> 00:05:28.759
<v Speaker 2>This shift from hardware centric to this flexible software defined

110
00:05:29.279 --> 00:05:33.279
<v Speaker 2>service based model, that's what delivers the flexibility, the stalability,

111
00:05:33.319 --> 00:05:35.160
<v Speaker 2>the modularity five G promises.

112
00:05:35.240 --> 00:05:39.079
<v Speaker 1>So it allows for faster innovation too. Because functions are independent.

113
00:05:38.680 --> 00:05:42.800
<v Speaker 2>Precisely, you can develop, deploy, update them independently without breaking

114
00:05:42.879 --> 00:05:43.600
<v Speaker 2>the whole network.

115
00:05:43.720 --> 00:05:46.439
<v Speaker 1>So back to that factory analogy. Four G was a

116
00:05:46.439 --> 00:05:50.480
<v Speaker 1>few big specialized machines. Updating one was a huge deal, right, slow.

117
00:05:50.279 --> 00:05:53.000
<v Speaker 2>Complex could shut down half the factory potentially, But.

118
00:05:53.000 --> 00:05:57.879
<v Speaker 1>Five GSBA is more like lots of small, interconnected robots, interchangeable,

119
00:05:58.199 --> 00:06:00.759
<v Speaker 1>each doing specific tasks, talking openly.

120
00:06:00.879 --> 00:06:03.319
<v Speaker 2>That's a good picture, and it's not just faster development.

121
00:06:03.439 --> 00:06:04.279
<v Speaker 2>Think resilience.

122
00:06:04.480 --> 00:06:08.600
<v Speaker 1>Ah right, If one robot function fails.

123
00:06:08.560 --> 00:06:12.519
<v Speaker 2>Its services can be dynamically rerouted to another instance much

124
00:06:12.560 --> 00:06:15.519
<v Speaker 2>better uptime, especially for critical stuff compared to the more

125
00:06:15.560 --> 00:06:16.879
<v Speaker 2>brittle four G systems.

126
00:06:16.920 --> 00:06:19.160
<v Speaker 1>That stability is a huge deal, and.

127
00:06:19.040 --> 00:06:23.160
<v Speaker 2>That resilience comes directly from key rest principles. They seem simple,

128
00:06:23.199 --> 00:06:27.639
<v Speaker 2>but they're powerful. Like client server totally separates concerns. Clients

129
00:06:27.680 --> 00:06:30.079
<v Speaker 2>request servers provide.

130
00:06:29.639 --> 00:06:32.680
<v Speaker 1>So one NF asks for a service, another provides it.

131
00:06:32.720 --> 00:06:36.240
<v Speaker 2>Yep, and they can evolve independently update the server NF

132
00:06:36.279 --> 00:06:39.279
<v Speaker 2>without needing to update every client ENF that uses.

133
00:06:39.000 --> 00:06:43.000
<v Speaker 1>It makes sense and statelessness statelessness hmmm crucial.

134
00:06:43.839 --> 00:06:46.800
<v Speaker 2>Each request has all the info needed the server doesn't

135
00:06:46.800 --> 00:06:49.800
<v Speaker 2>need to remember past interactions or session state, like a.

136
00:06:49.720 --> 00:06:52.600
<v Speaker 1>Web server, not needing to track every user's session details

137
00:06:52.600 --> 00:06:53.759
<v Speaker 1>constantly exactly.

138
00:06:53.879 --> 00:06:57.560
<v Speaker 2>That massively improved scalability makes it easier to distribute the

139
00:06:57.600 --> 00:06:58.399
<v Speaker 2>load more.

140
00:06:58.319 --> 00:07:01.399
<v Speaker 1>Robust Okay, and cacheability.

141
00:07:01.879 --> 00:07:05.040
<v Speaker 2>Responses can be marked as cacheable. Clients can store and

142
00:07:05.160 --> 00:07:06.759
<v Speaker 2>reuse that data.

143
00:07:06.399 --> 00:07:10.639
<v Speaker 1>Reducing requests. Boosting efficiency like cacheing common subscription data Closer.

144
00:07:10.360 --> 00:07:13.800
<v Speaker 2>Perfect example, speeds things up, reduces load on the core.

145
00:07:13.920 --> 00:07:15.199
<v Speaker 1>NF said the layered system.

146
00:07:15.480 --> 00:07:18.600
<v Speaker 2>Layered system clients don't need to know what happens beyond

147
00:07:18.639 --> 00:07:21.920
<v Speaker 2>the server they talk to. So say the SMF needs

148
00:07:22.000 --> 00:07:25.480
<v Speaker 2>user data, it asks the UDM. The UDM might then

149
00:07:25.560 --> 00:07:27.040
<v Speaker 2>talk to the UDR to get.

150
00:07:26.839 --> 00:07:29.480
<v Speaker 1>It, but the SMF doesn't care how the UDM does

151
00:07:29.519 --> 00:07:31.000
<v Speaker 1>its job internally exactly.

152
00:07:31.040 --> 00:07:34.879
<v Speaker 2>It simplifies the architecture improved security too. Nfs only need

153
00:07:34.920 --> 00:07:36.839
<v Speaker 2>to know their immediate neighbors got it.

154
00:07:36.959 --> 00:07:38.319
<v Speaker 1>And the uniform interface.

155
00:07:38.560 --> 00:07:43.319
<v Speaker 2>Uniform interface standardized methods get for retrieving, put for replacing,

156
00:07:43.480 --> 00:07:47.920
<v Speaker 2>put for creating patch for partial updates delete. The standard

157
00:07:47.959 --> 00:07:51.519
<v Speaker 2>web verbs pretty much makes communication predictable, easy to implement.

158
00:07:51.639 --> 00:07:54.120
<v Speaker 2>New functions can plug in seamlessly.

159
00:07:53.879 --> 00:07:57.240
<v Speaker 1>So this isn't just theory. It means a network that's agile, robust,

160
00:07:57.279 --> 00:08:00.360
<v Speaker 1>evolves quickly, handles diverse needs, recovers better.

161
00:08:00.439 --> 00:08:03.160
<v Speaker 2>It's the engine for those dynamic five G services for you,

162
00:08:03.480 --> 00:08:04.240
<v Speaker 2>the end user.

163
00:08:04.399 --> 00:08:07.600
<v Speaker 1>Okay, so with this SBA blueprint, let's meet some of

164
00:08:07.600 --> 00:08:10.439
<v Speaker 1>these key players. The network functions these robots.

165
00:08:10.680 --> 00:08:13.600
<v Speaker 2>Sounds good, And in five G there's a really clear

166
00:08:13.639 --> 00:08:16.759
<v Speaker 2>separation of concerns, much more so than in four G. First,

167
00:08:16.920 --> 00:08:19.639
<v Speaker 2>the Access and Mobility Function AMF.

168
00:08:19.240 --> 00:08:20.920
<v Speaker 1>The gatekeeper and passport control.

169
00:08:21.160 --> 00:08:24.279
<v Speaker 2>Good analogy. It's comparable to the MME and four G,

170
00:08:24.439 --> 00:08:30.279
<v Speaker 2>but more focused access and mobility management, registering users, managing connections,

171
00:08:30.399 --> 00:08:32.600
<v Speaker 2>knowing where devices are, and handling identity.

172
00:08:32.639 --> 00:08:34.399
<v Speaker 1>You mentioned SUPI right.

173
00:08:34.279 --> 00:08:38.200
<v Speaker 2>It handles your subscription permanent identifier SUPI. That's your unique

174
00:08:38.200 --> 00:08:42.399
<v Speaker 2>permanent ID. But crucially for security over the air, the

175
00:08:42.440 --> 00:08:47.200
<v Speaker 2>AMF assigns a temporary ID, the five G globally unique

176
00:08:47.360 --> 00:08:49.039
<v Speaker 2>Temporary Identifier five.

177
00:08:48.840 --> 00:08:51.320
<v Speaker 1>GGUTI, and that changes frequently.

178
00:08:51.080 --> 00:08:55.080
<v Speaker 2>Yep to keep your permanent SUPI private. A big security improvement.

179
00:08:55.200 --> 00:09:00.000
<v Speaker 1>Okay. AMF panels access, mobility, temporary ID. What about data sessions?

180
00:09:00.039 --> 00:09:03.440
<v Speaker 2>That's the session management function SMF Somewhat like the PGW

181
00:09:03.519 --> 00:09:07.279
<v Speaker 2>and four G, but again specialized. SMF is all about PDU.

182
00:09:06.960 --> 00:09:10.039
<v Speaker 1>Session PDU sessions like private data.

183
00:09:09.840 --> 00:09:13.200
<v Speaker 2>Tunnels, exactly your dedicated tunnel through the five G network.

184
00:09:13.320 --> 00:09:15.399
<v Speaker 2>When your phone connects to the Internet or an app.

185
00:09:15.480 --> 00:09:18.159
<v Speaker 2>The SMF sets up this tunnel, assigns your IP address,

186
00:09:18.399 --> 00:09:20.960
<v Speaker 2>manages how data flows, interacts with policy.

187
00:09:20.559 --> 00:09:22.919
<v Speaker 1>And charging, so it orchestrates the connection based on your

188
00:09:22.960 --> 00:09:23.759
<v Speaker 1>needs and plan.

189
00:09:23.919 --> 00:09:25.559
<v Speaker 2>Precisely, it tailors that connection.

190
00:09:25.799 --> 00:09:30.240
<v Speaker 1>Okay, AMF for access SMF for session orchestration. Who handles

191
00:09:30.279 --> 00:09:31.519
<v Speaker 1>the actual data movement?

192
00:09:31.600 --> 00:09:34.279
<v Speaker 2>That would be the user plane function UPF. This one's

193
00:09:34.320 --> 00:09:37.440
<v Speaker 2>critical along with the GNB the five GU radio base station.

194
00:09:37.559 --> 00:09:39.759
<v Speaker 2>The UPF is the only data plane node in the

195
00:09:39.799 --> 00:09:41.200
<v Speaker 2>five G core architecture.

196
00:09:41.320 --> 00:09:44.559
<v Speaker 1>Only data plane node. Everything else is control plane AMF

197
00:09:44.799 --> 00:09:45.879
<v Speaker 1>SMF correct.

198
00:09:46.120 --> 00:09:49.000
<v Speaker 2>They manage the network. The UPF moves the data. It's

199
00:09:49.039 --> 00:09:52.480
<v Speaker 2>the workhorse. It acts as the anchor point for mobility routes.

200
00:09:52.519 --> 00:09:54.440
<v Speaker 2>Your packets, can do deep packet.

201
00:09:54.120 --> 00:09:56.759
<v Speaker 1>Inspection for application detection yes, and.

202
00:09:56.840 --> 00:10:00.000
<v Speaker 2>Enforces quality of service making sure your video gets the bandwidth.

203
00:10:00.320 --> 00:10:02.600
<v Speaker 2>It also reports usage for billing.

204
00:10:02.480 --> 00:10:07.279
<v Speaker 1>So quick recap AMF. Where are you securely SMF? What

205
00:10:07.399 --> 00:10:11.840
<v Speaker 1>session you need, how it's managed upf handles the actual dataflow.

206
00:10:11.480 --> 00:10:14.639
<v Speaker 2>You got it? That clear separation emphasizes the modularity.

207
00:10:14.799 --> 00:10:18.240
<v Speaker 1>And this modularity, this division of labor, that's what unlocks

208
00:10:18.279 --> 00:10:20.320
<v Speaker 1>those really customized experiences.

209
00:10:19.840 --> 00:10:24.080
<v Speaker 2>Right absolutely, which brings us straight to two really groundbreaking concepts,

210
00:10:24.240 --> 00:10:26.480
<v Speaker 2>network slicing and MAC.

211
00:10:26.360 --> 00:10:28.399
<v Speaker 1>Right multi access edge computing.

212
00:10:28.600 --> 00:10:32.039
<v Speaker 2>Indeed, these aren't just buzzwords, they are fundamental game changers.

213
00:10:32.279 --> 00:10:33.360
<v Speaker 1>Let's start with slicing.

214
00:10:33.480 --> 00:10:37.120
<v Speaker 2>Network slicing. Okay, this is genuinely new in five g

215
00:10:37.480 --> 00:10:42.120
<v Speaker 2>imagine taking the single physical network infrastructure.

216
00:10:41.480 --> 00:10:44.039
<v Speaker 1>Towers, fiber, data centers, everything.

217
00:10:43.679 --> 00:10:48.480
<v Speaker 2>And partitioning it into multiple virtual, independent networks slices. Each

218
00:10:48.559 --> 00:10:52.679
<v Speaker 2>slice is then designed, configured, optimized for a specific application, service,

219
00:10:52.759 --> 00:10:53.840
<v Speaker 2>or customer.

220
00:10:53.480 --> 00:10:55.799
<v Speaker 1>A huge departure from the old one size fits.

221
00:10:55.559 --> 00:10:58.399
<v Speaker 2>All network totally And why is it so powerful? Well,

222
00:10:58.440 --> 00:11:00.960
<v Speaker 2>you can have one slice just for or massive IoT

223
00:11:01.639 --> 00:11:06.240
<v Speaker 2>optimize for efficiency millions of sensors simultaneously. Another slice provides

224
00:11:06.240 --> 00:11:08.320
<v Speaker 2>that ultra that's a great way to visualize it.

225
00:11:08.399 --> 00:11:13.600
<v Speaker 1>But running multiple specialized kitchens that sounds complex Operationally, How

226
00:11:13.600 --> 00:11:16.600
<v Speaker 1>do operators manage these slices effectively? Be sure they don't

227
00:11:16.639 --> 00:11:18.480
<v Speaker 1>interfere maintain those slas.

228
00:11:18.679 --> 00:11:21.679
<v Speaker 2>That is a critical point. The orchestration layer is key

229
00:11:21.960 --> 00:11:25.879
<v Speaker 2>automating the creation, deployment, life cycle management of slices. That's

230
00:11:25.879 --> 00:11:27.799
<v Speaker 2>where a lot of the challenge in innovation lies.

231
00:11:27.840 --> 00:11:30.399
<v Speaker 1>So it's not just set up its dynamic.

232
00:11:30.000 --> 00:11:36.639
<v Speaker 2>Management, dynamic real time resource allocation monitoring. Preventing one slice

233
00:11:36.759 --> 00:11:41.200
<v Speaker 2>from impacting another critical one needs sophisticated tools, maybe AI

234
00:11:41.799 --> 00:11:43.519
<v Speaker 2>to predict demand and adjust.

235
00:11:43.639 --> 00:11:48.279
<v Speaker 1>Okay, that makes sense now MAC Multi access Edge computing MEC.

236
00:11:48.519 --> 00:11:51.440
<v Speaker 2>This is about bringing computation and hosting closer.

237
00:11:51.200 --> 00:11:53.639
<v Speaker 1>To the action, closer to the user or device exactly.

238
00:11:53.679 --> 00:11:56.879
<v Speaker 2>Instead of sending all data to some distant centralized cloud

239
00:11:56.960 --> 00:12:00.440
<v Speaker 2>data center, MEC lets, applications and even parts of the

240
00:12:00.480 --> 00:12:03.159
<v Speaker 2>user plane like the UPF we discussed, be hosted at

241
00:12:03.200 --> 00:12:04.240
<v Speaker 2>the edge of the network.

242
00:12:04.480 --> 00:12:06.399
<v Speaker 1>So benefits our mainly lower latency.

243
00:12:06.600 --> 00:12:09.960
<v Speaker 2>That's a huge one. Reduced latency is vital for real

244
00:12:10.000 --> 00:12:14.240
<v Speaker 2>time things like autonomous riding or milliseconds count, but also

245
00:12:14.440 --> 00:12:18.440
<v Speaker 2>better responsiveness for local services think AR in a stadium

246
00:12:18.840 --> 00:12:20.639
<v Speaker 2>or real time sensor processing in.

247
00:12:20.639 --> 00:12:24.639
<v Speaker 1>A factory, and deploying upfs at the edge helps steer

248
00:12:24.679 --> 00:12:27.559
<v Speaker 1>traffic locally avoid sending it all the way back to

249
00:12:27.600 --> 00:12:28.080
<v Speaker 1>the main.

250
00:12:27.919 --> 00:12:32.879
<v Speaker 2>Core precisely, dynamic traffic steering to local application servers, saves time,

251
00:12:33.000 --> 00:12:35.000
<v Speaker 2>saves bandwidth, it's much more efficient.

252
00:12:35.279 --> 00:12:37.679
<v Speaker 1>So yeah, it's not just a generic pipe anymore. It's

253
00:12:37.720 --> 00:12:43.039
<v Speaker 1>this dynamic, on demand, customized platform tailored for almost any application,

254
00:12:43.480 --> 00:12:45.360
<v Speaker 1>enabling new business models.

255
00:12:45.120 --> 00:12:47.519
<v Speaker 2>A network that adapts to your needs, not the other

256
00:12:47.559 --> 00:12:48.120
<v Speaker 2>way around.

257
00:12:48.320 --> 00:12:50.879
<v Speaker 1>That is a big vision. And obviously building this new

258
00:12:50.879 --> 00:12:52.919
<v Speaker 1>five G core is an instant. It's a journey, right,

259
00:12:52.919 --> 00:12:56.120
<v Speaker 1>a migration. The source mentions different ways operators are handling

260
00:12:56.120 --> 00:12:57.320
<v Speaker 1>this transition from four G.

261
00:12:57.559 --> 00:13:00.200
<v Speaker 2>That's right. It's a massive undertaking the ancient. It came

262
00:13:00.279 --> 00:13:03.279
<v Speaker 2>up with two main approaches, five G non standalone NSA

263
00:13:03.480 --> 00:13:05.360
<v Speaker 2>and five G standalone.

264
00:13:04.879 --> 00:13:06.519
<v Speaker 1>Say and an essay is usually the first step.

265
00:13:06.639 --> 00:13:11.000
<v Speaker 2>Often, yes, it's pragmatic. It lets operators leverage their existing

266
00:13:11.039 --> 00:13:14.960
<v Speaker 2>four G LTE infrastructure, both the radio network the RAN

267
00:13:15.320 --> 00:13:18.960
<v Speaker 2>and the core network the EPC. In NSA, the four

268
00:13:19.000 --> 00:13:22.840
<v Speaker 2>G core, the EPC still acts as the anchor for control, functions,

269
00:13:22.919 --> 00:13:24.399
<v Speaker 2>mobility of sessions.

270
00:13:24.440 --> 00:13:27.120
<v Speaker 1>But the new five G radio handles the data mostly.

271
00:13:27.200 --> 00:13:31.039
<v Speaker 2>Yes, new radio NR gets integrated for the data plane.

272
00:13:31.080 --> 00:13:34.039
<v Speaker 2>It's basically upgrading the radio without immediately ripping out the

273
00:13:34.159 --> 00:13:34.759
<v Speaker 2>entire core.

274
00:13:35.080 --> 00:13:37.519
<v Speaker 1>So like putting that faster engine in the old car frame,

275
00:13:38.039 --> 00:13:40.000
<v Speaker 1>you g have speed, but still rely on the older

276
00:13:40.080 --> 00:13:40.720
<v Speaker 1>chassis for something.

277
00:13:40.879 --> 00:13:42.360
<v Speaker 2>That's a good way to think about it. It gets five

278
00:13:42.399 --> 00:13:43.399
<v Speaker 2>G services out.

279
00:13:43.279 --> 00:13:46.320
<v Speaker 1>Faster, But what are the downsides then, of relying on

280
00:13:46.360 --> 00:13:50.120
<v Speaker 1>that older four G core even temporarily? Does it limit

281
00:13:50.200 --> 00:13:52.080
<v Speaker 1>the real five G potential? It does?

282
00:13:52.159 --> 00:13:55.799
<v Speaker 2>That's the tradeoff. NSA accelerates deployment, lets you reuse assets,

283
00:13:55.840 --> 00:13:59.279
<v Speaker 2>boosts broadband capacity quickly, but it can't fully deliver on

284
00:13:59.320 --> 00:14:03.440
<v Speaker 2>all advanced features. True end to end network slicing limited

285
00:14:03.519 --> 00:14:05.720
<v Speaker 2>because the four G core doesn't natively support it like

286
00:14:05.720 --> 00:14:06.559
<v Speaker 2>the five G core does.

287
00:14:06.600 --> 00:14:08.360
<v Speaker 1>An ultralow latency also.

288
00:14:08.240 --> 00:14:11.240
<v Speaker 2>Constrained by the older corese capabilities, so NSA is a

289
00:14:11.240 --> 00:14:14.759
<v Speaker 2>powerful stepping stone, but not the final destination for the

290
00:14:14.799 --> 00:14:19.039
<v Speaker 2>full vision. A popular deployment option mention is option three

291
00:14:19.240 --> 00:14:22.320
<v Speaker 2>X oution three x YEAH, where the four GenB based

292
00:14:22.320 --> 00:14:25.080
<v Speaker 2>station acts as the master node and the five GGNB

293
00:14:25.279 --> 00:14:28.120
<v Speaker 2>is the secondary. They team up. They can even split

294
00:14:28.159 --> 00:14:30.639
<v Speaker 2>your data traffic between four G and five G paths

295
00:14:30.919 --> 00:14:35.159
<v Speaker 2>using a link called the XN interface, maximizes speed during transition.

296
00:14:35.440 --> 00:14:38.240
<v Speaker 1>Interesting. Okay, So NSA is the stepping stone. What's ssay?

297
00:14:38.440 --> 00:14:42.120
<v Speaker 2>Five GSA is the full vision stand alone, a completely

298
00:14:42.120 --> 00:14:45.759
<v Speaker 2>independent five G core network detached from four G infrastructure.

299
00:14:45.840 --> 00:14:50.000
<v Speaker 1>This is where all the advanced stuff happens. Slicing URLLC massive.

300
00:14:49.679 --> 00:14:53.240
<v Speaker 2>IoT fully realize. Yes, this is the ultimate goal. Enables

301
00:14:53.279 --> 00:14:55.799
<v Speaker 2>the whole spectrum of new applications, but it requires that

302
00:14:55.840 --> 00:14:57.960
<v Speaker 2>complete overhaul, significant investments.

303
00:14:58.000 --> 00:15:00.679
<v Speaker 1>So the typical path is four G then NSA like

304
00:15:00.720 --> 00:15:03.039
<v Speaker 1>option three x, and finally to ESSAY option two.

305
00:15:03.279 --> 00:15:06.639
<v Speaker 2>That's the common migration path described FORG option one to NSA,

306
00:15:06.679 --> 00:15:09.519
<v Speaker 2>Option three X, then to ESSAY option two. NSA is

307
00:15:09.600 --> 00:15:13.080
<v Speaker 2>vital for that initial rapid rollout, especially for boosting mobile broadband.

308
00:15:13.279 --> 00:15:15.639
<v Speaker 2>But ESSAY is the complete transformative evolution.

309
00:15:15.960 --> 00:15:19.080
<v Speaker 1>Wow, okay, that was quite a journey through the core.

310
00:15:19.759 --> 00:15:22.039
<v Speaker 1>It's really clear five G is so much more than

311
00:15:22.120 --> 00:15:26.600
<v Speaker 1>just speed. It's this fundamental rethink of network.

312
00:15:26.240 --> 00:15:29.399
<v Speaker 2>Building, absolutely far beyond what many people might initially think.

313
00:15:29.440 --> 00:15:33.279
<v Speaker 1>We acknowledged the hype, but we went way beyond, just faster.

314
00:15:33.600 --> 00:15:36.159
<v Speaker 1>We saw this re architected network, the service based.

315
00:15:36.039 --> 00:15:42.320
<v Speaker 2>Architecture modular flexible using open APIs like rest mirroring cloud principles,

316
00:15:42.559 --> 00:15:44.399
<v Speaker 2>more resilient, more agile.

317
00:15:44.519 --> 00:15:48.840
<v Speaker 1>We met the key players AMF, SMF, UPF, each with

318
00:15:48.919 --> 00:15:52.759
<v Speaker 1>clear roles from secure tracking to actually moving the data packets,

319
00:15:53.320 --> 00:15:56.720
<v Speaker 1>and we explored those huge capabilities like network slicing, dedicated

320
00:15:56.759 --> 00:16:00.639
<v Speaker 1>virtual networks, and MAC bringing computing close for low.

321
00:16:00.600 --> 00:16:04.000
<v Speaker 2>Latency, fundamentally changing how data is processed and delivered.

322
00:16:04.039 --> 00:16:07.240
<v Speaker 1>And we understood that strategic journey operators are on from

323
00:16:07.360 --> 00:16:10.320
<v Speaker 1>NSA leveraging four G to the full power.

324
00:16:10.039 --> 00:16:13.440
<v Speaker 2>Of essay, balancing those immediate benefits with the long term potential.

325
00:16:13.480 --> 00:16:14.679
<v Speaker 2>It's a big strategic play.

326
00:16:14.759 --> 00:16:17.279
<v Speaker 1>So the takeaway really is five G isn't just an upgrade,

327
00:16:17.279 --> 00:16:19.080
<v Speaker 1>it's a foundational redesign.

328
00:16:18.840 --> 00:16:21.519
<v Speaker 2>A shift from one size fits all to this highly

329
00:16:21.559 --> 00:16:27.879
<v Speaker 2>customizable on demand platform delivering tailored services. That adaptability is unprecedented.

330
00:16:28.159 --> 00:16:32.039
<v Speaker 1>So thinking about these shifts, it's not just how we connect,

331
00:16:32.080 --> 00:16:36.840
<v Speaker 1>but what's possible for industries, for daily life, maybe in

332
00:16:36.840 --> 00:16:37.639
<v Speaker 1>ways we haven't even.

333
00:16:37.559 --> 00:16:39.919
<v Speaker 2>Imagined yet definitely opens up new possibilities.

334
00:16:40.039 --> 00:16:43.799
<v Speaker 1>So here's something them all over what complex problems things

335
00:16:43.840 --> 00:16:46.720
<v Speaker 1>may be previously unsolvable. Do you think we'll finally find

336
00:16:46.759 --> 00:16:51.120
<v Speaker 1>solutions with this dynamic on demand five G network? Thanks

337
00:16:51.120 --> 00:16:53.360
<v Speaker 1>for diving deep with us today my pleasure. We really

338
00:16:53.399 --> 00:16:56.559
<v Speaker 1>hope this exploration gave you a fresh perspective, a shortcut

339
00:16:56.559 --> 00:16:59.519
<v Speaker 1>to being genuinely informed about the amazing engineering behind five G.

340
00:17:00.120 --> 00:17:00.879
<v Speaker 1>Until next time,