5G Core Network Setup

Introduction

A 5G network can contain the following products: YateNRF, YateUDM and YateUCN5G.

  • YateNRF is equivalent of YateSTP or YateDRA for 5G networks.
  • YateUDM is equivalent of YateHSS/HLR for 5G networks. YateUDM has similar features like YateHSS/HLR. It allows SS7 Support and Diameter support, but more than an usual YateHSS/HLR, the YateUDM allows 5G support. When this new feature is disabled your YateUDM works like an YateHSS/HLR, but when 5G support feature is enable two more wizard steps will be displayed: CAPIF and UDM/AUSF settings.
  • YateUCN5G is like an YateUCN but with some new features. YateUCN5G allows: SMF support, AMF support and SMSF support. If these new features are disabled, your YateUCN5G works like an YateUCN. But when at least one of these features is enabled some new wizards are displayed. These new wazards are: CAPIF, SMF, AMF,SMSF. The CAPIF wizard is displayed when at least one of the new features is enabled.

My Network

Network settings

First, it’s important to start by checking if 5G support is activated in My Network -> Network Setting. If it isn’t, check it.

5G Core Network Setup 29

Equipment

As a tip, if your network displays the following message “You need to configure network NRF before any other network equipment.”, you should know that the 5G support is activated on your netwok.

5G Core Network Setup 30

YateNRF

As you have seen above, the first equipment that has to be added is YateNRF. Without an YateNRF already installed , you are not allowed to add the other equipment: YateUDM and YateUCN5G. 

It is mandatory to set API Root on the NRF step. This is used to create connections to NRF from other equipment.
Ex – API Root: http://localhost

Optional, you can set SEPP Base URL (ex: http://localhost). This is used to build the connection from other equipment to the SEPP of the YateNRF when SEPP support is active. If SEPP Base URL is not set, connection to SEPP will use URL set in API Root.

5G Core Network Setup 31
5G Core Network Setup 32

If you choose to enable SEPP support, two more steps will be displayed:  Route table and N32c settings that apply to SEPP node.

5G Core Network Setup 33

YateUDM

YateUDM is the equivalent of YateHSS for 5G networks. In case you disable 5G support for YateUDM the ‘CAPIF’ and ‘UDM/AUSF settings’ steps won’t be displayed, so in this scenario, your YateUDM will work like an YateHSS/HLR.

5G Core Network Setup 34

Below you can see some configurations for CAPIF and UDM/AUSF settings:

5G Core Network Setup 35
5G Core Network Setup 36

What is configured in ‘UDM/AUSF settings’ step will be set in hss config file along with the other common settings.

YateUCN5G

YateUCN5G has more functionalities than an normal YateUCN. First, you have the possibility to enable/disable SMF Support, AMF support and SMSF support. If you have at least one of these features enabled, the CAPIF tab will be displayed.
If you have  SMF Support, AMF Support and SMSF Support disabled, your YateUCN5G will work like an YateUCN and CAPIF, AMF, SMF and SMSF steps will be hidden.

When a feature support is disabled, any previous configuration for that feature will also be deleted from equipment.

5G Core Network Setup 37

Also, you have the possibility to disable these features from each step (SMF, AMF, SMSF) using Status field. 

If feature support is active but its status (set from within the feature step) is disabled, then feature configuration won’t be deleted from equipment but it will be ignored (act as if feature is disabled).

Below you can see an example for CAPIF, SMF, AMF, SMSF fields:

5G Core Network Setup 38
5G Core Network Setup 39
5G Core Network Setup 40

NGAP SCTP Listeners 

NGAP SCTP Listeners are set in AMF step. If  AMF feature support is active and AMF module status is active, then it’s mandatory to set a NGAP SCTP Listener, otherwise an error from API will be displayed.

Default Listener status is active. On edit equipment you can disable a listener. Configuration of the disabled listeners won’t be sent to equipment.

The default value of NGAP SCTP Stream is 3. You can change this default value from NGAP SCTP Stream field, that will be applied for all the NGAP Listeners set. You can also specify a different Stream value for each Listener from NGAP Listener Advanced fields.

5G Core Network Setup 41

CAPIF

CAPIF step is displayed only if equipment has at least one 5G feature active. 
In the CAPIF step you can set:

  • Instances
  • Connections to NRF/SEPP (options are displayed based on equipment type YateNRF and the API Root set for it, respectively its SEPP)
  • Additional Connections (to nodes NRF, SEPP, AMF, SMF, SMSF, AUSF, UDM)
Instances


In ‘Common CAPIF settings’ you set the common values for all the instances (these values can be also set for each instance). 
Instances types are based on equipment type:

  • YateUCN5G: AMF, SMF, SMSF
  • YateUDM: AUSF, UDM

Node instance identifier can be generated by clicking on ‘Generate Instance value (UUID V4)’ (this must be unique). 
‘Register to NRF’ is a parameter with bool value. The ‘default’ option in each Instance for this field, is the value set above in Common CAPIF settings.
Do not set URL suffix in the ‘Base URL’ field, mention it separately in ‘URL suffix’ field. The default URL suffix is ‘capif.php’.

5G Core Network Setup 42

Connections to YateNRF

Connection to NRF

Connection between other 5G equipment and YateNRF can be built as follows:

  1. automatically when adding a YateNRF equipment (if other 5G equipment are already configured)
        – by checking the “Auto generate connection to it from all equipment” field and specifying the “API root” in NRF step

  2. from CAPIF step of each 5G equipment
    a. by using “Connections to YateNRF/SEPP”
        – check/choose connection to desired YateNRF
           (This option is available only if “API root” parameter was previously set in YateNRF equipment)
    b. by using “Additional Connection”
        – add connection selecting ‘NRF’ node type and specifying the ‘Base URL’
           (Pay attention to advanced fields with default values!)

Connection to SEPP

To set a connection to the SEPP of a YateNRF the following methods can be used:
(In order to set connections to the SEPP of a YateNRF, SEPP support feature should be active.)

  1. automatically when adding a YateNRF equipment (if other 5G equipment are already configured)
        – by checking the “Auto generate connection to it from all equipment” field and specifying the “API root” or ‘SEPP Base URL’ in NRF step (connection will use the URL specified in ‘SEPP Base URL’ if present, otherwise the one set in ‘API root’ field)
  2. from CAPIF step of each 5G equipment
    a. by using “Connections to YateNRF/SEPP”
        – check/choose connection to desired SEPP
          (This option is available only if “API root”/”SEPP Base URL” parameter was previously set in YateNRF equipment)
    b. by using “Additional Connection”
        – add connection selecting ‘SEPP’ node type and specifying the ‘Base URL’
          (Pay attention to advanced fields with default values!)

Attention: “SEPP Base URL” shouldn’t contain suffix! 

Note:
By checking “Auto generate connection to it from all equipment” option, if SEPP support feature is active on YateNRF equipment, on each 5G configured equipment two connections will be automatically added: one to the SEPP and one to the NRF.  The SEPP connection will be built using ‘SEPP Base URL’ if specified, otherwise will be built using the URL specified in ‘API root’. 

Online documentation