Configuring the SEPP
This section describes how to configure SEPP.
The following conditions are applicable when you configure SEPP:
-
It's configured in the same way how you configure the other NFs, like, for example, UDM, CHF, or PCF.
-
As it's an Edge proxy and not a proper NF, it must have service lists, which are supported by a peer SMF.
-
It supports failure handling functionality using the existing nf-client failure templates, similar to the other NFs.
Configuring the SEPP nf-client
To configure a SEPP nf-client, use the sample CLI configuration only as a reference.
profile nf-client nf-type sepp
sepp-profile SEPP1
locality LOC1
service name type nsmf-pdusession
endpoint-profile EP1
capacity 50
priority 50
uri-scheme http
endpoint-name sepp-ep-1
priority 50
capacity 50
primary ip-address ipv4 xx.xx.xx.xx
primary ip-address port xxxx
exit
exit
exit
exit
exit
exit
Configuring the Network Element Profiles for a SEPP
To configure the network element profiles linked to a SEPP nf-client, use the sample CLI configuration.
profile network-element sepp nrf-nf-sepp-1
nf-client-profile SEPP1
exit
Configuring the DNN Profile for a SEPP
To configure the DNN profile for a SEPP, use the sample CLI configuration only as a reference.
network-element-profile sepp nrf-nf-sepp-1 is linked to dnn
profile dnn intershatRoamer
network-element-profiles sepp nrf-nf-sepp-1
exit
Configuring the Failure Handling for a SEPP
The SEPP supports the existing failure handling template for all the HTTP error response codes. To configure failure handling for a SEPP, use the sample configuration only as a reference.
profile nf-client-failure nf-type sepp
profile failure-handling FH-SEPP
service name type nsmf-pdusession
message type VsmfPduSessionCreate
status-code httpv2 504
retry 2
action retry-and-terminate
exit
exit
exit
exit
exit
Note | In the current release, only the retry-terminate option is supported for all the messages. |
Configuring the Failure Handling Template for hSMF/vSMF and SEPP
The peer SMF and SEPP support the failure handling template for all the HTTP error response codes. To configure failure handling for a peer SMF message, use the sample configuration only as a reference.
The following is a sample configuration for hSMF:
profile nf-client-failure nf-type sepp
profile failure-handling FHSEPP
service name type nsmf-pdusession
responsetimeout 4000
message type VsmfPduSessionUpdate
status-code httpv2 500-599
retry 3
action retry-and-terminate
exit
exit
message type VsmfPduSessionNotify
status-code httpv2 400-599
retry 3
action retry-and-terminate
exit
exit
exit
exit
exit
The following is a sample configuration for vSMF:
profile nf-client-failure nf-type sepp
profile failure-handling sepp
service name type nsmf-pdusession
responsetimeout 4000
message type HsmfPduSessionCreate
status-code httpv2 400-599
retry 3
action retry-and-terminate
exit
exit
message type HsmfPduSessionUpdate
status-code httpv2 500-599
retry 3
action retry-and-terminate
exit
exit
message type HsmfPduSessionRelease
status-code httpv2 504
retry 3
action retry-and-terminate
exit
exit
exit
exit
exit
Note | The sample configurations use the nf-type SEPP. You can use the same for nf-type SMF. |
Configuring the Failure Handling Template with Alternate hSMF
If there is failure from a primary hSMF, vSMF tries the alternate hSMF. SMF service sends the alternate hSMF details to Rest Endpoint (rest-ep) and SMF gets alternate HSM details from AMF. Based on the N26 failure handling configuration, an alternate hSMF is selected.
Alternate hSMF is selected only if retry is configured for.pduSessionCreate
Note | smf-service includes listalternate-hsmf in the discoveryParams to Rest Endpoint. |
Based on the N26 failure handling configuration, an alternate hSMF is selected.
Rest-ep or NfLib sends the selected alternate hSMF back to service and vSMF sends this back to AMF. vSMF displays SelectedSmfId in smContextCreatedData.
Configuration Example:
The following is an example configuration:
[smf] smf(config)# profile nf-client-failure nf-type n16smf
smf] smf(config-n16smf)# profile failure-handling fh
[smf] smf(config-failure-handling-fh)# service name type nsmf-pdusession
[smf] smf(config-type-nsmf-pdusession)# message type [ PduSessionCreate ] status-code httpv2 <0-599>
[smf] smf(config-httpv2-400)# action [continue retry-and-continue retry-and-ignore retry-and-terminate terminate]
[smf] smf(config-httpv2-400)# retry <1-10>
Configuring the SMF NRF Registration
To configure the SMF NRF registration, use the sample configuration only as a reference.
profile smf smf1 instances
instances 1 fqdn 5gc.mnc456.mnc123.3gppnetwork.org
instances 1 inter-plmn-fqdn 5gc.mnc456.mnc123.3gppnetwork.org
instances 1 supported-features [ vsmf ]
Note | In the current release, for the SMF to register with an NRF, the inter-plmn-fqdn and vsmf-supported IEs are included for the SMF discovery. The configuration for vsmfSupportIndicator must be added on vSMF along with inter-plmn-fqdn. This configuration is required for vAMF to find a vSMF, which supports roaming. |
To undo the configuration for vsmfSupportIndicator, use the following sample configuration:
smf] smf(config-smf-smf1)# no instances 1 supported-features
[smf] smf(config-smf-smf1)# commit