More than 1 year has passed since last update.

Open5GS 5GCとUERANSIM UE/RANでgNodeBの最寄りのUPFを選択する設定

Last updated at 2023-03-28Posted at 2022-03-11

本記事は、Open5GSとUERANSIMを使用して、UEが接続したgNodeBの最寄りのUPFを選択する場合の簡単な設定について説明します。これにより、UEからのトラフィックを最寄りの基地局のDNにルーティングしてMECを実現する際の設定のヒントになることを期待しています。
なお、5GCのコア網に登場する各NF(Network Function)の役割やインターフェースについて概ね知っていることを期待して書いており、これらの説明は省略します。

Open5GS 5GCのシミュレーション携帯網の概要

このシミュレーション環境は以下の条件を満たす最小構成になります。

gNodeBとUPFのペアは同じロケーションに存在します。
gNodeBに接続したUEは、同じロケーションにあるUPFによって管理されているDNに接続します。

構築したシミュレーション環境は以下の通りです。

5GCとUE/RANに使用しているOSSは以下の通りです。

5GC - Open5GS v2.4.7 - https://github.com/open5gs/open5gs
UE/RAN - UERANSIM v3.2.6 - https://github.com/aligungr/UERANSIM

各VMは以下の通りです。

VM#	SW & Role	IP address	OS	Memory (Min)	HDD (Min)
VM1	Open5GS 5GC C-Plane	192.168.0.111/24 192.168.0.112/24 192.168.0.113/24	Ubuntu 20.04	1GB	20GB
VM2	Open5GS 5GC U-Plane1	192.168.0.114/24	Ubuntu 20.04	1GB	20GB
VM3	Open5GS 5GC U-Plane2	192.168.0.115/24	Ubuntu 20.04	1GB	20GB
VM4	UERANSIM RAN (gNodeB1)	192.168.0.131/24	Ubuntu 20.04	1GB	10GB
VM5	UERANSIM RAN (gNodeB2)	192.168.0.132/24	Ubuntu 20.04	1GB	10GB
VM6	UERANSIM UE	192.168.0.133/24	Ubuntu 20.04	1GB	10GB

AMFとSMFのIPアドレスは以下の通りです。

NF	IP address	IP address on SBI	Supported TACs
AMF	192.168.0.111	127.0.0.5	1, 2
SMF1	192.168.0.112	127.0.0.4	1
SMF2	192.168.0.113	127.0.0.24	2

gNodeBの情報は以下の通りです。(その他の項目はデフォルト値)

gNodeB#	Location#	TAC#	IP address
gNodeB1	Loc1	1	192.168.0.131
gNodeB2	Loc2	2	192.168.0.132

加入者情報は以下の通りです。(その他の項目はデフォルト値)
注意。UERANSIMのUEの設定に合わせて、OPあるいはOPcを選択してください。

UE	IMSI	DNN	OP/OPc	gNodeB#
UE	001010000000000	internet	OPc	gNodeB1 in Loc1 gNodeB2 in Loc2

これらの情報の登録には、Open5GSが提供するWebUIを使用しました。なお、3GPP認証とキー生成機能(MILENAGE)の試験データとして、3GPP TS 35.208 "4.3 Test Sets"が公開されています。

各DNは以下の通りです。

DN	Location#	TUNnel interface of DN	DNN	TUNnel interface of UE	U-Plane#
10.45.0.0/16	Loc1	ogstun	internet	uesimtun0	U-Plane1
10.46.0.0/16	Loc2	ogstun	internet	uesimtun0	U-Plane2

Open5GS 5GCとUERANSIM UE/RANの設定ファイルの変更点

Open5GSとUERANSIMのビルド方法は以下を参照して下さい。

Open5GS v2.4.7 - https://open5gs.org/open5gs/docs/guide/02-building-open5gs-from-sources/
UERANSIM v3.2.6 - https://github.com/aligungr/UERANSIM/wiki/Installation

Open5GS 5GC C-Planeの設定ファイルの変更点

open5gs/install/etc/open5gs/amf.yaml

--- amf.yaml.orig       2022-06-06 14:09:42.000000000 +0900
+++ amf.yaml    2022-06-06 14:14:58.000000000 +0900
@@ -229,23 +229,23 @@
       - addr: 127.0.0.5
         port: 7777
     ngap:
-      - addr: 127.0.0.5
+      - addr: 192.168.0.111
     guami:
       - plmn_id:
-          mcc: 901
-          mnc: 70
+          mcc: 001
+          mnc: 01
         amf_id:
           region: 2
           set: 1
     tai:
       - plmn_id:
-          mcc: 901
-          mnc: 70
-        tac: 1
+          mcc: 001
+          mnc: 01
+        tac: [1, 2]
     plmn_support:
       - plmn_id:
-          mcc: 901
-          mnc: 70
+          mcc: 001
+          mnc: 01
         s_nssai:
           - sst: 1
     security:

open5gs/install/etc/open5gs/smf1.yaml

--- smf.yaml.orig       2022-06-06 14:09:42.000000000 +0900
+++ smf1.yaml   2022-06-06 14:18:48.000000000 +0900
@@ -381,17 +381,14 @@
       - addr: 127.0.0.4
         port: 7777
     pfcp:
-      - addr: 127.0.0.4
-      - addr: ::1
+      - addr: 192.168.0.112
     gtpc:
       - addr: 127.0.0.4
-      - addr: ::1
     gtpu:
-      - addr: 127.0.0.4
-      - addr: ::1
+      - addr: 192.168.0.112
     subnet:
       - addr: 10.45.0.1/16
-      - addr: 2001:db8:cafe::1/48
+        dnn: internet
     dns:
       - 8.8.8.8
       - 8.8.4.4
@@ -400,7 +397,17 @@
     mtu: 1400
     ctf:
       enabled: auto
-    freeDiameter: /root/open5gs/install/etc/freeDiameter/smf.conf
+    freeDiameter: /root/open5gs/install/etc/freeDiameter/smf1.conf
+    info:
+      - s_nssai:
+          - sst: 1
+            dnn:
+              - internet
+        tai:
+          - plmn_id:
+              mcc: 001
+              mnc: 01
+            tac: 1
 
 #
 # nrf:
@@ -501,7 +508,8 @@
 #
 upf:
     pfcp:
-      - addr: 127.0.0.7
+      - addr: 192.168.0.114
+        dnn: internet
 
 #
 # parameter:

open5gs/install/etc/open5gs/smf2.yaml

--- smf.yaml.orig       2022-06-06 14:09:42.000000000 +0900
+++ smf2.yaml   2022-06-06 14:21:56.000000000 +0900
@@ -378,20 +378,17 @@
 
 smf:
     sbi:
-      - addr: 127.0.0.4
+      - addr: 127.0.0.24
         port: 7777
     pfcp:
-      - addr: 127.0.0.4
-      - addr: ::1
+      - addr: 192.168.0.113
     gtpc:
-      - addr: 127.0.0.4
-      - addr: ::1
+      - addr: 127.0.0.24
     gtpu:
-      - addr: 127.0.0.4
-      - addr: ::1
+      - addr: 192.168.0.113
     subnet:
-      - addr: 10.45.0.1/16
-      - addr: 2001:db8:cafe::1/48
+      - addr: 10.46.0.1/16
+        dnn: internet
     dns:
       - 8.8.8.8
       - 8.8.4.4
@@ -400,7 +397,17 @@
     mtu: 1400
     ctf:
       enabled: auto
-    freeDiameter: /root/open5gs/install/etc/freeDiameter/smf.conf
+    freeDiameter: /root/open5gs/install/etc/freeDiameter/smf2.conf
+    info:
+      - s_nssai:
+          - sst: 1
+            dnn:
+              - internet
+        tai:
+          - plmn_id:
+              mcc: 001
+              mnc: 01
+            tac: 2
 
 #
 # nrf:
@@ -501,7 +508,8 @@
 #
 upf:
     pfcp:
-      - addr: 127.0.0.7
+      - addr: 192.168.0.115
+        dnn: internet
 
 #
 # parameter:

open5gs/install/etc/freeDiameter/smf1.conf

smf1.confは元のsmf.confと同じです。

open5gs/install/etc/freeDiameter/smf2.conf

--- smf.conf.orig       2021-08-09 14:06:48.000000000 +0000
+++ smf2.conf   2021-08-09 16:01:40.000000000 +0000
@@ -79,7 +79,7 @@
 #ListenOn = "202.249.37.5";
 #ListenOn = "2001:200:903:2::202:1";
 #ListenOn = "fe80::21c:5ff:fe98:7d62%eth0";
-ListenOn = "127.0.0.4";
+ListenOn = "127.0.0.24";
 
 
 ##############################################################

Open5GS 5GC U-Plane1の設定ファイルの変更点

open5gs/install/etc/open5gs/upf.yaml

--- upf.yaml.orig       2022-06-06 14:09:42.000000000 +0900
+++ upf.yaml    2022-06-06 14:29:06.000000000 +0900
@@ -166,12 +166,13 @@
 #
 upf:
     pfcp:
-      - addr: 127.0.0.7
+      - addr: 192.168.0.114
     gtpu:
-      - addr: 127.0.0.7
+      - addr: 192.168.0.114
     subnet:
       - addr: 10.45.0.1/16
-      - addr: 2001:db8:cafe::1/48
+        dnn: internet
+        dev: ogstun
 
 #
 # smf:

Open5GS 5GC U-Plane2の設定ファイルの変更点

open5gs/install/etc/open5gs/upf.yaml

--- upf.yaml.orig       2022-06-06 14:09:42.000000000 +0900
+++ upf.yaml    2022-06-06 14:32:46.000000000 +0900
@@ -166,12 +166,13 @@
 #
 upf:
     pfcp:
-      - addr: 127.0.0.7
+      - addr: 192.168.0.115
     gtpu:
-      - addr: 127.0.0.7
+      - addr: 192.168.0.115
     subnet:
-      - addr: 10.45.0.1/16
-      - addr: 2001:db8:cafe::1/48
+      - addr: 10.46.0.1/16
+        dnn: internet
+        dev: ogstun
 
 #
 # smf:

UERANSIM UE/RANの設定ファイルの変更点

RAN(gNodeB1)の設定ファイルの変更点

UERANSIM/config/open5gs-gnb.yaml

--- open5gs-gnb.yaml.orig       2021-04-19 21:30:50.000000000 +0000
+++ open5gs-gnb.yaml    2021-08-09 16:09:56.000000000 +0000
@@ -1,17 +1,17 @@
-mcc: '901'          # Mobile Country Code value
-mnc: '70'           # Mobile Network Code value (2 or 3 digits)
+mcc: '001'          # Mobile Country Code value
+mnc: '01'           # Mobile Network Code value (2 or 3 digits)
 
 nci: '0x000000010'  # NR Cell Identity (36-bit)
 idLength: 32        # NR gNB ID length in bits [22...32]
 tac: 1              # Tracking Area Code
 
-linkIp: 127.0.0.1   # gNB's local IP address for Radio Link Simulation (Usually same with local IP)
-ngapIp: 127.0.0.1   # gNB's local IP address for N2 Interface (Usually same with local IP)
-gtpIp: 127.0.0.1    # gNB's local IP address for N3 Interface (Usually same with local IP)
+linkIp: 192.168.0.131   # gNB's local IP address for Radio Link Simulation (Usually same with local IP)
+ngapIp: 192.168.0.131   # gNB's local IP address for N2 Interface (Usually same with local IP)
+gtpIp: 192.168.0.131    # gNB's local IP address for N3 Interface (Usually same with local IP)
 
 # List of AMF address information
 amfConfigs:
-  - address: 127.0.0.5
+  - address: 192.168.0.111
     port: 38412
 
 # List of supported S-NSSAIs by this gNB

RAN(gNodeB2)の設定ファイルの変更点

UERANSIM/config/open5gs-gnb.yaml

--- open5gs-gnb.yaml.orig       2021-04-19 21:30:50.000000000 +0000
+++ open5gs-gnb.yaml    2021-08-09 16:10:18.000000000 +0000
@@ -1,17 +1,17 @@
-mcc: '901'          # Mobile Country Code value
-mnc: '70'           # Mobile Network Code value (2 or 3 digits)
+mcc: '001'          # Mobile Country Code value
+mnc: '01'           # Mobile Network Code value (2 or 3 digits)
 
 nci: '0x000000010'  # NR Cell Identity (36-bit)
 idLength: 32        # NR gNB ID length in bits [22...32]
-tac: 1              # Tracking Area Code
+tac: 2              # Tracking Area Code
 
-linkIp: 127.0.0.1   # gNB's local IP address for Radio Link Simulation (Usually same with local IP)
-ngapIp: 127.0.0.1   # gNB's local IP address for N2 Interface (Usually same with local IP)
-gtpIp: 127.0.0.1    # gNB's local IP address for N3 Interface (Usually same with local IP)
+linkIp: 192.168.0.132   # gNB's local IP address for Radio Link Simulation (Usually same with local IP)
+ngapIp: 192.168.0.132   # gNB's local IP address for N2 Interface (Usually same with local IP)
+gtpIp: 192.168.0.132    # gNB's local IP address for N3 Interface (Usually same with local IP)
 
 # List of AMF address information
 amfConfigs:
-  - address: 127.0.0.5
+  - address: 192.168.0.111
     port: 38412
 
 # List of supported S-NSSAIs by this gNB

Loc1のUE(IMSI-001010000000000)の設定ファイルの変更点

UERANSIM/config/open5gs-ue-loc1.yaml

--- open5gs-ue.yaml.orig        2021-09-15 13:38:14.000000000 +0900
+++ open5gs-ue-loc1.yaml        2022-06-06 14:47:38.000000000 +0900
@@ -1,9 +1,9 @@
 # IMSI number of the UE. IMSI = [MCC|MNC|MSISDN] (In total 15 digits)
-supi: 'imsi-901700000000001'
+supi: 'imsi-001010000000000'
 # Mobile Country Code value of HPLMN
-mcc: '901'
+mcc: '001'
 # Mobile Network Code value of HPLMN (2 or 3 digits)
-mnc: '70'
+mnc: '01'
 
 # Permanent subscription key
 key: '465B5CE8B199B49FAA5F0A2EE238A6BC'
@@ -20,7 +20,7 @@
 
 # List of gNB IP addresses for Radio Link Simulation
 gnbSearchList:
-  - 127.0.0.1
+  - 192.168.0.131
 
 # UAC Access Identities Configuration
 uacAic:

Loc2のUE(IMSI-001010000000000)の設定ファイルの変更点

UERANSIM/config/open5gs-ue-loc2.yaml

--- open5gs-ue.yaml.orig        2021-09-15 13:38:14.000000000 +0900
+++ open5gs-ue-loc2.yaml        2022-06-06 14:48:32.000000000 +0900
@@ -1,9 +1,9 @@
 # IMSI number of the UE. IMSI = [MCC|MNC|MSISDN] (In total 15 digits)
-supi: 'imsi-901700000000001'
+supi: 'imsi-001010000000000'
 # Mobile Country Code value of HPLMN
-mcc: '901'
+mcc: '001'
 # Mobile Network Code value of HPLMN (2 or 3 digits)
-mnc: '70'
+mnc: '01'
 
 # Permanent subscription key
 key: '465B5CE8B199B49FAA5F0A2EE238A6BC'
@@ -20,7 +20,7 @@
 
 # List of gNB IP addresses for Radio Link Simulation
 gnbSearchList:
-  - 127.0.0.1
+  - 192.168.0.132
 
 # UAC Access Identities Configuration
 uacAic:

Open5GS 5GCとUERANSIM UE/RANのネットワーク設定

Open5GS 5GC C-Planeのネットワーク設定

SMF1とSMF2に以下の通りIPアドレスを追加します。

ip addr add 192.168.0.112/24 dev enp0s8
ip addr add 192.168.0.113/24 dev enp0s8

注意。本記事のVirtualBoxの環境では、enp0s8は192.168.0.0/24のネットワークインターフェースです。環境に応じて変更して下さい。

Open5GS 5GC U-Plane1のネットワーク設定

最初に、/etc/sysctl.confファイルの以下の行のコメントを外し、OSに反映します。

net.ipv4.ip_forward=1

# sysctl -p

次に、TUNインターフェースとNAPTを設定します。

ip tuntap add name ogstun mode tun
ip addr add 10.45.0.1/16 dev ogstun
ip link set ogstun up

iptables -t nat -A POSTROUTING -s 10.45.0.0/16 ! -o ogstun -j MASQUERADE

Open5GS 5GC U-Plane2のネットワーク設定

最初に、/etc/sysctl.confファイルの以下の行のコメントを外し、OSに反映します。

net.ipv4.ip_forward=1

# sysctl -p

次に、TUNインターフェースとNAPTを設定します。

ip tuntap add name ogstun mode tun
ip addr add 10.46.0.1/16 dev ogstun
ip link set ogstun up

iptables -t nat -A POSTROUTING -s 10.46.0.0/16 ! -o ogstun -j MASQUERADE

Open5GSとUERANSIMのビルド

Open5GSとUERANSIMのビルド方法は以下を参照して下さい。

Open5GS v2.4.7 - https://open5gs.org/open5gs/docs/guide/02-building-open5gs-from-sources/
UERANSIM v3.2.6 - https://github.com/aligungr/UERANSIM/wiki/Installation

注意。Open5GS 5GC C-PlaneマシンにMongoDBをインストールして下さい。なお、MongoDBのデータベースを簡単に確認するには、MongoDB Compassが便利です。

# apt update
# apt install mongodb
# systemctl start mongodb
# systemctl enable mongodb

なお、Open5GS 5GC U-PlaneマシンにはMongoDBをインストールする必要はありません。

Open5GS 5GCとUERANSIM UE/RANを実行

最初に5GCを起動し、次にUERANSIM(UEとRANのシミュレータ)を起動します。

Open5GS 5GC C-Planeを実行

Open5GS 5GC C-Plane

./install/bin/open5gs-nrfd &
sleep 2
./install/bin/open5gs-amfd &
sleep 2
./install/bin/open5gs-smfd -c install/etc/open5gs/smf1.yaml &
./install/bin/open5gs-smfd -c install/etc/open5gs/smf2.yaml &
./install/bin/open5gs-ausfd &
./install/bin/open5gs-udmd &
./install/bin/open5gs-udrd &
./install/bin/open5gs-pcfd &
./install/bin/open5gs-nssfd &
./install/bin/open5gs-bsfd &

Open5GS 5GC U-Plane1とU-Plane2を実行

次に、Open5GS 5GC U-Planeを起動します。

Open5GS 5GC U-Plane1

./install/bin/open5gs-upfd &

Open5GS 5GC U-Plane2

./install/bin/open5gs-upfd &

また、各U-PlaneのVMに追加で端末を開き、tcpdumpを実行します。

VM2 (U-Plane1)でtcpdumpを実行

# tcpdump -i ogstun -n
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ogstun, link-type RAW (Raw IP), capture size 262144 bytes

VM3 (U-Plane2)でtcpdumpを実行

# tcpdump -i ogstun -n
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ogstun, link-type RAW (Raw IP), capture size 262144 bytes

UERANSIM(gNodeBs)を実行

二つのロケーションにある、TAC=1,2の各gNodeBを稼働します。
UERANSIMの使い方は以下を参照して下さい。

https://github.com/aligungr/UERANSIM/wiki/Usage

Loc1にあるTAC=1のgNodeB1を起動

次のようにgNBを起動します。

# ./nr-gnb -c ../config/open5gs-gnb.yaml
UERANSIM v3.2.6
[2022-06-07 00:01:28.141] [sctp] [info] Trying to establish SCTP connection... (192.168.0.111:38412)
[2022-06-07 00:01:28.143] [sctp] [info] SCTP connection established (192.168.0.111:38412)
[2022-06-07 00:01:28.144] [sctp] [debug] SCTP association setup ascId[4]
[2022-06-07 00:01:28.144] [ngap] [debug] Sending NG Setup Request
[2022-06-07 00:01:28.145] [ngap] [debug] NG Setup Response received
[2022-06-07 00:01:28.145] [ngap] [info] NG Setup procedure is successful

Open5GS C-Planeのログは以下の通りです。

06/07 00:01:28.141: [amf] INFO: gNB-N2 accepted[192.168.0.131]:50968 in ng-path module (../src/amf/ngap-sctp.c:113)
06/07 00:01:28.141: [amf] INFO: gNB-N2 accepted[192.168.0.131] in master_sm module (../src/amf/amf-sm.c:619)
06/07 00:01:28.142: [amf] INFO: [Added] Number of gNBs is now 1 (../src/amf/context.c:876)
06/07 00:01:28.142: [amf] INFO: gNB-N2[192.168.0.131] max_num_of_ostreams : 10 (../src/amf/amf-sm.c:658)

Loc2にあるTAC=2のgNodeB2を起動

次のようにgNBを起動します。

# ./nr-gnb -c ../config/open5gs-gnb.yaml
UERANSIM v3.2.6
[2022-06-07 00:02:25.990] [sctp] [info] Trying to establish SCTP connection... (192.168.0.111:38412)
[2022-06-07 00:02:25.993] [sctp] [info] SCTP connection established (192.168.0.111:38412)
[2022-06-07 00:02:25.993] [sctp] [debug] SCTP association setup ascId[4]
[2022-06-07 00:02:25.993] [ngap] [debug] Sending NG Setup Request
[2022-06-07 00:02:25.994] [ngap] [debug] NG Setup Response received
[2022-06-07 00:02:25.994] [ngap] [info] NG Setup procedure is successful

Open5GS C-Planeのログは以下の通りです。

06/07 00:02:25.991: [amf] INFO: gNB-N2 accepted[192.168.0.132]:59332 in ng-path module (../src/amf/ngap-sctp.c:113)
06/07 00:02:25.991: [amf] INFO: gNB-N2 accepted[192.168.0.132] in master_sm module (../src/amf/amf-sm.c:619)
06/07 00:02:25.991: [amf] INFO: [Added] Number of gNBs is now 2 (../src/amf/context.c:876)
06/07 00:02:25.991: [amf] INFO: gNB-N2[192.168.0.132] max_num_of_ostreams : 10 (../src/amf/amf-sm.c:658)

UERANSIM(Loc1のUE)を実行

Loc1のgNodeB1にUEを接続して、パケットが同じLoc1のU-Plane1のDNを通過することを確認します。

Loc1のgNodeB1にUEを接続

# ./nr-ue -c ../config/open5gs-ue-loc1.yaml 
UERANSIM v3.2.6
[2022-06-07 00:03:23.431] [nas] [info] UE switches to state [MM-DEREGISTERED/PLMN-SEARCH]
[2022-06-07 00:03:23.431] [rrc] [debug] New signal detected for cell[1], total [1] cells in coverage
[2022-06-07 00:03:23.432] [nas] [info] Selected plmn[001/01]
[2022-06-07 00:03:23.432] [rrc] [info] Selected cell plmn[001/01] tac[1] category[SUITABLE]
[2022-06-07 00:03:23.432] [nas] [info] UE switches to state [MM-DEREGISTERED/PS]
[2022-06-07 00:03:23.433] [nas] [info] UE switches to state [MM-DEREGISTERED/NORMAL-SERVICE]
[2022-06-07 00:03:23.433] [nas] [debug] Initial registration required due to [MM-DEREG-NORMAL-SERVICE]
[2022-06-07 00:03:23.434] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-06-07 00:03:23.434] [nas] [debug] Sending Initial Registration
[2022-06-07 00:03:23.434] [nas] [info] UE switches to state [MM-REGISTER-INITIATED]
[2022-06-07 00:03:23.435] [rrc] [debug] Sending RRC Setup Request
[2022-06-07 00:03:23.436] [rrc] [info] RRC connection established
[2022-06-07 00:03:23.436] [rrc] [info] UE switches to state [RRC-CONNECTED]
[2022-06-07 00:03:23.436] [nas] [info] UE switches to state [CM-CONNECTED]
[2022-06-07 00:03:23.446] [nas] [debug] Authentication Request received
[2022-06-07 00:03:23.449] [nas] [debug] Security Mode Command received
[2022-06-07 00:03:23.449] [nas] [debug] Selected integrity[2] ciphering[0]
[2022-06-07 00:03:23.462] [nas] [debug] Registration accept received
[2022-06-07 00:03:23.463] [nas] [info] UE switches to state [MM-REGISTERED/NORMAL-SERVICE]
[2022-06-07 00:03:23.463] [nas] [debug] Sending Registration Complete
[2022-06-07 00:03:23.463] [nas] [info] Initial Registration is successful
[2022-06-07 00:03:23.464] [nas] [debug] Sending PDU Session Establishment Request
[2022-06-07 00:03:23.464] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-06-07 00:03:23.674] [nas] [debug] Configuration Update Command received
[2022-06-07 00:03:23.693] [nas] [debug] PDU Session Establishment Accept received
[2022-06-07 00:03:23.697] [nas] [info] PDU Session establishment is successful PSI[1]
[2022-06-07 00:03:23.721] [app] [info] Connection setup for PDU session[1] is successful, TUN interface[uesimtun0, 10.45.0.2] is up.

Open5GS C-Planeのログは以下の通りです。

06/07 00:03:23.408: [amf] INFO: InitialUEMessage (../src/amf/ngap-handler.c:361)
06/07 00:03:23.409: [amf] INFO: [Added] Number of gNB-UEs is now 1 (../src/amf/context.c:2072)
06/07 00:03:23.409: [amf] INFO:     RAN_UE_NGAP_ID[1] AMF_UE_NGAP_ID[1] TAC[1] CellID[0x10] (../src/amf/ngap-handler.c:497)
06/07 00:03:23.410: [amf] INFO: [suci-0-001-01-0000-0-0-0000000000] Unknown UE by SUCI (../src/amf/context.c:1398)
06/07 00:03:23.410: [amf] INFO: [Added] Number of AMF-UEs is now 1 (../src/amf/context.c:1197)
06/07 00:03:23.411: [gmm] INFO: Registration request (../src/amf/gmm-sm.c:134)
06/07 00:03:23.411: [gmm] INFO: [suci-0-001-01-0000-0-0-0000000000]    SUCI (../src/amf/gmm-handler.c:157)
06/07 00:03:23.411: [app] WARNING: Try to discover [AUSF] (../lib/sbi/path.c:110)
06/07 00:03:23.412: [amf] INFO: [6977149c-e5a9-41ec-8151-e337ca534306] (NF-discover) NF registered (../src/amf/nnrf-handler.c:344)
06/07 00:03:23.413: [amf] INFO: [6977149c-e5a9-41ec-8151-e337ca534306] (NF-discover) NF Profile updated (../src/amf/nnrf-handler.c:406)
06/07 00:03:23.414: [app] WARNING: Try to discover [UDM] (../lib/sbi/path.c:110)
06/07 00:03:23.414: [ausf] INFO: [6976d25c-e5a9-41ec-ad14-43376ecf8842] (NF-discover) NF registered (../src/ausf/nnrf-handler.c:285)
06/07 00:03:23.415: [ausf] INFO: [6976d25c-e5a9-41ec-ad14-43376ecf8842] (NF-discover) NF Profile updated (../src/ausf/nnrf-handler.c:333)
06/07 00:03:23.421: [app] WARNING: Try to discover [UDM] (../lib/sbi/path.c:110)
06/07 00:03:23.422: [amf] INFO: [6976d25c-e5a9-41ec-ad14-43376ecf8842] (NF-discover) NF registered (../src/amf/nnrf-handler.c:344)
06/07 00:03:23.422: [amf] INFO: [6976d25c-e5a9-41ec-ad14-43376ecf8842] (NF-discover) NF Profile updated (../src/amf/nnrf-handler.c:406)
06/07 00:03:23.426: [app] WARNING: Try to discover [PCF] (../lib/sbi/path.c:110)
06/07 00:03:23.427: [amf] INFO: [697c6dca-e5a9-41ec-a62b-310b7c640deb] (NF-discover) NF registered (../src/amf/nnrf-handler.c:344)
06/07 00:03:23.427: [amf] INFO: [697c6dca-e5a9-41ec-a62b-310b7c640deb] (NF-discover) NF Profile updated (../src/amf/nnrf-handler.c:406)
06/07 00:03:23.428: [app] WARNING: Try to discover [UDR] (../lib/sbi/path.c:110)
06/07 00:03:23.429: [pcf] INFO: [697c1b54-e5a9-41ec-bd80-79fc59629fbf] (NF-discover) NF registered (../src/pcf/nnrf-handler.c:288)
06/07 00:03:23.429: [pcf] INFO: [697c1b54-e5a9-41ec-bd80-79fc59629fbf] (NF-discover) NF Profile updated (../src/pcf/nnrf-handler.c:350)
06/07 00:03:23.640: [gmm] INFO: [imsi-001010000000000] Registration complete (../src/amf/gmm-sm.c:1063)
06/07 00:03:23.642: [amf] INFO: [imsi-001010000000000] Configuration update command (../src/amf/nas-path.c:389)
06/07 00:03:23.642: [gmm] INFO:     UTC [2022-06-06T15:03:23] Timezone[0]/DST[0] (../src/amf/gmm-build.c:502)
06/07 00:03:23.643: [gmm] INFO:     LOCAL [2022-06-07T00:03:23] Timezone[32400]/DST[0] (../src/amf/gmm-build.c:507)
06/07 00:03:23.645: [amf] INFO: [Added] Number of AMF-Sessions is now 1 (../src/amf/context.c:2084)
06/07 00:03:23.646: [gmm] INFO: UE SUPI[imsi-001010000000000] DNN[internet] S_NSSAI[SST:1 SD:0xffffff] (../src/amf/gmm-handler.c:1068)
06/07 00:03:23.648: [smf] INFO: [Added] Number of SMF-UEs is now 1 (../src/smf/context.c:846)
06/07 00:03:23.649: [smf] INFO: [Added] Number of SMF-Sessions is now 1 (../src/smf/context.c:2868)
06/07 00:03:23.650: [app] WARNING: Try to discover [UDM] (../lib/sbi/path.c:110)
06/07 00:03:23.651: [smf] INFO: [6976d25c-e5a9-41ec-ad14-43376ecf8842] (NF-discover) NF registered (../src/smf/nnrf-handler.c:286)
06/07 00:03:23.651: [smf] INFO: [6976d25c-e5a9-41ec-ad14-43376ecf8842] (NF-discover) NF Profile updated (../src/smf/nnrf-handler.c:334)
06/07 00:03:23.653: [app] WARNING: Try to discover [PCF] (../lib/sbi/path.c:110)
06/07 00:03:23.654: [smf] INFO: [697c6dca-e5a9-41ec-a62b-310b7c640deb] (NF-discover) NF registered (../src/smf/nnrf-handler.c:286)
06/07 00:03:23.655: [smf] INFO: [697c6dca-e5a9-41ec-a62b-310b7c640deb] (NF-discover) NF Profile updated (../src/smf/nnrf-handler.c:334)
06/07 00:03:23.656: [app] WARNING: Try to discover [BSF] (../lib/sbi/path.c:110)
06/07 00:03:23.657: [pcf] INFO: [6976bf24-e5a9-41ec-ace6-d932889486a4] (NF-discover) NF registered (../src/pcf/nnrf-handler.c:288)
06/07 00:03:23.657: [pcf] INFO: [6976bf24-e5a9-41ec-ace6-d932889486a4] (NF-discover) NF Profile updated (../src/pcf/nnrf-handler.c:350)
06/07 00:03:23.658: [smf] INFO: UE SUPI[imsi-001010000000000] DNN[internet] IPv4[10.45.0.2] IPv6[] (../src/smf/npcf-handler.c:492)
06/07 00:03:23.659: [gtp] INFO: gtp_connect() [192.168.0.114]:2152 (../lib/gtp/path.c:60)
06/07 00:03:23.659: [app] WARNING: Try to discover [AMF] (../lib/sbi/path.c:110)
06/07 00:03:23.660: [smf] INFO: [697ad4b0-e5a9-41ec-8312-53319a20c697] (NF-discover) NF registered (../src/smf/nnrf-handler.c:286)
06/07 00:03:23.660: [smf] INFO: [697ad4b0-e5a9-41ec-8312-53319a20c697] (NF-discover) NF Profile updated (../src/smf/nnrf-handler.c:334)

Open5GS U-Plane1のログは以下の通りです。

06/07 00:03:23.681: [upf] INFO: [Added] Number of UPF-Sessions is now 1 (../src/upf/context.c:178)
06/07 00:03:23.681: [gtp] INFO: gtp_connect() [192.168.0.112]:2152 (../lib/gtp/path.c:60)
06/07 00:03:23.681: [upf] INFO: UE F-SEID[CP:0x1 UP:0x1] APN[internet] PDN-Type[1] IPv4[10.45.0.2] IPv6[] (../src/upf/context.c:397)
06/07 00:03:23.688: [gtp] INFO: gtp_connect() [192.168.0.131]:2152 (../lib/gtp/path.c:60)

TUNnelインターフェースuesimtun0は次のように作成され、IPアドレス10.45.0.2がUEに割り当てられたことが分かります。

# ip addr show
...
6: uesimtun0: <POINTOPOINT,PROMISC,NOTRAILERS,UP,LOWER_UP> mtu 1400 qdisc fq_codel state UNKNOWN group default qlen 500
    link/none 
    inet 10.45.0.2/32 scope global uesimtun0
       valid_lft forever preferred_lft forever
    inet6 fe80::c69c:7869:841d:ebb5/64 scope link stable-privacy 
       valid_lft forever preferred_lft forever
...

Loc1のDN=10.45.0.0/16を経由してgoogle.comにpingする

tcpdumpを使用して、パケットがU-Plane1のif=ogstunを通過することを確認します。

# ping google.com -I uesimtun0 -n
PING google.com (172.217.26.238) from 10.45.0.2 uesimtun0: 56(84) bytes of data.
64 bytes from 172.217.26.238: icmp_seq=1 ttl=61 time=25.6 ms
64 bytes from 172.217.26.238: icmp_seq=2 ttl=61 time=19.2 ms
64 bytes from 172.217.26.238: icmp_seq=3 ttl=61 time=19.6 ms

U-Plane1のtcpdumpのログは以下の通りです。

00:05:42.875865 IP 10.45.0.2 > 172.217.26.238: ICMP echo request, id 3, seq 1, length 64
00:05:42.898769 IP 172.217.26.238 > 10.45.0.2: ICMP echo reply, id 3, seq 1, length 64
00:05:43.877164 IP 10.45.0.2 > 172.217.26.238: ICMP echo request, id 3, seq 2, length 64
00:05:43.894229 IP 172.217.26.238 > 10.45.0.2: ICMP echo reply, id 3, seq 2, length 64
00:05:44.878832 IP 10.45.0.2 > 172.217.26.238: ICMP echo request, id 3, seq 3, length 64
00:05:44.896115 IP 172.217.26.238 > 10.45.0.2: ICMP echo reply, id 3, seq 3, length 64

注意。パケットがU-Plane2を通過しないことを確認して下さい。UEは接続したLoc1のgNodeB1に従って、同じLoc1のU-Plane1のDNに接続します。

UERANSIM(Loc2のUE)を実行

gNodeB1との接続を切り、Loc2のgNodeB2にUEを接続して、パケットが同じLoc2のU-Plane2のDNを通過することを確認します。

Loc2のgNodeB2にUEを接続

# ./nr-ue -c ../config/open5gs-ue-loc2.yaml 
UERANSIM v3.2.6
[2022-06-07 00:06:56.988] [nas] [info] UE switches to state [MM-DEREGISTERED/PLMN-SEARCH]
[2022-06-07 00:06:56.989] [rrc] [debug] New signal detected for cell[1], total [1] cells in coverage
[2022-06-07 00:06:56.990] [nas] [info] Selected plmn[001/01]
[2022-06-07 00:06:56.990] [rrc] [info] Selected cell plmn[001/01] tac[2] category[SUITABLE]
[2022-06-07 00:06:56.990] [nas] [info] UE switches to state [MM-DEREGISTERED/PS]
[2022-06-07 00:06:56.991] [nas] [info] UE switches to state [MM-DEREGISTERED/NORMAL-SERVICE]
[2022-06-07 00:06:56.991] [nas] [debug] Initial registration required due to [MM-DEREG-NORMAL-SERVICE]
[2022-06-07 00:06:56.992] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-06-07 00:06:56.992] [nas] [debug] Sending Initial Registration
[2022-06-07 00:06:56.993] [rrc] [debug] Sending RRC Setup Request
[2022-06-07 00:06:56.993] [nas] [info] UE switches to state [MM-REGISTER-INITIATED]
[2022-06-07 00:06:56.994] [rrc] [info] RRC connection established
[2022-06-07 00:06:56.994] [rrc] [info] UE switches to state [RRC-CONNECTED]
[2022-06-07 00:06:56.995] [nas] [info] UE switches to state [CM-CONNECTED]
[2022-06-07 00:06:57.002] [nas] [debug] Authentication Request received
[2022-06-07 00:06:57.005] [nas] [debug] Security Mode Command received
[2022-06-07 00:06:57.005] [nas] [debug] Selected integrity[2] ciphering[0]
[2022-06-07 00:06:57.014] [nas] [debug] Registration accept received
[2022-06-07 00:06:57.014] [nas] [info] UE switches to state [MM-REGISTERED/NORMAL-SERVICE]
[2022-06-07 00:06:57.015] [nas] [debug] Sending Registration Complete
[2022-06-07 00:06:57.015] [nas] [info] Initial Registration is successful
[2022-06-07 00:06:57.015] [nas] [debug] Sending PDU Session Establishment Request
[2022-06-07 00:06:57.016] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-06-07 00:06:57.220] [nas] [debug] Configuration Update Command received
[2022-06-07 00:06:57.239] [nas] [debug] PDU Session Establishment Accept received
[2022-06-07 00:06:57.240] [nas] [info] PDU Session establishment is successful PSI[1]
[2022-06-07 00:06:57.259] [app] [info] Connection setup for PDU session[1] is successful, TUN interface[uesimtun0, 10.46.0.2] is up.

Open5GS C-Planeのログは以下の通りです。

06/07 00:06:56.963: [amf] INFO: InitialUEMessage (../src/amf/ngap-handler.c:361)
06/07 00:06:56.963: [amf] INFO: [Added] Number of gNB-UEs is now 2 (../src/amf/context.c:2072)
06/07 00:06:56.963: [amf] INFO:     RAN_UE_NGAP_ID[1] AMF_UE_NGAP_ID[2] TAC[2] CellID[0x10] (../src/amf/ngap-handler.c:497)
06/07 00:06:56.963: [amf] INFO: [suci-0-001-01-0000-0-0-0000000000] known UE by SUCI (../src/amf/context.c:1396)
06/07 00:06:56.963: [gmm] INFO: Registration request (../src/amf/gmm-sm.c:134)
06/07 00:06:56.963: [gmm] INFO: [suci-0-001-01-0000-0-0-0000000000]    SUCI (../src/amf/gmm-handler.c:157)
06/07 00:06:56.964: [amf] INFO: UE Context Release [Action:1] (../src/amf/ngap-handler.c:1405)
06/07 00:06:56.964: [amf] INFO:     RAN_UE_NGAP_ID[1] AMF_UE_NGAP_ID[1] (../src/amf/ngap-handler.c:1406)
06/07 00:06:56.965: [amf] INFO: [Removed] Number of gNB-UEs is now 1 (../src/amf/context.c:2078)
06/07 00:06:56.966: [smf] INFO: Removed Session: UE IMSI:[imsi-001010000000000] DNN:[internet:1] IPv4:[10.45.0.2] IPv6:[] (../src/smf/context.c:1540)
06/07 00:06:56.966: [smf] INFO: [Removed] Number of SMF-Sessions is now 0 (../src/smf/context.c:2874)
06/07 00:06:56.967: [smf] INFO: [Removed] Number of SMF-UEs is now 0 (../src/smf/context.c:901)
06/07 00:06:56.967: [amf] INFO: [imsi-001010000000000:1] Release SM context [204] (../src/amf/amf-sm.c:451)
06/07 00:06:56.967: [amf] INFO: [Removed] Number of AMF-Sessions is now 0 (../src/amf/context.c:2090)
06/07 00:06:56.979: [pcf] WARNING: NF EndPoint updated [127.0.0.5:7777] (../src/pcf/npcf-handler.c:93)
06/07 00:06:57.184: [gmm] INFO: [imsi-001010000000000] Registration complete (../src/amf/gmm-sm.c:1063)
06/07 00:06:57.185: [amf] INFO: [imsi-001010000000000] Configuration update command (../src/amf/nas-path.c:389)
06/07 00:06:57.186: [gmm] INFO:     UTC [2022-06-06T15:06:57] Timezone[0]/DST[0] (../src/amf/gmm-build.c:502)
06/07 00:06:57.187: [gmm] INFO:     LOCAL [2022-06-07T00:06:57] Timezone[32400]/DST[0] (../src/amf/gmm-build.c:507)
06/07 00:06:57.188: [amf] INFO: [Added] Number of AMF-Sessions is now 1 (../src/amf/context.c:2084)
06/07 00:06:57.188: [gmm] INFO: UE SUPI[imsi-001010000000000] DNN[internet] S_NSSAI[SST:1 SD:0xffffff] (../src/amf/gmm-handler.c:1068)
06/07 00:06:57.190: [smf] INFO: [Added] Number of SMF-UEs is now 1 (../src/smf/context.c:846)
06/07 00:06:57.191: [smf] INFO: [Added] Number of SMF-Sessions is now 1 (../src/smf/context.c:2868)
06/07 00:06:57.191: [app] WARNING: Try to discover [UDM] (../lib/sbi/path.c:110)
06/07 00:06:57.193: [smf] INFO: [6976d25c-e5a9-41ec-ad14-43376ecf8842] (NF-discover) NF registered (../src/smf/nnrf-handler.c:286)
06/07 00:06:57.194: [smf] INFO: [6976d25c-e5a9-41ec-ad14-43376ecf8842] (NF-discover) NF Profile updated (../src/smf/nnrf-handler.c:334)
06/07 00:06:57.198: [app] WARNING: Try to discover [PCF] (../lib/sbi/path.c:110)
06/07 00:06:57.199: [smf] INFO: [697c6dca-e5a9-41ec-a62b-310b7c640deb] (NF-discover) NF registered (../src/smf/nnrf-handler.c:286)
06/07 00:06:57.199: [smf] INFO: [697c6dca-e5a9-41ec-a62b-310b7c640deb] (NF-discover) NF Profile updated (../src/smf/nnrf-handler.c:334)
06/07 00:06:57.201: [smf] INFO: UE SUPI[imsi-001010000000000] DNN[internet] IPv4[10.46.0.2] IPv6[] (../src/smf/npcf-handler.c:492)
06/07 00:06:57.202: [gtp] INFO: gtp_connect() [192.168.0.115]:2152 (../lib/gtp/path.c:60)
06/07 00:06:57.203: [app] WARNING: Try to discover [AMF] (../lib/sbi/path.c:110)
06/07 00:06:57.203: [smf] INFO: [697ad4b0-e5a9-41ec-8312-53319a20c697] (NF-discover) NF registered (../src/smf/nnrf-handler.c:286)
06/07 00:06:57.204: [smf] INFO: [697ad4b0-e5a9-41ec-8312-53319a20c697] (NF-discover) NF Profile updated (../src/smf/nnrf-handler.c:334)

Open5GS U-Plane2のログは以下の通りです。

06/07 00:06:57.216: [upf] INFO: [Added] Number of UPF-Sessions is now 1 (../src/upf/context.c:178)
06/07 00:06:57.216: [gtp] INFO: gtp_connect() [192.168.0.113]:2152 (../lib/gtp/path.c:60)
06/07 00:06:57.216: [upf] INFO: UE F-SEID[CP:0x1 UP:0x1] APN[internet] PDN-Type[1] IPv4[10.46.0.2] IPv6[] (../src/upf/context.c:397)
06/07 00:06:57.221: [gtp] INFO: gtp_connect() [192.168.0.132]:2152 (../lib/gtp/path.c:60)

TUNnelインターフェースuesimtun0は次のように作成され、IPアドレス10.46.0.2がUEに割り当てられたことが分かります。

# ip addr show
...
7: uesimtun0: <POINTOPOINT,PROMISC,NOTRAILERS,UP,LOWER_UP> mtu 1400 qdisc fq_codel state UNKNOWN group default qlen 500
    link/none 
    inet 10.46.0.2/32 scope global uesimtun0
       valid_lft forever preferred_lft forever
    inet6 fe80::95ac:7201:6b2f:d9c9/64 scope link stable-privacy 
       valid_lft forever preferred_lft forever
...

Loc2のDN=10.46.0.0/16を経由してgoogle.comにpingする

tcpdumpを使用して、パケットがU-Plane2のif=ogstunを通過することを確認します。

# ping google.com -I uesimtun0 -n
PING google.com (172.217.31.142) from 10.46.0.2 uesimtun0: 56(84) bytes of data.
64 bytes from 172.217.31.142: icmp_seq=1 ttl=61 time=20.6 ms
64 bytes from 172.217.31.142: icmp_seq=2 ttl=61 time=18.8 ms
64 bytes from 172.217.31.142: icmp_seq=3 ttl=61 time=18.6 ms

U-Plane2のtcpdumpのログは以下の通りです。

00:08:49.720410 IP 10.46.0.2 > 172.217.31.142: ICMP echo request, id 4, seq 1, length 64
00:08:49.737952 IP 172.217.31.142 > 10.46.0.2: ICMP echo reply, id 4, seq 1, length 64
00:08:50.721785 IP 10.46.0.2 > 172.217.31.142: ICMP echo request, id 4, seq 2, length 64
00:08:50.738229 IP 172.217.31.142 > 10.46.0.2: ICMP echo reply, id 4, seq 2, length 64
00:08:51.723584 IP 10.46.0.2 > 172.217.31.142: ICMP echo request, id 4, seq 3, length 64
00:08:51.739664 IP 172.217.31.142 > 10.46.0.2: ICMP echo reply, id 4, seq 3, length 64

注意。パケットがU-Plane1を通過しないことを確認して下さい。UEは接続したLoc2のgNodeB2に従って、同じLoc2のU-Plane2のDNに接続します。

これで、UEが接続したgNodeBと同じロケーションにあるUPFのDNに接続するという非常にシンプルな構成を確認できました。UEからのトラフィックを最寄りの基地局のDNにルーティングしてMECを実現する際の設定のヒントになることを期待しています。

最後に

端末が接続した基地局に応じて、最寄りのネットワークのサーバにトラフィックを集約して処理することは、MECの視点からポピュラーなニーズと思います。
ところで、3GPP TS 23.502- 5.2.7.3.2 Nnrf_NFDiscovery_Request service operationのNF選択の入力パラメータの観点から、Open5GSの場合、AMFがSMFを選択する際のパラメータには、S-NSSAI、DNNの他に、TAI(=PLMN+TAC)が使えます。これにより、gNodeBのTACに応じて最寄りのSMFが選択され、この結果、最寄りのUPFが選択されるロジックは、自然な印象を受けました。
一方、free5GCのAMFはTACでSMFを選択せず、preferred target NF locationを用いる方式です。この場合、今回のような構成を実現しようとすると、AMFとSMFのペアをロケーション毎に用意する感じになると思います。
いずれも一長一短があると思いますが、欲を言えば、両方に対応することで、とても柔軟にAMF、SMF、UPFを構成できるようになると良いと思います。

最後に、元記事はGithubに書いたものです。Open5GSのチュートリアルからもリンクして頂きました。

主な変更履歴

[2022.07.13] Open5GS v2.4.7に対応し、UERANSIM v3.2.6に対応。
[2022.03.11] 初版。

You get articles that match your needs
You can efficiently read back useful information
You can use dark theme

What you can do with signing up

Open5GS 5GCとUERANSIM UE/RANでgNodeBの最寄りのUPFを選択する設定

目次

Open5GS 5GCのシミュレーション携帯網の概要

Open5GS 5GCとUERANSIM UE/RANの設定ファイルの変更点

Open5GS 5GC C-Planeの設定ファイルの変更点

Open5GS 5GC U-Plane1の設定ファイルの変更点

Open5GS 5GC U-Plane2の設定ファイルの変更点

UERANSIM UE/RANの設定ファイルの変更点

RAN(gNodeB1)の設定ファイルの変更点

RAN(gNodeB2)の設定ファイルの変更点

Loc1のUE(IMSI-001010000000000)の設定ファイルの変更点

Loc2のUE(IMSI-001010000000000)の設定ファイルの変更点

Open5GS 5GCとUERANSIM UE/RANのネットワーク設定

Open5GS 5GC C-Planeのネットワーク設定

Open5GS 5GC U-Plane1のネットワーク設定

Open5GS 5GC U-Plane2のネットワーク設定

Open5GSとUERANSIMのビルド

Open5GS 5GCとUERANSIM UE/RANを実行

Open5GS 5GC C-Planeを実行

Open5GS 5GC U-Plane1とU-Plane2を実行

UERANSIM(gNodeBs)を実行

Loc1にあるTAC=1のgNodeB1を起動

Loc2にあるTAC=2のgNodeB2を起動

UERANSIM(Loc1のUE)を実行

Loc1のgNodeB1にUEを接続

Loc1のDN=10.45.0.0/16を経由してgoogle.comにpingする

UERANSIM(Loc2のUE)を実行

Loc2のgNodeB2にUEを接続

Loc2のDN=10.46.0.0/16を経由してgoogle.comにpingする

最後に

主な変更履歴