XOS>> open5gs_5gc_ueransim_sample_config>> 返回
项目作者： s5uishida

项目描述 ：
Open5GS 5GC & UERANSIM UE / RAN Sample Configuration
高级语言：
项目地址: git://github.com/s5uishida/open5gs_5gc_ueransim_sample_config.git


Open5GS 5GC & UERANSIM UE / RAN Sample Configuration

UERANSIM (5G UE & RAN (gNodeB) implementation) supports IPv4 of PDU Session Type from 2020.11.17 version, and the Data Plane facility has been enabled.
Therefore, in order to use U-Plane’s DN (Data Network) as a trial, I built a simulation environment for the 5GC mobile network.
This briefly describes the overall and configuration files.

Sample Configurations and Miscellaneous for Mobile Network

Table of Contents

Overview of Open5GS 5GC Simulation Mobile Network

I created a 5GC mobile network (Internet reachable) for simulation with the aim of creating an environment in which packets can be sent end-to-end with different DNs for each DNN.

The following minimum configuration was set as a condition.

  • C-Plane have multiple U-Planes.
  • U-Plane have multiple DNs.
  • Multiple UEs connect to same DN.

The built simulation environment is as follows.

The 5GC / UE / RAN used are as follows.

Each VMs are as follows.
| VM # | SW & Role | IP address | OS | Memory (Min) | HDD (Min) |
| —- | —- | —- | —- | —- | —- |
| VM1 | Open5GS 5GC C-Plane | 192.168.0.111/24 | Ubuntu 22.04 | 1GB | 20GB |
| VM2 | Open5GS 5GC U-Plane1 | 192.168.0.112/24 | Ubuntu 22.04 | 1GB | 20GB |
| VM3 | Open5GS 5GC U-Plane2 | 192.168.0.113/24 | Ubuntu 22.04 | 1GB | 20GB |
| VM4 | UERANSIM RAN (gNodeB) | 192.168.0.131/24 | Ubuntu 22.04 | 1GB | 10GB |
| VM5 | UERANSIM UE | 192.168.0.132/24 | Ubuntu 22.04 | 1GB | 10GB |

Subscriber Information (other information is the same) is as follows.
Note. Please select OP or OPc according to the setting of UERANSIM UE configuration files.
| UE # | IMSI | DNN | OP/OPc |
| —- | —- | —- | —- |
| UE0 | 001010000000000 | internet | OPc |
| UE1 | 001010000000001 | internet2 | OPc |
| UE2 | 001010000000002 | internet2 | OPc |
| UE3 | 001010000000003 | ims | OPc |
| UE4 | 001010000000004 | ims | OPc |

I registered these information with the Open5GS WebUI.
In addition, 3GPP TS 35.208 “4.3 Test Sets” is published by 3GPP as test data for the 3GPP authentication and key generation functions (MILENAGE).

Each DNs are as follows.
| DN | TUNnel interface of DN | DNN | TUNnel interface of UE | U-Plane # |
| —- | —- | —- | —- | —- |
| 10.45.0.0/16 | ogstun | internet | uesimtun0 | U-Plane1 |
| 10.46.0.0/16 | ogstun2 | internet2 | uesimtun1, uesimtun2 | U-Plane1 |
| 10.47.0.0/16 | ogstun3 | ims | uesimtun3, uesimtun4 | U-Plane2 |

Additional information.

Open5GS 5GC U-Plane worked fine on Raspberry Pi 4 Model B. I used Ubuntu 20.04 (64bit) for Raspberry Pi 4 as the OS. I think it would be convenient to place a compact U-Plane in the edge environment and use it as an end-point for DN.

In addition, I have not confirmed the communication performance.

Changes in configuration files of Open5GS 5GC and UERANSIM UE / RAN

Please refer to the following for building Open5GS and UERANSIM respectively.

Changes in configuration files of Open5GS 5GC C-Plane

The following parameters can be used in the logic that selects UPF as the connection destination by PFCP.

  • DNN
  • TAC (Tracking Area Code)
  • nr_CellID

For the sake of simplicity, I used only DNN this time.

  • open5gs/install/etc/open5gs/amf.yaml
    ```diff
    —- amf.yaml.orig 2024-03-24 15:36:48.000000000 +0900
    +++ amf.yaml 2024-03-24 20:19:58.000000000 +0900
    @@ -19,27 +19,27 @@
    1.    - uri: http://127.0.0.200:7777
    ngap:
    server:
    • address: 127.0.0.5
    • address: 192.168.0.111
      metrics:
      server:
    • address: 127.0.0.5
      port: 9090
      guami:
    • plmn_id:
  • mcc: 999
  • mnc: 70
  • mcc: 001
  • mnc: 01
    amf_id:
    region: 2
    set: 1
    tai:
    • plmn_id:
  • mcc: 999
  • mnc: 70
  • mcc: 001
  • mnc: 01
    tac: 1
    plmn_support:
    • plmn_id:
  • mcc: 999
  • mnc: 70
  • mcc: 001
  • mnc: 01
    s_nssai:
    • sst: 1
      security:
      ```
  • open5gs/install/etc/open5gs/nrf.yaml
    ```diff
    —- nrf.yaml.orig 2024-03-24 15:36:48.000000000 +0900
    +++ nrf.yaml 2024-03-24 20:58:02.000000000 +0900
    @@ -10,8 +10,8 @@
    nrf:
    serving: # 5G roaming requires PLMN in NRF
    • plmn_id:
  • mcc: 999
  • mnc: 70
  • mcc: 001
  • mnc: 01
    sbi:
    server:
    • address: 127.0.0.10
      ```
  • open5gs/install/etc/open5gs/smf.yaml
    ```diff
    —- smf.yaml.orig 2024-03-24 15:36:48.000000000 +0900
    +++ smf.yaml 2024-03-31 22:47:39.617010062 +0900
    @@ -19,35 +19,37 @@
    1.    - uri: http://127.0.0.200:7777
    pfcp:
    server:
    • address: 127.0.0.4
    • address: 192.168.0.111
      client:
      upf:
    • address: 127.0.0.7
  • gtpc:
  • server:
    • address: 127.0.0.4
    • address: 192.168.0.112
  • dnn: [internet, internet2]
    • address: 192.168.0.113
  • dnn: ims
    gtpu:
    server:
    • address: 127.0.0.4
    • address: 192.168.0.111
      metrics:
      server:
    • address: 127.0.0.4
      port: 9090
      session:
    • subnet: 10.45.0.1/16
    • subnet: 2001:db8:cafe::1/48
  • dnn: internet
    • subnet: 10.46.0.1/16
  • dnn: internet2
    • subnet: 10.47.0.1/16
  • dnn: ims
    dns:
    • 8.8.8.8
    • 8.8.4.4
    • 2001:4860:4860::8888
    • 2001:4860:4860::8844
      mtu: 1400

      p-cscf:

      - 127.0.0.1

      - ::1

      ctf:

      enabled: auto # auto(default)|yes|no

  • freeDiameter: /root/open5gs/install/etc/freeDiameter/smf.conf
    +# freeDiameter: /root/open5gs/install/etc/freeDiameter/smf.conf

    #

    SMF Info

    ```

Changes in configuration files of Open5GS 5GC U-Plane1

  • open5gs/install/etc/open5gs/upf.yaml
    ```diff
    —- upf.yaml.orig 2024-03-24 15:36:48.000000000 +0900
    +++ upf.yaml 2024-03-29 18:40:33.139948345 +0900
    @@ -10,16 +10,20 @@
    upf:
    pfcp:
    server:
    • address: 127.0.0.7
    • address: 192.168.0.112
      client:

      smf: # UPF PFCP Client try to associate SMF PFCP Server

      - address: 127.0.0.4

      gtpu:
      server:
    • address: 127.0.0.7
    • address: 192.168.0.112
      session:
    • subnet: 10.45.0.1/16
    • subnet: 2001:db8:cafe::1/48
  • dnn: internet
  • dev: ogstun
    • subnet: 10.46.0.1/16
  • dnn: internet2
  • dev: ogstun2
    metrics:
    server:
    • address: 127.0.0.7
      ```

Changes in configuration files of Open5GS 5GC U-Plane2

  • open5gs/install/etc/open5gs/upf.yaml
    ```diff
    —- upf.yaml.orig 2024-03-24 15:36:48.000000000 +0900
    +++ upf.yaml 2024-03-29 18:42:31.755931554 +0900
    @@ -10,16 +10,17 @@
    upf:
    pfcp:
    server:
    • address: 127.0.0.7
    • address: 192.168.0.113
      client:

      smf: # UPF PFCP Client try to associate SMF PFCP Server

      - address: 127.0.0.4

      gtpu:
      server:
    • address: 127.0.0.7
    • address: 192.168.0.113
      session:
    • subnet: 10.45.0.1/16
    • subnet: 2001:db8:cafe::1/48
    • subnet: 10.47.0.1/16
  • dnn: ims
  • dev: ogstun3
    metrics:
    server:
    • address: 127.0.0.7
      ```

Changes in configuration files of UERANSIM UE / RAN

Changes in configuration files of RAN

  • UERANSIM/config/open5gs-gnb.yaml
    ```diff
    —- open5gs-gnb.yaml.orig 2022-07-03 13:06:44.000000000 +0900
    +++ open5gs-gnb.yaml 2024-03-29 16:25:09.415183762 +0900
    @@ -1,17 +1,17 @@
    -mcc: ‘999’ # 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

    ```

Changes in configuration files of UE0 (IMSI-001010000000000)

First, copy open5gs-ue0.yaml from open5gs-ue.yaml.

  1. # cd UERANSIM/config
  2. # cp open5gs-ue.yaml open5gs-ue0.yaml

Next, edit open5gs-ue0.yaml.

  • UERANSIM/config/open5gs-ue0.yaml
    ```diff
    —- open5gs-ue.yaml.orig 2023-12-02 06:14:20.000000000 +0900
    +++ open5gs-ue0.yaml 2024-03-29 16:27:36.390313563 +0900
    @@ -1,9 +1,9 @@

    IMSI number of the UE. IMSI = [MCC|MNC|MSISDN] (In total 15 digits)

    -supi: ‘imsi-999700000000001’
    +supi: ‘imsi-001010000000000’

    Mobile Country Code value of HPLMN

    -mcc: ‘999’
    +mcc: ‘001’

    Mobile Network Code value of HPLMN (2 or 3 digits)

    -mnc: ‘70’
    +mnc: ‘01’

    SUCI Protection Scheme : 0 for Null-scheme, 1 for Profile A and 2 for Profile B

    protectionScheme: 0

    Home Network Public Key for protecting with SUCI Profile A

    @@ -28,7 +28,7 @@

    List of gNB IP addresses for Radio Link Simulation

    gnbSearchList:

    • 127.0.0.1
    • 192.168.0.131

    UAC Access Identities Configuration

    uacAic:
    ```

Changes in configuration files of UE1 (IMSI-001010000000001)

First, copy open5gs-ue1.yaml from open5gs-ue.yaml.

  1. # cd UERANSIM/config
  2. # cp open5gs-ue.yaml open5gs-ue1.yaml

Next, edit open5gs-ue1.yaml.

  • UERANSIM/config/open5gs-ue1.yaml
    ```diff
    —- open5gs-ue.yaml.orig 2023-12-02 06:14:20.000000000 +0900
    +++ open5gs-ue1.yaml 2024-03-29 18:52:49.604939075 +0900
    @@ -1,9 +1,9 @@

    IMSI number of the UE. IMSI = [MCC|MNC|MSISDN] (In total 15 digits)

    -supi: ‘imsi-999700000000001’
    +supi: ‘imsi-001010000000001’

    Mobile Country Code value of HPLMN

    -mcc: ‘999’
    +mcc: ‘001’

    Mobile Network Code value of HPLMN (2 or 3 digits)

    -mnc: ‘70’
    +mnc: ‘01’

    SUCI Protection Scheme : 0 for Null-scheme, 1 for Profile A and 2 for Profile B

    protectionScheme: 0

    Home Network Public Key for protecting with SUCI Profile A

    @@ -28,7 +28,7 @@

    List of gNB IP addresses for Radio Link Simulation

    gnbSearchList:

    • 127.0.0.1
    • 192.168.0.131

    UAC Access Identities Configuration

    uacAic:
    @@ -47,7 +47,7 @@

    Initial PDU sessions to be established

    sessions:

    • type: ‘IPv4’
  • apn: ‘internet’
  • apn: ‘internet2’
    slice:
    sst: 1
  2. <a id="changes_ue2"></a>
  4. #### Changes in configuration files of UE2 (IMSI-001010000000002)
  6. First, copy `open5gs-ue2.yaml` from `open5gs-ue.yaml`.

cd UERANSIM/config

cp open5gs-ue.yaml open5gs-ue2.yaml

  1. Next, edit `open5gs-ue2.yaml`.
  2. - `UERANSIM/config/open5gs-ue2.yaml`
  3. ```diff
  4. --- open5gs-ue.yaml.orig        2023-12-02 06:14:20.000000000 +0900
  5. +++ open5gs-ue2.yaml    2024-03-29 18:53:06.317952751 +0900
  6. @@ -1,9 +1,9 @@
  7.  # IMSI number of the UE. IMSI = [MCC|MNC|MSISDN] (In total 15 digits)
  8. -supi: 'imsi-999700000000001'
  9. +supi: 'imsi-001010000000002'
  10.  # Mobile Country Code value of HPLMN
  11. -mcc: '999'
  12. +mcc: '001'
  13.  # Mobile Network Code value of HPLMN (2 or 3 digits)
  14. -mnc: '70'
  15. +mnc: '01'
  16.  # SUCI Protection Scheme : 0 for Null-scheme, 1 for Profile A and 2 for Profile B
  17.  protectionScheme: 0
  18.  # Home Network Public Key for protecting with SUCI Profile A
  19. @@ -28,7 +28,7 @@
  21.  # List of gNB IP addresses for Radio Link Simulation
  22.  gnbSearchList:
  23. -  - 127.0.0.1
  24. +  - 192.168.0.131
  26.  # UAC Access Identities Configuration
  27.  uacAic:
  28. @@ -47,7 +47,7 @@
  29.  # Initial PDU sessions to be established
  30.  sessions:
  31.    - type: 'IPv4'
  32. -    apn: 'internet'
  33. +    apn: 'internet2'
  34.      slice:
  35.        sst: 1

Changes in configuration files of UE3 (IMSI-001010000000003)

First, copy open5gs-ue3.yaml from open5gs-ue.yaml.

  1. # cd UERANSIM/config
  2. # cp open5gs-ue.yaml open5gs-ue3.yaml

Next, edit open5gs-ue3.yaml.

  • UERANSIM/config/open5gs-ue3.yaml
    ```diff
    —- open5gs-ue.yaml.orig 2023-12-02 06:14:20.000000000 +0900
    +++ open5gs-ue3.yaml 2024-03-29 18:53:41.885991489 +0900
    @@ -1,9 +1,9 @@

    IMSI number of the UE. IMSI = [MCC|MNC|MSISDN] (In total 15 digits)

    -supi: ‘imsi-999700000000001’
    +supi: ‘imsi-001010000000003’

    Mobile Country Code value of HPLMN

    -mcc: ‘999’
    +mcc: ‘001’

    Mobile Network Code value of HPLMN (2 or 3 digits)

    -mnc: ‘70’
    +mnc: ‘01’

    SUCI Protection Scheme : 0 for Null-scheme, 1 for Profile A and 2 for Profile B

    protectionScheme: 0

    Home Network Public Key for protecting with SUCI Profile A

    @@ -28,7 +28,7 @@

    List of gNB IP addresses for Radio Link Simulation

    gnbSearchList:

    • 127.0.0.1
    • 192.168.0.131

    UAC Access Identities Configuration

    uacAic:
    @@ -47,7 +47,7 @@

    Initial PDU sessions to be established

    sessions:

    • type: ‘IPv4’
  • apn: ‘internet’
  • apn: ‘ims’
    slice:
    sst: 1
  2. <a id="changes_ue4"></a>
  4. #### Changes in configuration files of UE4 (IMSI-001010000000004)
  6. First, copy `open5gs-ue4.yaml` from `open5gs-ue.yaml`.

cd UERANSIM/config

cp open5gs-ue.yaml open5gs-ue4.yaml

  1. Next, edit `open5gs-ue4.yaml`.
  2. - `UERANSIM/config/open5gs-ue4.yaml`
  3. ```diff
  4. --- open5gs-ue.yaml.orig        2023-12-02 06:14:20.000000000 +0900
  5. +++ open5gs-ue4.yaml    2024-03-29 18:54:02.414019541 +0900
  6. @@ -1,9 +1,9 @@
  7.  # IMSI number of the UE. IMSI = [MCC|MNC|MSISDN] (In total 15 digits)
  8. -supi: 'imsi-999700000000001'
  9. +supi: 'imsi-001010000000004'
  10.  # Mobile Country Code value of HPLMN
  11. -mcc: '999'
  12. +mcc: '001'
  13.  # Mobile Network Code value of HPLMN (2 or 3 digits)
  14. -mnc: '70'
  15. +mnc: '01'
  16.  # SUCI Protection Scheme : 0 for Null-scheme, 1 for Profile A and 2 for Profile B
  17.  protectionScheme: 0
  18.  # Home Network Public Key for protecting with SUCI Profile A
  19. @@ -28,7 +28,7 @@
  21.  # List of gNB IP addresses for Radio Link Simulation
  22.  gnbSearchList:
  23. -  - 127.0.0.1
  24. +  - 192.168.0.131
  26.  # UAC Access Identities Configuration
  27.  uacAic:
  28. @@ -47,7 +47,7 @@
  29.  # Initial PDU sessions to be established
  30.  sessions:
  31.    - type: 'IPv4'
  32. -    apn: 'internet'
  33. +    apn: 'ims'
  34.      slice:
  35.        sst: 1

Network settings of Open5GS 5GC and UERANSIM UE / RAN

Network settings of Open5GS 5GC U-Plane1

First, uncomment the next line in the /etc/sysctl.conf file and reflect it in the OS.

  1. net.ipv4.ip_forward=1
  1. # sysctl -p

Next, configure the TUNnel interface and NAPT.

  1. ip tuntap add name ogstun mode tun
  2. ip addr add 10.45.0.1/16 dev ogstun
  3. ip link set ogstun up
  5. iptables -t nat -A POSTROUTING -s 10.45.0.0/16 ! -o ogstun -j MASQUERADE
  7. ip tuntap add name ogstun2 mode tun
  8. ip addr add 10.46.0.1/16 dev ogstun2
  9. ip link set ogstun2 up
  11. iptables -t nat -A POSTROUTING -s 10.46.0.0/16 ! -o ogstun2 -j MASQUERADE

Network settings of Open5GS 5GC U-Plane2

First, uncomment the next line in the /etc/sysctl.conf file and reflect it in the OS.

  1. net.ipv4.ip_forward=1
  1. # sysctl -p

Next, configure the TUNnel interface and NAPT.

  1. ip tuntap add name ogstun3 mode tun
  2. ip addr add 10.47.0.1/16 dev ogstun3
  3. ip link set ogstun3 up
  5. iptables -t nat -A POSTROUTING -s 10.47.0.0/16 ! -o ogstun3 -j MASQUERADE

Build Open5GS and UERANSIM

Please refer to the following for building Open5GS and UERANSIM respectively.

Install MongoDB on Open5GS 5GC C-Plane machine.
It is not necessary to install MongoDB on Open5GS 5GC U-Plane machines.
MongoDB Compass is a convenient tool to look at the MongoDB database.

Run Open5GS 5GC and UERANSIM UE / RAN

First run the 5GC, then UERANSIM (UE & RAN implementation).

Run Open5GS 5GC C-Plane

First, run Open5GS 5GC C-Plane.

  • Open5GS 5GC C-Plane
    1. ./install/bin/open5gs-nrfd &
    2. sleep 2
    3. ./install/bin/open5gs-scpd &
    4. sleep 2
    5. ./install/bin/open5gs-amfd &
    6. sleep 2
    7. ./install/bin/open5gs-smfd &
    8. ./install/bin/open5gs-ausfd &
    9. ./install/bin/open5gs-udmd &
    10. ./install/bin/open5gs-udrd &
    11. ./install/bin/open5gs-pcfd &
    12. ./install/bin/open5gs-nssfd &
    13. ./install/bin/open5gs-bsfd &

Run Open5GS 5GC U-Plane1 & U-Plane2

Next, run Open5GS 5GC U-Plane.

  • Open5GS 5GC U-Plane1
    1. ./install/bin/open5gs-upfd &
  • Open5GS 5GC U-Plane2
    1. ./install/bin/open5gs-upfd &

Run UERANSIM

Here, the case of UE0 (IMSI-001010000000000) & RAN is described.
First, do an NG Setup between gNodeB and 5GC, then register the UE with 5GC and establish a PDU session.

Please refer to the following for usage of UERANSIM.

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

Start gNB

Start gNB as follows.

  1. # ./nr-gnb -c ../config/open5gs-gnb.yaml
  2. UERANSIM v3.2.6
  3. [2024-03-29 19:14:15.643] [sctp] [info] Trying to establish SCTP connection... (192.168.0.111:38412)
  4. [2024-03-29 19:14:15.656] [sctp] [info] SCTP connection established (192.168.0.111:38412)
  5. [2024-03-29 19:14:15.657] [sctp] [debug] SCTP association setup ascId[20]
  6. [2024-03-29 19:14:15.657] [ngap] [debug] Sending NG Setup Request
  7. [2024-03-29 19:14:15.675] [ngap] [debug] NG Setup Response received
  8. [2024-03-29 19:14:15.675] [ngap] [info] NG Setup procedure is successful

The Open5GS C-Plane log when executed is as follows.

  1. 03/29 19:14:15.672: [amf] INFO: gNB-N2 accepted[192.168.0.131]:42377 in ng-path module (../src/amf/ngap-sctp.c:113)
  2. 03/29 19:14:15.672: [amf] INFO: gNB-N2 accepted[192.168.0.131] in master_sm module (../src/amf/amf-sm.c:754)
  3. 03/29 19:14:15.688: [amf] INFO: [Added] Number of gNBs is now 1 (../src/amf/context.c:1236)
  4. 03/29 19:14:15.689: [amf] INFO: gNB-N2[192.168.0.131] max_num_of_ostreams : 10 (../src/amf/amf-sm.c:793)

Start UE (UE0)

Start UE (UE0) as follows. This will register the UE with 5GC and establish a PDU session.

  1. # ./nr-ue -c ../config/open5gs-ue0.yaml 
  2. UERANSIM v3.2.6
  3. [2024-03-29 19:15:04.380] [nas] [info] UE switches to state [MM-DEREGISTERED/PLMN-SEARCH]
  4. [2024-03-29 19:15:04.381] [rrc] [debug] New signal detected for cell[1], total [1] cells in coverage
  5. [2024-03-29 19:15:04.382] [nas] [info] Selected plmn[001/01]
  6. [2024-03-29 19:15:04.383] [rrc] [info] Selected cell plmn[001/01] tac[1] category[SUITABLE]
  7. [2024-03-29 19:15:04.384] [nas] [info] UE switches to state [MM-DEREGISTERED/PS]
  8. [2024-03-29 19:15:04.384] [nas] [info] UE switches to state [MM-DEREGISTERED/NORMAL-SERVICE]
  9. [2024-03-29 19:15:04.385] [nas] [debug] Initial registration required due to [MM-DEREG-NORMAL-SERVICE]
  10. [2024-03-29 19:15:04.389] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
  11. [2024-03-29 19:15:04.390] [nas] [debug] Sending Initial Registration
  12. [2024-03-29 19:15:04.390] [rrc] [debug] Sending RRC Setup Request
  13. [2024-03-29 19:15:04.391] [nas] [info] UE switches to state [MM-REGISTER-INITIATED]
  14. [2024-03-29 19:15:04.393] [rrc] [info] RRC connection established
  15. [2024-03-29 19:15:04.393] [rrc] [info] UE switches to state [RRC-CONNECTED]
  16. [2024-03-29 19:15:04.394] [nas] [info] UE switches to state [CM-CONNECTED]
  17. [2024-03-29 19:15:04.422] [nas] [debug] Authentication Request received
  18. [2024-03-29 19:15:04.422] [nas] [debug] Received SQN [000000000341]
  19. [2024-03-29 19:15:04.423] [nas] [debug] SQN-MS [000000000000]
  20. [2024-03-29 19:15:04.440] [nas] [debug] Security Mode Command received
  21. [2024-03-29 19:15:04.440] [nas] [debug] Selected integrity[2] ciphering[0]
  22. [2024-03-29 19:15:04.485] [nas] [debug] Registration accept received
  23. [2024-03-29 19:15:04.485] [nas] [info] UE switches to state [MM-REGISTERED/NORMAL-SERVICE]
  24. [2024-03-29 19:15:04.485] [nas] [debug] Sending Registration Complete
  25. [2024-03-29 19:15:04.486] [nas] [info] Initial Registration is successful
  26. [2024-03-29 19:15:04.486] [nas] [debug] Sending PDU Session Establishment Request
  27. [2024-03-29 19:15:04.487] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
  28. [2024-03-29 19:15:04.693] [nas] [debug] Configuration Update Command received
  29. [2024-03-29 19:15:04.755] [nas] [debug] PDU Session Establishment Accept received
  30. [2024-03-29 19:15:04.761] [nas] [info] PDU Session establishment is successful PSI[1]
  31. [2024-03-29 19:15:04.809] [app] [info] Connection setup for PDU session[1] is successful, TUN interface[uesimtun0, 10.45.0.2] is up.

The Open5GS C-Plane log when executed is as follows.

  1. 03/29 19:15:04.397: [amf] INFO: InitialUEMessage (../src/amf/ngap-handler.c:401)
  2. 03/29 19:15:04.397: [amf] INFO: [Added] Number of gNB-UEs is now 1 (../src/amf/context.c:2656)
  3. 03/29 19:15:04.397: [amf] INFO:     RAN_UE_NGAP_ID[1] AMF_UE_NGAP_ID[1] TAC[1] CellID[0x10] (../src/amf/ngap-handler.c:562)
  4. 03/29 19:15:04.398: [amf] INFO: [suci-0-001-01-0000-0-0-0000000000] Unknown UE by SUCI (../src/amf/context.c:1840)
  5. 03/29 19:15:04.398: [amf] INFO: [Added] Number of AMF-UEs is now 1 (../src/amf/context.c:1621)
  6. 03/29 19:15:04.398: [gmm] INFO: Registration request (../src/amf/gmm-sm.c:1224)
  7. 03/29 19:15:04.398: [gmm] INFO: [suci-0-001-01-0000-0-0-0000000000]    SUCI (../src/amf/gmm-handler.c:172)
  8. 03/29 19:15:04.405: [sbi] WARNING: [UDM] (NRF-discover) NF has already been added [106a8792-edb5-41ee-901e-57e68da538eb:1] (../lib/sbi/nnrf-handler.c:1162)
  9. 03/29 19:15:04.406: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.12:80] (../lib/sbi/context.c:2210)
  10. 03/29 19:15:04.406: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.12:7777] (../lib/sbi/context.c:1946)
  11. 03/29 19:15:04.407: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.12:7777] (../lib/sbi/context.c:1946)
  12. 03/29 19:15:04.408: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.12:7777] (../lib/sbi/context.c:1946)
  13. 03/29 19:15:04.408: [sbi] INFO: [UDM] (NF-discover) NF Profile updated [106a8792-edb5-41ee-901e-57e68da538eb:1] (../lib/sbi/nnrf-handler.c:1200)
  14. 03/29 19:15:04.418: [sbi] INFO: [UDM] (SCP-discover) NF registered [106a8792-edb5-41ee-901e-57e68da538eb:1] (../lib/sbi/path.c:211)
  15. 03/29 19:15:04.477: [sbi] WARNING: [UDR] (NRF-discover) NF has already been added [1071b454-edb5-41ee-acea-637fa974d3e9:1] (../lib/sbi/nnrf-handler.c:1162)
  16. 03/29 19:15:04.478: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.20:80] (../lib/sbi/context.c:2210)
  17. 03/29 19:15:04.478: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.20:7777] (../lib/sbi/context.c:1946)
  18. 03/29 19:15:04.478: [sbi] INFO: [UDR] (NF-discover) NF Profile updated [1071b454-edb5-41ee-acea-637fa974d3e9:1] (../lib/sbi/nnrf-handler.c:1200)
  19. 03/29 19:15:04.481: [sbi] INFO: [UDR] (SCP-discover) NF registered [1071b454-edb5-41ee-acea-637fa974d3e9:1] (../lib/sbi/path.c:211)
  20. 03/29 19:15:04.691: [gmm] INFO: [imsi-001010000000000] Registration complete (../src/amf/gmm-sm.c:2321)
  21. 03/29 19:15:04.692: [amf] INFO: [imsi-001010000000000] Configuration update command (../src/amf/nas-path.c:591)
  22. 03/29 19:15:04.693: [gmm] INFO:     UTC [2024-03-29T10:15:04] Timezone[0]/DST[0] (../src/amf/gmm-build.c:558)
  23. 03/29 19:15:04.693: [gmm] INFO:     LOCAL [2024-03-29T19:15:04] Timezone[32400]/DST[0] (../src/amf/gmm-build.c:563)
  24. 03/29 19:15:04.695: [amf] INFO: [Added] Number of AMF-Sessions is now 1 (../src/amf/context.c:2677)
  25. 03/29 19:15:04.695: [gmm] INFO: UE SUPI[imsi-001010000000000] DNN[internet] S_NSSAI[SST:1 SD:0xffffff] smContextRef [NULL] (../src/amf/gmm-handler.c:1285)
  26. 03/29 19:15:04.696: [gmm] INFO: SMF Instance [107d70f0-edb5-41ee-8d98-11ef17677feb] (../src/amf/gmm-handler.c:1324)
  27. 03/29 19:15:04.700: [smf] INFO: [Added] Number of SMF-UEs is now 1 (../src/smf/context.c:1019)
  28. 03/29 19:15:04.701: [smf] INFO: [Added] Number of SMF-Sessions is now 1 (../src/smf/context.c:3090)
  29. 03/29 19:15:04.706: [sbi] WARNING: [UDM] (NRF-discover) NF has already been added [106a8792-edb5-41ee-901e-57e68da538eb:1] (../lib/sbi/nnrf-handler.c:1162)
  30. 03/29 19:15:04.707: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.12:80] (../lib/sbi/context.c:2210)
  31. 03/29 19:15:04.708: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.12:7777] (../lib/sbi/context.c:1946)
  32. 03/29 19:15:04.709: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.12:7777] (../lib/sbi/context.c:1946)
  33. 03/29 19:15:04.709: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.12:7777] (../lib/sbi/context.c:1946)
  34. 03/29 19:15:04.709: [sbi] INFO: [UDM] (NF-discover) NF Profile updated [106a8792-edb5-41ee-901e-57e68da538eb:1] (../lib/sbi/nnrf-handler.c:1200)
  35. 03/29 19:15:04.719: [sbi] INFO: [UDM] (SCP-discover) NF registered [106a8792-edb5-41ee-901e-57e68da538eb:1] (../lib/sbi/path.c:211)
  36. 03/29 19:15:04.724: [sbi] WARNING: [PCF] (NRF-discover) NF has already been added [1071741c-edb5-41ee-9bbc-47729d50ab25:1] (../lib/sbi/nnrf-handler.c:1162)
  37. 03/29 19:15:04.725: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.13:80] (../lib/sbi/context.c:2210)
  38. 03/29 19:15:04.726: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.13:7777] (../lib/sbi/context.c:1946)
  39. 03/29 19:15:04.726: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.13:7777] (../lib/sbi/context.c:1946)
  40. 03/29 19:15:04.727: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.13:7777] (../lib/sbi/context.c:1946)
  41. 03/29 19:15:04.727: [sbi] INFO: [PCF] (NF-discover) NF Profile updated [1071741c-edb5-41ee-9bbc-47729d50ab25:1] (../lib/sbi/nnrf-handler.c:1200)
  42. 03/29 19:15:04.732: [sbi] WARNING: [UDR] (NRF-discover) NF has already been added [1071b454-edb5-41ee-acea-637fa974d3e9:1] (../lib/sbi/nnrf-handler.c:1162)
  43. 03/29 19:15:04.733: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.20:80] (../lib/sbi/context.c:2210)
  44. 03/29 19:15:04.733: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.20:7777] (../lib/sbi/context.c:1946)
  45. 03/29 19:15:04.734: [sbi] INFO: [UDR] (NF-discover) NF Profile updated [1071b454-edb5-41ee-acea-637fa974d3e9:1] (../lib/sbi/nnrf-handler.c:1200)
  46. 03/29 19:15:04.737: [sbi] WARNING: [UDR] (SCP-discover) NF has already been added [1071b454-edb5-41ee-acea-637fa974d3e9:2] (../lib/sbi/path.c:216)
  47. 03/29 19:15:04.740: [sbi] WARNING: [BSF] (NRF-discover) NF has already been added [106ac766-edb5-41ee-ac23-695413178af1:1] (../lib/sbi/nnrf-handler.c:1162)
  48. 03/29 19:15:04.741: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.15:80] (../lib/sbi/context.c:2210)
  49. 03/29 19:15:04.741: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.15:7777] (../lib/sbi/context.c:1946)
  50. 03/29 19:15:04.741: [sbi] INFO: [BSF] (NF-discover) NF Profile updated [106ac766-edb5-41ee-ac23-695413178af1:1] (../lib/sbi/nnrf-handler.c:1200)
  51. 03/29 19:15:04.744: [sbi] INFO: [BSF] (SCP-discover) NF registered [106ac766-edb5-41ee-ac23-695413178af1:1] (../lib/sbi/path.c:211)
  52. 03/29 19:15:04.747: [sbi] INFO: [PCF] (SCP-discover) NF registered [1071741c-edb5-41ee-9bbc-47729d50ab25:1] (../lib/sbi/path.c:211)
  53. 03/29 19:15:04.748: [smf] INFO: UE SUPI[imsi-001010000000000] DNN[internet] IPv4[10.45.0.2] IPv6[] (../src/smf/npcf-handler.c:542)
  54. 03/29 19:15:04.750: [gtp] INFO: gtp_connect() [192.168.0.112]:2152 (../lib/gtp/path.c:60)
  55. 03/29 19:15:04.762: [sbi] WARNING: [UDM] (NRF-discover) NF has already been added [106a8792-edb5-41ee-901e-57e68da538eb:1] (../lib/sbi/nnrf-handler.c:1162)
  56. 03/29 19:15:04.763: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.12:80] (../lib/sbi/context.c:2210)
  57. 03/29 19:15:04.763: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.12:7777] (../lib/sbi/context.c:1946)
  58. 03/29 19:15:04.764: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.12:7777] (../lib/sbi/context.c:1946)
  59. 03/29 19:15:04.764: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.12:7777] (../lib/sbi/context.c:1946)
  60. 03/29 19:15:04.764: [sbi] INFO: [UDM] (NF-discover) NF Profile updated [106a8792-edb5-41ee-901e-57e68da538eb:1] (../lib/sbi/nnrf-handler.c:1200)
  61. 03/29 19:15:04.768: [sbi] WARNING: [UDM] (SCP-discover) NF has already been added [106a8792-edb5-41ee-901e-57e68da538eb:2] (../lib/sbi/path.c:216)
  62. 03/29 19:15:04.770: [amf] INFO: [imsi-001010000000000:1:11][0:0:NULL] /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify (../src/amf/nsmf-handler.c:867)

The Open5GS U-Plane1 log when executed is as follows.

  1. 03/29 19:15:04.743: [upf] INFO: [Added] Number of UPF-Sessions is now 1 (../src/upf/context.c:208)
  2. 03/29 19:15:04.744: [gtp] INFO: gtp_connect() [192.168.0.111]:2152 (../lib/gtp/path.c:60)
  3. 03/29 19:15:04.744: [upf] INFO: UE F-SEID[UP:0x57e CP:0x6bd] APN[internet] PDN-Type[1] IPv4[10.45.0.2] IPv6[] (../src/upf/context.c:485)
  4. 03/29 19:15:04.744: [upf] INFO: UE F-SEID[UP:0x57e CP:0x6bd] APN[internet] PDN-Type[1] IPv4[10.45.0.2] IPv6[] (../src/upf/context.c:485)
  5. 03/29 19:15:04.754: [gtp] INFO: gtp_connect() [192.168.0.131]:2152 (../lib/gtp/path.c:60)

Looking at the console log of the nr-ue command, UE0 has been assigned the IP address 10.45.0.2 from Open5GS 5GC.

  1. [2024-03-29 19:15:04.809] [app] [info] Connection setup for PDU session[1] is successful, TUN interface[uesimtun0, 10.45.0.2] is up.

Just in case, make sure it matches the IP address of the UE0’s TUNnel interface.

  1. # ip addr show
  2. ...
  3. 21: uesimtun0: <POINTOPOINT,PROMISC,NOTRAILERS,UP,LOWER_UP> mtu 1400 qdisc fq_codel state UNKNOWN group default qlen 500
  4.     link/none 
  5.     inet 10.45.0.2/32 scope global uesimtun0
  6.        valid_lft forever preferred_lft forever
  7.     inet6 fe80::3d90:4d95:c73e:89da/64 scope link stable-privacy 
  8.        valid_lft forever preferred_lft forever
  9. ...

Ping google.com

Specify the UE0’s TUNnel interface and try ping.

Please refer to the following for usage of TUNnel interface.

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

Case for going through DN 10.45.0.0/16

Execute tcpdump on VM2 (U-Plane1) and check that the packet goes through if=ogstun.

  • ping google.com on VM5 (UE0)
    1. # ping google.com -I uesimtun0 -n
    2. PING google.com (172.217.26.238) from 10.45.0.2 uesimtun0: 56(84) bytes of data.
    3. 64 bytes from 172.217.26.238: icmp_seq=1 ttl=61 time=24.8 ms
    4. 64 bytes from 172.217.26.238: icmp_seq=2 ttl=61 time=29.5 ms
    5. 64 bytes from 172.217.26.238: icmp_seq=3 ttl=61 time=20.8 ms
  • Run tcpdump on VM2 (U-Plane1)
    1. # tcpdump -i ogstun -n
    2. tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    3. listening on ogstun, link-type RAW (Raw IP), capture size 262144 bytes
    4. 19:17:14.619358 IP 10.45.0.2 > 172.217.26.238: ICMP echo request, id 13, seq 1, length 64
    5. 19:17:14.641298 IP 172.217.26.238 > 10.45.0.2: ICMP echo reply, id 13, seq 1, length 64
    6. 19:17:15.620458 IP 10.45.0.2 > 172.217.26.238: ICMP echo request, id 13, seq 2, length 64
    7. 19:17:15.647406 IP 172.217.26.238 > 10.45.0.2: ICMP echo reply, id 13, seq 2, length 64
    8. 19:17:16.621402 IP 10.45.0.2 > 172.217.26.238: ICMP echo request, id 13, seq 3, length 64
    9. 19:17:16.639589 IP 172.217.26.238 > 10.45.0.2: ICMP echo reply, id 13, seq 3, length 64

You could specify the IP address assigned to the TUNnel interface to run almost any applications (iperf3 etc.) as in the following example using nr-binder tool.

  • curl google.com on VM5 (UE0)
    1. # sh nr-binder 10.45.0.2 curl google.com
    2. <HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
    3. <TITLE>301 Moved</TITLE></HEAD><BODY>
    4. <H1>301 Moved</H1>
    5. The document has moved
    6. <A HREF="http://www.google.com/">here</A>.
    7. </BODY></HTML>
  • Run tcpdump on VM2 (U-Plane1)
    1. 19:18:10.546698 IP 10.45.0.2.44451 > 172.217.26.238.80: Flags [S], seq 3582922701, win 65280, options [mss 1360,sackOK,TS val 3395679140 ecr 0,nop,wscale 7], length 0
    2. 19:18:10.563086 IP 172.217.26.238.80 > 10.45.0.2.44451: Flags [S.], seq 13760001, ack 3582922702, win 65535, options [mss 1460], length 0
    3. 19:18:10.565440 IP 10.45.0.2.44451 > 172.217.26.238.80: Flags [.], ack 1, win 65280, length 0
    4. 19:18:10.565708 IP 10.45.0.2.44451 > 172.217.26.238.80: Flags [P.], seq 1:75, ack 1, win 65280, length 74: HTTP: GET / HTTP/1.1
    5. 19:18:10.565876 IP 172.217.26.238.80 > 10.45.0.2.44451: Flags [.], ack 75, win 65535, length 0
    6. 19:18:10.626697 IP 172.217.26.238.80 > 10.45.0.2.44451: Flags [P.], seq 1:774, ack 75, win 65535, length 773: HTTP: HTTP/1.1 301 Moved Permanently
    7. 19:18:10.629617 IP 10.45.0.2.44451 > 172.217.26.238.80: Flags [.], ack 774, win 64507, length 0
    8. 19:18:10.632064 IP 10.45.0.2.44451 > 172.217.26.238.80: Flags [F.], seq 75, ack 774, win 64507, length 0
    9. 19:18:10.632358 IP 172.217.26.238.80 > 10.45.0.2.44451: Flags [.], ack 76, win 65535, length 0
    10. 19:18:10.649379 IP 172.217.26.238.80 > 10.45.0.2.44451: Flags [F.], seq 774, ack 76, win 65535, length 0
    11. 19:18:10.651794 IP 10.45.0.2.44451 > 172.217.26.238.80: Flags [.], ack 775, win 64507, length 0
    Please note that the ping tool does not work with nr-binder. Please refer to here for the reason.

For UE1-UE4 as well, execute tcpdump on each U-Plane and check the packets flowing through ogstunX.

You could now create the end-to-end TUN interfaces on the DN and send any packets on the network.

In investigating 5G SA, I have built a simulation environment and can now use a very useful system for investigating 5GC and MEC of 5G SA mobile network. I would like to thank the excellent developers and all the contributors of Open5GS and UERANSIM.

Changelog (summary)

  • [2024.03.31] This commit fixed the issue where SMF crashes without gtpc section in smf.yaml. So deleted the gtpc section in smf.yaml for 5G use.
  • [2024.03.29] Updated to Open5GS v2.7.0 (2024.03.24).
  • [2023.01.12] Updated to Open5GS v2.5.6.
  • [2022.06.05] Updated to Open5GS v2.4.7 and UERANSIM v3.2.6.
  • [2021.08.29] Updated to Open5GS v2.3.3 and added a little about BSF. And updated to UERANSIM v3.2.3.
  • [2021.03.09] Updated to Open5GS v2.2.0 and added a little about NSSF. And updated to UERANSIM v3.1.3.
  • [2021.01.28] Updated to UERANSIM v3.0.1 and updated the operation procedure.
  • [2020.12.23] Updated to UERANSIM v2.2.1 and updated the operation procedure.
  • [2020.12.20] Updated to UERANSIM v2.1.1.
  • [2020.12.14] Updated to UERANSIM v2.0.1 and updated the operation procedure.
  • [2020.12.13] Updated to Open5GS v2.1.0 and added a little about PCF.
  • [2020.11.29] Initial release.