-
Notifications
You must be signed in to change notification settings - Fork 2
/
etri2024.html
728 lines (672 loc) · 24.3 KB
/
etri2024.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Open5GS – Status</title>
<meta name="description" content="A framework for easily creating beautiful presentations using HTML">
<meta name="author" content="Hakim El Hattab">
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="stylesheet" href="dist/reset.css">
<link rel="stylesheet" href="dist/reveal.css">
<link rel="stylesheet" href="dist/theme/black.css" id="theme">
<!-- Theme used for syntax highlighting of code -->
<link rel="stylesheet" href="plugin/highlight/monokai.css">
<style>
.reveal h1, .reveal h2, .reveal h3, .reveal h4, .reveal h5 {
text-transform: none;
}
</style>
</head>
<body>
<div class="reveal">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section>
<h2>
<a href="https://open5gs.org" target="_blank">Open5GS</a> status: recent, current and future developments
</h2>
<p><small>Presentation link : <a href="https://open5gs.org/slides/etri2024" target="_blank">https://open5gs.org/slides/etri2024</a></small></p>
<p style="text-align: right;">Sukchan Lee</p>
</section>
<section style="text-align: left;">
<h2>Recent Developments</h2>
<ul>
<li>HTTP/2 over TLS</li>
<small>
Enhanced security and performance for control plane communications
</small>
<li>5G SUCI Profile A/B Scheme</li>
<small>
Enhanced subscriber privacy protection
</small>
<li>UPF High Availability</li>
<small>
SMF detects UPF failover using PFCP Heartbeats. Process of transferring PDU sessions to a new UPF for uninterrupted service
</small>
</ul>
</section>
<section style="text-align: left;">
<h2>
Metrics Support using Prometheus
</h2>
<p>
<small>
Introduction of a generic API for counters, gauges, etc.
</small>
</p>
<img height="400px" data-src="https://open5gs.org/assets/img/metrics.png" alt="Metrics">
</section>
<section style="text-align: left;">
<h2>
Framed Routing in 5G
</h2>
<p>
<small>
Framed Routing allows a range of IP addresses or prefixes to be reachable over a single PDU Session, supporting IP networks behind a UE for IPv4 and IPv6 sessions.
</small>
</p>
<p>
<small>
The Session Management Function (SMF) provides Framed Route information to the User Plane Function (UPF), and updates or releases PDU Sessions based on changes in Framed Route information from DN-AAA or UDM sources.
</small>
</p>
</section>
<section style="text-align: left;">
<h2>
Subscriber Database
</h2>
<ul>
<li>
192.168.21.0/24 being routed to the <b>internet</b> APN is as follows.
</li>
</ul>
<pre data-id="code-animation"><code class="hljs" data-trim data-line-numbers="6">
"imsi", ("999700000021309"),
...
"slice", "[", "{",
"session", "[", "{",
"name", ("internet"),
"ipv4_framed_routes", ("192.168.21.0/24"),
...
</code></pre>
</section>
<section style="text-align: left;">
<h2>
Overview of PFCP Restoration
</h2>
<p>
<small>
PFCP is a 3GPP protocol used in 5G core networks and 4G/LTE EPC to define the interactions between SMF and UPF or between SGW-C and SGW-U.
</small>
</p>
<p>
<small>
Across PFCP based interfaces, an SGW-C, SGW-U, SMF and UPF Node shall utilize PFCP Heartbeat Request and Heartbeat Response messages to detect and handle a peer PFCP entity failure or restart.
</small>
</p>
<p>
<ul>
<small>
<li>
TS23.007 LTE Restoration procedures
</li>
<li>
TS23.527 5G Restoration procedures
</li>
</small>
</ul>
</p>
</section>
<section style="text-align: left;">
<h2>
PFCP Restoration Method
</h2>
<p>
SMF/SGW-C Restoration Procedures
</p>
<p>
<small>
UPF/SGW-U shall delete all session contexts affected by the PFCP entity restart that it may have stored.
</small>
</p>
<p>
UPF/SGW-U Restoration Procedures
</p>
<p>
<small>
SMF/SGW-C shall include a restoration indication in the PFCP Session Establishment Request message to indicate to the UPF/SGW-U.
</small>
<p>
</section>
<section style="text-align: left;">
<h2>
What is SEPP?
</h2>
<p>
A network function in 5G architecture designed to secure information exchange between network operators for roaming.
</p>
</section>
<section style="text-align: left;">
<h2>
How Does 5G Roaming Work?
</h2>
<p>
<small>
Use of TLS (Transport Layer Security) for encryption and N32 interface for communication between SEPPs.
</small>
</p>
<img height="400px" data-src="https://open5gs.org/assets/img/roaming-lbo.png" alt="Roaming(LBO)">
</section>
<section style="text-align: left;">
<h2>
Design 5G Roaming
</h2>
<p>
TLS Certification and Interface Configuration:
<small>
Discussion on the security practice of using different TLS certificates for SBI and N32 interfaces, and the design consideration behind separating N32c and N32f interfaces for control and forwarding.
</small>
</p>
<p class="fragment fade-up">
Challenges:
<small>
Legacy configuration files (up to version 2.6.x) lack the flexibility and features needed to effectively design roaming settings.
</small>
<small>
Key requirements such as Transport Layer Security (TLS) and specific configurations like n32/n32f are difficult to implement.
</small>
</p>
</section>
<section style="text-align: left;">
<h2>New Configuration(Cont.)</h2>
<ul>
<li><a href="https://github.com/open5gs/open5gs/blob/main/configs/open5gs/mme.yaml.in" target="_blank">/etc/open5gs/mme.yaml</a></li>
</ul>
<pre data-id="code-animation"><code class="hljs" data-trim data-line-numbers="4-6|7-15|17-21|29-36">
mme:
freeDiameter: /home/acetcom/Documents/git/open5gs/install/etc/freeDiameter/mme.conf
s1ap:
- - addr: 127.0.0.2
+ server:
+ - address: 127.0.0.2
gtpc:
- - addr: 127.0.0.2
+ server:
+ - address: 127.0.0.2
+ client:
+ sgwc:
+ - address: 127.0.0.3
+ smf:
+ - address: 127.0.0.4
metrics:
- - addr: 127.0.0.2
- port: 9090
+ server:
+ - address: 127.0.0.2
+ port: 9090
gummei:
- plmn_id:
mcc: 999
@@ -25,16 +33,3 @@
full: Open5GS
short: Next
mme_name: open5gs-mme0
-sgwc:
- gtpc:
- - addr: 127.0.0.3
-smf:
- gtpc:
- - addr:
- - 127.0.0.4
- - ::1
</code></pre>
</section>
<section style="text-align: left;">
<h2>
New Configuration File Format
</h2>
<ul>
<li><a href="https://github.com/open5gs/open5gs/blob/main/configs/open5gs/amf.yaml.in" target="_blank">/etc/open5gs/amf.yaml</a></li>
</ul>
<pre data-id="code-animation"><code class="hljs" data-trim data-line-numbers="1-5|8-15|17-19|20-24">
-scp:
- sbi:
- - addr: 127.0.1.10
- port: 7777
-
amf:
sbi:
- - addr: 127.0.0.5
- port: 7777
+ server:
+ - address: 127.0.0.5
+ port: 7777
+ client:
+ scp:
+ - uri: http://127.0.0.200:7777
ngap:
- - addr: 127.0.0.5
+ server:
+ - address: 127.0.0.5
metrics:
- - addr: 127.0.0.5
- port: 9090
+ server:
+ - address: 127.0.0.5
+ port: 9090
</code></pre>
</section>
<section style="text-align: left;">
<h2>SEPP Configuration</h2>
<p>
<small>
Only N32 uses HTTPS with TLS, while other NFs use HTTP without TLS.
</small>
</p>
<pre data-id="code-animation"><code class="hljs" data-trim data-line-numbers="2-8|10-15|19|22-25|30|33">
sepp:
default:
tls:
server:
private_key: /etc/open5gs/tls/sepp1.key
cert: /etc/open5gs/tls/sepp1.crt
client:
cacert: /etc/open5gs/tls/ca.crt
sbi:
server:
- address: 127.0.1.250
port: 7777
client:
scp:
- uri: http://127.0.0.200:7777
n32:
server:
- sender: sepp1.localdomain
scheme: https
address: 127.0.1.251
port: 7777
n32f:
scheme: https
address: 127.0.1.252
port: 7777
client:
sepp:
- receiver: sepp2.localdomain
uri: https://sepp2.localdomain:7777
resolve: 127.0.2.251
n32f:
uri: https://sepp2.localdomain:7777
resolve: 127.0.2.252
</code></pre>
</section>
<section style="text-align: left;">
<h2>SEPP Configuration(Cont.)</h2>
<p>
<small>
N32 control and N32 forwarding interface use different key/certificate.
</small>
</p>
<pre data-id="code-animation"><code class="hljs" data-trim data-line-numbers="2-7|13-16|20-23|29-31|35-37">
sbi:
server:
- address: 127.0.1.250
port: 7777
client:
scp:
- uri: http://127.0.0.200:7777
n32:
server:
- sender: sepp1.localdomain
scheme: https
address: 127.0.1.251
private_key: /etc/open5gs/tls/sepp1.key
cert: /etc/open5gs/tls/sepp1.crt
verify_client: true
verify_client_cacert: /etc/open5gs/tls/ca.crt
n32f:
scheme: https
address: 127.0.1.252
private_key: /etc/open5gs/tls/sepp1-n32f.key
cert: /etc/open5gs/tls/sepp1-n32f.crt
verify_client: true
verify_client_cacert: /etc/open5gs/tls/ca.crt
client:
sepp:
- receiver: sepp2.localdomain
uri: https://sepp2.localdomain
resolve: 127.0.2.251
cacert: /etc/open5gs/tls/ca.crt
client_private_key: /etc/open5gs/tls/sepp1.key
client_cert: /etc/open5gs/tls/sepp1.crt
n32f:
uri: https://sepp2.localdomain
resolve: 127.0.2.252
cacert: /etc/open5gs/tls/ca.crt
client_private_key: /etc/open5gs/tls/sepp1-n32f.key
client_cert: /etc/open5gs/tls/sepp1-n32f.crt
</code></pre>
</section>
<section style="text-align: left;">
<h2>
NRF requires a PLMN-ID
</h2>
<p>
<small>
For 5G Roaming, the PLMN ID must be configured in the NRF as follows:
</small>
</p>
<ul>
<li><a href="https://github.com/open5gs/open5gs/blob/main/configs/open5gs/nrf.yaml.in" target="_blank">/etc/open5gs/nrf.yaml</a></li>
</ul>
<pre data-id="code-animation"><code class="hljs" data-trim data-line-numbers="3-5">
nrf:
serving: # 5G roaming requires PLMN in NRF
- plmn_id:
mcc: 999
mnc: 70
sbi:
server:
- address: 127.0.0.10
port: 7777
</code></pre>
</section>
<section style="text-align: left;">
<h2>
The configuration of FQDN in NFs
</h2>
<p>
<small>
During the registration phase, a Network Function (NF) receives PLMN-ID information from the NRF and configures its own Fully Qualified Domain Name (FQDN) accordingly.
</small>
</p>
<ul>
<li>/etc/hosts</li>
</ul>
<pre data-id="code-animation"><code class="hljs" data-trim data-line-numbers="1-3|5-7|9-11">
127.0.1.10 nrf.5gc.mnc070.mcc999.3gppnetwork.org
127.0.1.11 ausf.5gc.mnc070.mcc999.3gppnetwork.org
127.0.1.12 udm.5gc.mnc070.mcc999.3gppnetwork.org
127.0.2.10 nrf.5gc.mnc001.mcc001.3gppnetwork.org
127.0.2.11 ausf.5gc.mnc001.mcc001.3gppnetwork.org
127.0.2.12 udm.5gc.mnc001.mcc001.3gppnetwork.org
127.0.3.10 nrf.5gc.mnc010.mcc315.3gppnetwork.org
127.0.3.11 ausf.5gc.mnc010.mcc315.3gppnetwork.org
127.0.3.12 udm.5gc.mnc010.mcc315.3gppnetwork.org
</code></pre>
</section>
<section style="text-align: left;">
<h2>
Determining UE Roaming in NFs
</h2>
<ul>
<li>
AMF
</li>
</ul>
<p>
<small>
Due to the ability to accurately extract the PLMN-ID from the SUCI, it is easy to distinguish whether the connection is being made from the Home PLMN or a Visited PLMN.
</small>
</p>
<p style="text-align: center;">
<img style="text-align: center;" height="300px" data-src="https://open5gs.org/assets/img/suci.png" alt="SUCI">
</p>
</section>
<section style="text-align: left;">
<h2>
Determining UE Roaming(Cont.)
</h2>
<ul>
<li>
SMF
</li>
</ul>
<p>
<small>
The AMF transmits session information to the SMF for roaming UEs using the Full DNN method, leveraging FQDN information.
</small>
</p>
<p>
<small>
By comparing the SUPI with the Full DNN, the SMF determines whether the MNC is 2 or 3 bytes and identifies the accurate Home PLMN ID, allowing it to discern whether the UE is on the Home or Visited PLMN.
</small>
</p>
<pre data-id="code-animation"><code class="hljs" data-trim data-line-numbers="1-4|5-9">
Full DNN: internet.5gc.mnc070.mcc999.3gppnetwork.org
SUPI: imsi-999700000000001
IMSI: 999700000000001
PLMN-ID: MCC(999) MNC(70)
Full DNN: internet.5gc.mnc014.mcc310.3gppnetwork.org
SUPI: imsi-3100140000000001
IMSI: 3100140000000001
PLMN-ID: MCC(310) MNC(014)
</code></pre>
</section>
<section style="text-align: left;">
<h2>
The Risk of Full DNN:
</h2>
<p>
<small>
If an AMF from other vendor doesn't use Full DNN, it won't work right.
</small>
</p>
<pre data-id="code-animation"><code class="hljs" data-trim data-line-numbers="7-9|11|13-14">
TS29.502
6.1 Nsmf_PDUSession Service API
Table 6.1.6.2.2-1: Definition of type SmContextCreateData
NAME: dnn, Data type: Dnn
When present, it shall contain the requested DNN; the DNN
shall be the full DNN (i.e. with both the Network Identifier
and Operator Identifier) for a HR PDU session, and
it should be the full DNN in LBO and non-roaming scenarios.
If the Operator Identifier is absent,
the serving core network operator shall be assumed.
</code></pre>
</section>
<section style="text-align: left;">
<h2>5G Roaming</h2>
<p>
<small>
For insights and detailed information on 5G Roaming with Open5GS, the tutorial at <a href="https://open5gs.org/open5gs/docs/tutorial/05-roaming/" target="_blank">https://open5gs.org/open5gs/docs/tutorial/05-roaming/</a> serves as an excellent resource.
</small>
</p>
</section>
<section style="text-align: left;">
<h2>Open5GS in the Present</h2>
<p>
<small>
Working to fill in the gaps where functionality is limited or not yet fully implemented, as shown below.
</small>
</p>
<ul>
<li>Partial implementation of Roaming</li>
<li>No OCS/OFCS</li>
</ul>
</section>
<section style="text-align: left;">
<h2>Home Routed Roaming</h2>
<p>
<small>
While progress has been made in supporting LBO for roaming, the complete implementation for Home Routed roaming is pending.
</small>
</p>
<img height="400px" data-src="https://open5gs.org/assets/img/roaming-hb.png" alt="Roaming(Home-Routed)">
</section>
<section style="text-align: left;">
<h2>Gy Interface Development</h2>
<ul>
<li>
Collaboration with Osmocom is ongoing for Gy interface implementation
</li>
<li>
open5gs-smfd supports interacting to an OCS node through the Gy interface
</li>
<li>
Initial basic code for open5gs-ocsd is expected to be released soon - Issues <a href="https://github.com/open5gs/open5gs/issues/1492" target="_blank">#1492</a>
</li>
</ul>
</section>
<section style="text-align: left;">
<h2>open5gs-ocsd</h2>
<p>
<small>
It may make sense to introduce at least a minimal open5gs-ocsd in open5gs.git which announced the Credit Control diameter app support, and which can handle CCR Initial/Update/Termination answering with CCA.
</small>
</p>
<p>
<small>
It could also set Validity-Time and Volume-Threshold each time it is requested some resources, to get periodic reports about each subscriber, and perhaps store that into the mongodb database.
</small>
</p>
</section>
<section>
<h2>Future Work</h2>
<p>
I wonder if I should...
</p>
<p>
<small>
Moving Documentation and WebUI to separate repositories
</small>
</p>
</section>
<section>
<h2>Request from Community</h2>
<ul>
<li>MongoDB Alternative using YAML conf</li>
<li>CLI using Rest API</li>
<li>GTP-U Restoration</li>
<li>io_uring</li>
<li>osmo-gsm-shark with gsmtap</li>
</ul>
</section>
<section>
<h2>Request from Community(Cont.)</h2>
<ul>
<li>EAP-AKA-Prime</li>
<li>Add locality in the configuration</li>
<li>SUPI/GPSI Ranges in UDM - Issues <a href="https://github.com/open5gs/open5gs/issues/2010" target="_blank">#2010</a></li>
<li>UL Classifier - N9 interface between UPFs</li>
<li>NEF</li>
</ul>
</section>
<section>
<h2>Mesurement of UPF Performance</h2>
<table>
<thead>
<tr>
<th>UPF</th>
<th>TCP</th>
<th>UDP</th>
<th>Loss</th>
<th>RTT</th>
</tr>
</thead>
<tbody>
<tr>
<td>UPG-VPP</td>
<td>1162Mbps</td>
<td>458Mbps</td>
<td>0.96%</td>
<td>0.398ms</td>
</tr>
<tr>
<td>eUPF</td>
<td>358Mbps</td>
<td>418Mbps</td>
<td>3.6%</td>
<td>0.882ms</td>
</tr>
<tr>
<td>free5GC</td>
<td>231Mbps</td>
<td>401Mbps</td>
<td>23%</td>
<td>0.786ms</td>
</tr>
<tr>
<td>Open5GS</td>
<td>205Mbps</td>
<td>389Mbps</td>
<td>30%</td>
<td>1.081ms</td>
</tr>
</tbody>
</table>
</section>
<section>
<h2>UPF Comparison</h2>
<table>
<thead>
<tr>
<th>Kind</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="border:none;">eBPF/XDP</td>
<td style="border:none;">
Simply works on mainline linux
</td>
</tr>
<tr>
<td style="border:none;">DPDK/VPP</td>
<td style="border:none;">
A slightly higher performance than XDP
</td>
</tr>
<tr>
<td style="border:none;"></td>
<td style="border:none;">
NIC need to be dedicated to DPDK
</td>
</tr>
</tbody>
</table>
</section>
<section>
<h2>Open5GS UPF Improvements</h2>
<p>
Should Open5GS create its own UPF?
</p>
</section>
<section>
<h2>Harmonious Prioritization</h2>
<ul>
<li>Prioritizing bug fixes in the issue</li>
<li>Need to address security vulnerablilities</li>
<li>Hope to do a lot of new features</li>
</ul>
</section>
<section style="text-align: left;">
<h1>Thank you</h1>
<p>
Thank You for Your Attention!
</p>
</section>
</div>
</div>
<script src="dist/reveal.js"></script>
<script src="plugin/zoom/zoom.js"></script>
<script src="plugin/notes/notes.js"></script>
<script src="plugin/search/search.js"></script>
<script src="plugin/markdown/markdown.js"></script>
<script src="plugin/highlight/highlight.js"></script>
<script>
// Also available as an ES module, see:
// https://revealjs.com/initialization/
Reveal.initialize({
controls: true,
progress: true,
center: true,
hash: true,
// Learn about plugins: https://revealjs.com/plugins/
plugins: [ RevealZoom, RevealNotes, RevealSearch, RevealMarkdown, RevealHighlight ]
});
</script>
</body>
</html>