4 Benchmarking SCP Model D

This section describes Model D test topologies and test scenarios for benchmarking SCP.

4.1 Model D Call Flow

The following call flow represents how a service request is processed by SCP.

  1. Consumer NF sends the service request to SCP with discovery parameters.
  2. SCP sends the discovery request to NRF with the received discovery parameters.
  3. NRF responds with the NF profile list that contains information about the preferred producer NFs.
  4. SCP sends the request to the producer NF based on the NF profile list received from NRF.
  5. Producer NF sends the response to SCP for the service request.
  6. SCP routes the response received from the producer NF to the consumer NF.

Figure 4-1 Model D Call Flow


Model D Call Flow

4.1.1 Model D Traffic Distribution

The following table describes the percentage of messages processed by SCP using N11, N7, N10, N36, N28, and so on interfaces.

Table 4-1 Model D Traffic Distribution

NF-C NF-P Interface Reference NF Service Percentage (%) of Messages
AMF SMF N11 nsmf-pdusession 50.00
SMF PCF N7

npcf-smpolicycontrol

 30.00
SMF UDM N10
  • nudm-sdm
  • nudm-uecm
 10.90
PCF UDR N36

nudr-dr

 0.40
PCF CHF N28 nchf-spendinglimitcontrol 0.40
PCF BSF Nbsf nbsf-management 0.30
AMF UDM N8
  • nudm-sdm
  • nudm-uecm
 2.50
AMF AUSF N12 nausf-auth 2.50
AMF PCF N15
  • npcf-ue-policy-control
  • npcf-am-policy-control
 3.00

Routing Configuration

The following table describes the routing configurations for the NF services.

Table 4-2 Routing Configuration

NF Service Initial Message Subsequent Message reverseProxySupport Deployment ResponseTimeout
    routePolicy reroutePolicy routePolicy reroutePolicy      
SMF Nsmf_PDUSession Load_Balance RerouteWithinRegion Load_Balance RerouteWithinRegion False REGIONAL 1s
PCF Npcf_SMPolicyControl Load_Balance RerouteWithinRegion Load_Balance RerouteWithinRegion False REGIONAL 1s
UDR Nudr_dm Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
CHF Nchf_SpendingLimitControl Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
UDM Nudm_sdm Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
UDM Nudm_uecm Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
PCF Npcf_AMPolicyControl Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
PCF Npcf_UEPolicyControl Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
AUSF Nausf_UEAuthentication Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
BSF Nbsf_management Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
UDR Nudr_udrService Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s

NF Profiles

The following table describes NF profile configuration, traffic, and message call flows for 176 NF profiles registered on SCP.

Table 4-3 NF Profiles

NF-C NF-P Interfaces Supported Services Service-related traffic Profiles Registered NF Range Message Call flows Discover parameters (Delegated Discovery)
AMF SMF N11
  • nsmf-pdusession
  • nsmf-event-exposure
 nsmf-pdusession 80 SMF1 to SMF80
  • Create PDU session
  • Modify PDU session
  • Release PDU session
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-Discovery-Snssais
  • 3gpp-Sbi-Discovery-dnn
  • 3gpp-Sbi-Discovery-tai
  • 3gpp-Sbi-Discovery-service-names
AMF PCF N15
  • npcf-am-policy-control
  • npcf-smpolicycontrol
  • npcf-policyauthorization
  • npcf-bdtpolicycontrol
  • npcf-ue-policy-control
  • npcf-ue-policy-control
  • npcf-am-policy-control
 12 PCF1 to PCF12

Npcf_AMPolicyControl

  • Create AM Policy Association
  • Retrieve SM Policy
  • Update Policy
  • Policy Update Notification

Npcf_UEPolicyControl

  • Create Policy Association
  • Retrieve Policy Association
  • Update Policy Association
  • Policy Update Notification
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-snssais
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions
  • 3gpp-Sbi-Discovery-service-names
SMF PCF N7
  • npcf-am-policy-control
  • npcf-smpolicycontrol
  • npcf-policyauthorization
  • npcf-bdtpolicycontrol
  • npcf-ue-policy-control
 npcf-smpolicycontrol 38 PCF13 to PCF50
  • Create SM Policy
  • Update SM Policy
  • Delete SM Policy
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-snssais
  • 3gpp-Sbi-discovery-dnn
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions
SMF UDM N10
  • nudm-ueau
  • nudm-uecm
  • nudm-sdm
  • nudm-ee
  • nudm-pp
  • nudm-sdm
  • nudm-uecm
 3 UDM1 to UDM3

Nudm_sdm

  • Subscribe to Notifications
  • Data Change Notification
  • Unsubscribe from Notifications

Nudm_uecm

  • Register SMF
  • Deregister SMF
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions
  • 3gpp-sbi-discovery-supi
  • 3gpp-sbi-discovery-group-id-list
AMF UDM N8
  • nudm-ueau
  • nudm-uecm
  • nudm-sdm
  • nudm-ee
  • nudm-pp
  • nudm-sdm
  • nudm-uecm
 3 UDM4 to UDM6

Nudm_sdm

  • Subscribe to Notifications
  • Data Change Notification
  • Unsubscribe from Notifications

Nudm_uecm

  • Register AMF
  • Deregister AMF
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions
  • 3gpp-sbi-discovery-supi
  • 3gpp-sbi-discovery-group-id-list
PCF UDR N36
  • nudr-dr
  • nudr-group-id-map
 nudr-dr 10 UDR1 to UDR10
  • Create Policy Data Subscription
  • Delete Policy Data Subscription
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions
  • 3gpp-sbi-discovery-supi
  • 3gpp-Sbi-Discovery-data-set
PCF CHF N28
  • nchf-spendinglimitcontrol
  • nchf-convergedcharging
 nchf-spendinglimitcontrol 10 CHF1 to CHF10
  • Subscribe to notification
  • Cancel an existing subscription
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions
AMF AUSF N12
  • nausf-auth
  • nausf-sorprotection
  • nausf-upuprotection
 nausf-auth 10 AUSF1 to AUSF10 Authenticate UE
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions
PCF BSF Nbsf nbsf-management nbsf-management 10 BSF1 to BSF10
  • Register the session binding information
  • Retrieve the session binding information
  • Remove an existing session binding
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions
  

4.2 Test Topology 1 for SCP Model D Benchmarking

The following image represents the test topology consisting of the following components:

  • SCP

  • Consumer NF test simulator
  • Producer NF test simulator
  • NRF simulator

Figure 4-2 SCP Model D Topology


SCP Model D Topology

The aforementioned image represents the Model D test topology. In Release 16 Model D indirect 5G SBI communication with delegated discovery mode, the consumer NF delegates the producer NF discovery procedure to SCP by adding discovery parameters to the service requests. SCP performs NF discovery with NRF using the received discovery parameters and sends the request to the producer NF based on the NF profile list received from NRF.

4.2.1 Topology 1 Traffic Distribution

The following table describes the percentage of messages processed by SCP using N11, N7, N10, N36, N28, and so on interfaces:

Table 4-4 Topology 1 Traffic Distribution

NF-C NF-P Interface Reference NF Service Percentage (%) of Messages
AMF SMF N11 nsmf-pdusession 50.00%
SMF PCF N7

npcf-smpolicycontrol

 30.00%
SMF UDM N10
  • nudm-sdm
  • nudm-uecm
 10.90%
PCF UDR N36

nudr-dr

 0.40%
PCF CHF N28 nchf-spendinglimitcontrol 0.40%
PCF BSF Nbsf nbsf-management 0.30%
AMF UDM N8
  • nudm-sdm
  • nudm-uecm
 2.50%
AMF AUSF N12 nausf-auth 2.50%
AMF PCF N15
  • npcf-ue-policy-control
  • npcf-am-policy-control
 3.00%

Topology 1 Routing Configuration

The following table describes the routing configurations for the NF services:

Table 4-5 Routing Configuration

NF Service Initial Message Subsequent Message reverseProxySupport Deployment ResponseTimeout
    routePolicy reroutePolicy routePolicy routePolicy      
SMF Nsmf_PDUSession Load_Balance RerouteWithinRegion Load_Balance RerouteWithinRegion False REGIONAL 1s
PCF Npcf_SMPolicyControl Load_Balance RerouteWithinRegion Load_Balance RerouteWithinRegion False REGIONAL 1s
UDR Nudr_dm Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
CHF Nchf_SpendingLimitControl Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
UDM Nudm_sdm Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
UDM Nudm_uecm Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
PCF Npcf_AMPolicyControl Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
PCF Npcf_UEPolicyControl Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
AUSF Nausf_UEAuthentication Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
BSF Nbsf_management Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
UDR Nudr_udrService Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s

Topology 1 NF Profiles

The following table describes NF profile configuration, traffic, and message call flows for 176 NF profiles registered on SCP:

Table 4-6 NF Profiles

NF-C NF-P Interfaces Supported Services Service-related traffic Profiles Registered NF Range Message Call flows Discover parameters (Delegated Discovery)
AMF SMF N11
  • nsmf-pdusession
  • nsmf-event-exposure
 nsmf-pdusession 80 SMF1 to SMF80
  • Create PDU session
  • Modify PDU session
  • Release PDU session
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-Discovery-Snssais
  • 3gpp-Sbi-Discovery-dnn
  • 3gpp-Sbi-Discovery-tai
  • 3gpp-Sbi-Discovery-service-names
AMF PCF N15
  • npcf-am-policy-control
  • npcf-smpolicycontrol
  • npcf-policyauthorization
  • npcf-bdtpolicycontrol
  • npcf-ue-policy-control
  • npcf-ue-policy-control
  • npcf-am-policy-control
 12 PCF1 to PCF12

Npcf_AMPolicyControl

  • Create AM Policy Association
  • Retrieve SM Policy
  • Update Policy
  • Policy Update Notification

Npcf_UEPolicyControl

  • Create Policy Association
  • Retrieve Policy Association
  • Update Policy Association
  • Policy Update Notification
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-snssais
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions
  • 3gpp-Sbi-Discovery-service-names
SMF PCF N7
  • npcf-am-policy-control
  • npcf-smpolicycontrol
  • npcf-policyauthorization
  • npcf-bdtpolicycontrol
  • npcf-ue-policy-control
 npcf-smpolicycontrol 38 PCF13 to PCF50
  • Create SM Policy
  • Update SM Policy
  • Delete SM Policy
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-snssais
  • 3gpp-Sbi-discovery-dnn
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions
SMF UDM N10
  • nudm-ueau
  • nudm-uecm
  • nudm-sdm
  • nudm-ee
  • nudm-pp
  • nudm-sdm
  • nudm-uecm
 3 UDM1 to UDM3

Nudm_sdm

  • Subscribe to Notifications
  • Data Change Notification
  • Unsubscribe from Notifications

Nudm_uecm

  • Register SMF
  • Deregister SMF
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions
  • 3gpp-sbi-discovery-supi
  • 3gpp-sbi-discovery-group-id-list
AMF UDM N8
  • nudm-ueau
  • nudm-uecm
  • nudm-sdm
  • nudm-ee
  • nudm-pp
  • nudm-sdm
  • nudm-uecm
 3 UDM4 to UDM6

Nudm_sdm

  • Subscribe to Notifications
  • Data Change Notification
  • Unsubscribe from Notifications

Nudm_uecm

  • Register AMF
  • Deregister AMF
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions
  • 3gpp-sbi-discovery-supi
  • 3gpp-sbi-discovery-group-id-list
PCF UDR N36
  • nudr-dr
  • nudr-group-id-map
 nudr-dr 10 UDR1 to UDR10
  • Create Policy Data Subscription
  • Delete Policy Data Subscription
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions
  • 3gpp-sbi-discovery-supi
  • 3gpp-Sbi-Discovery-data-set
PCF CHF N28
  • nchf-spendinglimitcontrol
  • nchf-convergedcharging
 nchf-spendinglimitcontrol 10 CHF1 to CHF10
  • Subscribe to notification
  • Cancel an existing subscription
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions
AMF AUSF N12
  • nausf-auth
  • nausf-sorprotection
  • nausf-upuprotection
 nausf-auth 10 AUSF1 to AUSF10 Authenticate UE
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions
PCF BSF Nbsf nbsf-management nbsf-management 10 BSF1 to BSF10
  • Register the session binding information
  • Retrieve the session binding information
  • Remove an existing session binding
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
  • 3gpp-Sbi-discovery-preferred-locality
  • 3gpp-Sbi-discovery-preferred-api-versions

Access Token Request Parameters

The following table lists the data set of NF instance level access token:

Table 4-7 Data Set

Data Set 1: NFtype level access token Data Set 1: NFtype level access token
nfInstanceId, nfType, targetNfType, scope, requesterSnssaiList, targetSnssaiList nfInstanceId, scope, requesterSnssaiList, targetSnssaiList, targetNfInstanceId, targetNfServiceSetId

OAuth Parameters

The following table describes the OAuth parameters and their data set:

Table 4-8 OAuth Parameters

Parameter Data Set 1 Data Set 2 Data Set 3
Average size of access token (in bytes) 500 1000 500
Average size of AccessTokenReq message sent to NRF (in bytes) 500 1000 1500
Average value of Access Token Expiry time (in hr) 1 24
  • 50% tokens: 1 hr
  • 50% tokens: 24 hr
Will the access token expiration time be the same for all access tokens or different? What are the criteria? All access tokens expire at same time All access tokens expire at same time Half of tokens expire at same time
Non-Roaming partners
Maximum number of consumer NFs using oAuth 200 100 200
Maximum number of producer NFs for which OAuth enabled 200 200 200
Average number of producer NF Types to whom each consumer NFs communicates 5 5 5
Number of NF-Sets per NF Type (Number of NF instances in a GR deployment per NF Type)
  • 3
  • 9
  • 3
  • 9
  • 3
  • 9
Max. number of slices for which token is to be granted 3 3 3
Max. number of PLMNs in local network for which token is to be granted 5 5 10
Access Token Cache Size (# of records) - Derived from (6-11) 45000 22500 99000
Roaming partners
Max. Number of roaming PLMNs 200 100 500
Call mix
Access Token Type mix
  • 33% NF Type level tokens
  • 33% NF instance level tokens
  • 50% NF Type level tokens
  • 25% NF instance level tokens
  • 50% NF Type level tokens
  • 25% NF instance level tokens

Topology 1 Notification NRF

The following table describes NF profile configuration, traffic, and message call flows for NF profiles registered on SCP:

  • Priority of NF services has changed
  • Capacity of NF services has changed
  • Priority and Capacity of NF services has changed
  • Load of NF has changed
  • Addition of SUPI range to NF
  • Addition of GPSI range to NF
  • Removed service instances from the NF profile
  • Added service instances to the NF profile

4.3 Test Topology 2 for SCP Model D Benchmarking

The following image represents the test topology consisting of the following components:

  • SCP

  • Consumer NF test simulator
  • Producer NF test simulator
  • NRF simulator

Figure 4-3 SCP Model D Topology 2


SCP Model D Topology 2

4.3.1 Topology 2 Traffic Distribution

The following table describes the percentage of messages processed by SCP:

Table 4-9 Topology 2 Traffic Distribution

NF-C NF-P Interface Reference NF Service Percentage (%) of Messages
SMF UDM N10 nudm-sdm 20%
nudm-uecm 10%
AMF UDR N8 Nudm_sdm 25%
Nudm_uecm 15%
AMF AUSF N12 Nausf-auth 5%
SMSF UDM N21 Nudm_sdm 10%
Nudm_uecm 6%
AMF 5G-EIR N17 N5g-eir_EquipmentIdentityCheck 5%
NEF AMF N51 Namf_Communication 2%
GMLC AMF NLg Namf_Location 2%
NRF SCP Notifications   10 notifications every 15 minutes

Topology 2 Routing Configuration

The following table describes the routing configurations for the NF services:

Table 4-10 Routing Configuration

NF Service Initial Message Subsequent Message reverseProxySupport Deployment ResponseTimeout
  routePolicy reroutePolicy routePolicy reroutePolicy  
UDM nudm-sdm Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
UDM nudm-uecm Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
PCF Npcf_AMPolicyControl Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
PCF Npcf_UEPolicyControl Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
AUSF Nausf_UEAuthentication Load_Balance RerouteWithinSite Forward_Route RerouteWithinSite False SITE_WIDE 1s
AMF Namf_Communication Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
AMF Namf_Location Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s
EIR N5g-eir_EquipmentIdentityCheck Load_Balance RerouteWithinSite Load_Balance RerouteWithinSite False SITE_WIDE 1s

Topology 2 NF Profiles

The following table describes NF profile configuration, traffic, and message call flows for 152 NF profiles registered on SCP:

Table 4-11 NF Profiles

NF-C NF-P Interfaces Supported Services Service-related traffic Profiles Registered NF Range Message Call flows Discover parameters(Delegated Discovery)
SMF UDM N10
  • nudm-ueau
  • nudm-uecm
  • nudm-sdm
  • nudm-ee
  • nudm-sdm
  • nudm-uecm
 66 UDM 1 to UDM 66

Nudm_sdm

  • Subscribe to Notifications
  • Modify Subscription
  • Unsubscribe from Notifications
Nudm_uecm
  • Register SMF
  • Deregister SMF
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
AMF UDM N8
  • nudm-ueau
  • nudm-uecm
  • nudm-sdm
  • nudm-ee
  • nudm-sdm
  • nudm-uecm

Nudm_sdm

  • Subscribe to Notifications
  • Retrieve Subscription Data
Nudm_uecm
  • Register AMF
  • Update Registration
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
SMSF UDM N21
  • Nudm_sdm
  • Nudm_uecm
  • Nudm_sdm
  • Nudm_uecm
  • Retrieve SMS Management Subscription Data
  • Register the serving SMSF
  • Deregister the serving SMSF
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
AMF AUSF N12
  • nausf-auth
  • nausf-sorprotection
  • nausf-upuprotection
 nausf-auth 66 AUSF 1 To AUSF 66 Authenticate UE
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
AMF 5G-EIR N17 n5g-eir-eic n5g-eir-eic 10 5G-EIR 1 to 5G-EIR 10 Retrieve the equipment status
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
NEF AMF N51 namf-comm namf-comm 10 AMF 1 to AMF 10
  • Create UE Context
  • Release UE Context
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type
GMLC AMF NLg namf-loc namf-loc
  • Provide Positioning Info
  • Cancel Notification
  • 3gpp-sbi-discovery-target-nf-type
  • 3gpp-sbi-discovery-requester-nf-type

Topology 2 Notification NRF

The following lists the notifications:

  • Priority of NF services has changed
  • Capacity of NF services has changed
  • Priority and Capacity of NF services has changed
  • Load of NF has changed
  • Addition of SUPI range to NF
  • Addition of GPSI range to NF
  • Removal of service instances from the NF profile
  • Addition of service instances to the NF profile

4.4 Model D Testcases

This section provides information about the SCP Model-D testcases.

This test scenario describes the performance and capacity of SCP with Model D and provides the benchmarking results with latency in a network.

4.4.1 Model D Testcase Summary

The following table provides a summary of the benchmark tests:

Table 4-12 Benchmark Testcase Summary

Benchmark Testcase Number Description
Model D - Testcase Scenario 1 The Model D test is based on the network latency of 150 milliseconds at the rate of 120K MPS without rate limit and 20% delegated discovery requests towards NRF.
Model D - Testcase Scenario 2 The Model D test is based on the network latency of 150 milliseconds at the rate of 120K MPS with the rate limit disabled and 20% delegated discovery sent towards NRF. The enforceReqSpecificSvcDiscovery parameter is enabled, and the delegated discovery response is received from NRF with 66 NF profiles and with a validity timer of 600 seconds and 1 second.
Model D - Testcase Scenario 3 The Model D test is based on the network latency of 150 milliseconds at the rate of 120K MPS with the rate limit disabled and 20% delegated discovery sent towards NRF. The enforceReqSpecificSvcDiscovery parameter is disabled, and the delegated discovery response is received from NRF with 66 NF profiles and with a validity timer of 600 seconds and 1 second.
Model D - Testcase Scenario 4 The Model D test is based on the network latency of 150 milliseconds at the rate of 120K MPS with the rate limit disabled and 20% delegated discovery sent towards NRF. The enforceReqSpecificSvcDiscovery parameter is disabled, and the delegated discovery response is received from NRF with 66 NF profiles and with a validity timer of 1800 seconds and 1 second.
Model D - Testcase Scenario 5 The Model D test is based on a network latency of 150 milliseconds at a rate of 186K MPS and 20% delegated discovery sent towards NRF. The enforceReqSpecificSvcDiscovery parameter is enabled, and the delegated discovery response is received from NRF with 66 NF profiles and a validity timer of 1 second.
Model D - Testcase Scenario 6 The Model D test is based on a network latency of 150 milliseconds at a rate of 186K MPS with Oauth2.0 and Cache enabled.
Model D - Testcase Scenario 7 The Model D test is based on a network latency of 150 milliseconds at a rate of 186K MPS with Oauth2.0 enabled and cache disabled.

4.4.2 Model D - Testcase Scenario 1

This is a Model D test based on the network latency of 150 milliseconds without rate limit.

Objective

This testcase scenario describes the performance and capacity of SCP with Model D. It provides the benchmarking results with latency in a network, and no rate limit is applied to the ingress and egress traffic.

The following table describes test bed configurations:

Table 4-13 Input Parameter Details

Input Parameter Details Configuration Values
Duration of Test 72 Hours
SCP Version Tag 22.3.0
Cluster Test Bed 1 - CNE on Bare Metal. For more information, see Cluster Details
Topology Topology 1. For information about topology, see Test Topology 1 for SCP Model D Benchmarking

Testcase Parameters

The following table describes the testcase parameters and their values:

Table 4-14 Testcase Parameters

Input Parameter Details Configuration Values

Maximum SCP system wide traffic rate (in MPS)

 120K MPS
Network deployment diagram Topology 1. For information about topology, see Test Topology 1 for SCP Model D Benchmarking
Mode of Network deployment (Model-C or Model-D) Model D
Number of NFs deployed in the network which SCP is supposed to learn (number of NF Profiles)
  • Number of NF instances: 176 profiles as described in Table 3-3.
  • NF Services per NF instance:
    • SMF profile has two service types such as nsmf-pdusession and nsmf-event-exposure. Each service type has one instance.
    • PCF profile has five service types such as npcf-am-policy-control, npcf-smpolicycontrol, npcf-policyauthorization, npcf-bdtpolicycontrol, npcf-ue-policy-control. Each service type has one instance.
    • UDM profile has five service types such as nudm-ueau, nudm-uecm, nudm-sdm, nudm-ee, and nudm-pp. Each service type has one instance.
    • UDR profile has two service types such as nudr-dr and nudr-group-id-map. Each service type has one instance.
    • CHF profile has two service types such as nchf-spendinglimitcontrol and nchf-convergedcharging. Each service type has one instance.
    • AUSF profile has three service types such as nausf-auth, nausf-sorprotection, and nausf-upuprotection. Each service type has one instance.
    • BSF profile has one service type such as nbsf-management. Each service type has one instance.
  • IP/FQDN per service: Each service instance has single unique IPendpoint within a service type, which is repeated across multiple service types within an NF profile.
NF Status Information
  • Add or Modify or Delete 10 notification every 15 min
  • Profile notification updates were run every 15 minutes along with traffic run
  • Notifications could come with the following updates:
    • The priority of NF services has changed.
    • The capacity of the NF services has changed.
    • The priority and capacity of NF services have changed.
    • The load of NF has changed.
    • Service instances are removed from the profiles.
    • Service instances are removed from profiles.
NF Profile - Priority, Capacity, Load value same in all services of same kind? (Yes, No) No
LAN latency in intra-SCP services and 5G NF communication (between SCP data and control plane services, SCP and other NFs ) in millisecond 150 milliseconds
WAN latency in SCP services and 5G NF communication (SCP to NFs in other regions) in millisecond 300 milliseconds
Number of SCP ingress IPs configured 1
How many connections per published IP/FQDN producers can handle? 96
Per Egress connection max traffic in MPS 400
How many connections consumer can initiate towards per SCP IP? 384
Per Ingress connection max traffic in MPS 1000
Average Request and Response message size
  • Average HTTP Request Packet Size: 4000 Bytes
  • Average HTTP Response Packet Size: 4500 Bytes
Percentage of alternate routed requests to NF due to any reason (2% to 5%) 2%
Configured audit interval and audit mode
  • Configured Audit Interval: 3600 seconds
  • Configured Audit Mode: nnrf-mgmt
Number of NRFs and NRF Sets deployed in the network
  • Number of NRFs in an NFSet: 2
  • Number of NRF NFSets: 3
Response time (latency) from NRF (NRF processing time) 150 milliseconds
Delegated Discovery Traffic Information
  • Model D Cache: Disabled
  • enforceReqSpecificSvcDiscovery: Disabled
  • Delegated discovery traffic rate (% of delegated discovery request per interface wise): 20%
  • Provide the list of discovery parameters for every 3GPP interface
  • ValidityPeriod value in discovery response (cache TTL): NA
NF Discovery response size and Info
  • Largest number of NF profiles returned in discovery response: 6
  • Largest number of NF services in each NF profile in discovery response: 5
Egress and Ingress Configurations NA
Mediation Configurations NA
Mediation Trigger point configuration NA
Secured HTTPs connection - % of message on HTTPs? NA
DNS SRV configuration and response time NA
Roaming traffic details NA
Pods deployed
  • Control plane pods:
    • Notification:1
    • Subscription:1
    • Audit:1
    • Configuration:1
    • Alternate Resolution:1
  • Data plane pods:
    • Worker: 24
    • NRF Proxy: 8
    • NRF Auth : 0
    • Cache:3
    • Mediation:0
SCP Worker Pod Profile 8 vCPU & 12 Gi Memory
Oracle Communications Network Analytics Data Director Configurations NA
LCI Configurations NA
Processing latency(processing time) per producer NF Upstream Network Latency: 150 milliseconds
OAuth Traffic Rate NA
OCI Configurations NA

Result and Observation

The following table provides observation data for the performance test that can be used for benchmark testing to increase the traffic rate:

Table 4-15 Result and Observation

Parameter Values
Test Duration 4 Hours
MPS Achieved 120K MPS
Average per scp-worker pod MPS ~4.8 K MPS
Average per scp-nrf pod MPS ~2.4 MPS
Success rate ~99%
Average SCP processing time (Request and Response) Less than 25 milliseconds for both Request and Response processing

SCP Microservices and their Utilization

The following table describes SCP microservices and their utilization:

Table 4-16 SCP Microservices and their Utilization

SCP Microservices CPU Memory
Max Avg Max Avg
scp-worker 5.14 4.28 7.42 Gi 6.94 Gi
scp-nrfproxy 7.59 2.63 5.64 Gi 4.71 Gi
scpc-notification 0.114 0.0655 1.31 Gi 1.13 Gi
scpc-audit 0.0218 0.00331 567 MB 488 MB
scpc-configuration 0.0399 0.00242 699 MB 521 MB
scpc-subscription 0.113 0.0713 634 MB 506 MB
scp-cache 0.0172 0.00839 766 MB 731 MB

Observed Values of cnDBTier Services

The following table provides information about observed values of cnDBTier services:

Table 4-17 Observed Values of cnDBTier Services

cnDBTier Services Value
Memory usage of data nodes 0.7%
CPU usage of data nodes 0.17%
Write operations per second -
Read operations per second 30.6 seconds
Transaction rates on data nodes 4.24

4.4.3 Model D - Testcase Scenario 2

The Model D test is based on the network latency of 150 milliseconds with 20% delegated and non-delegated discovery requests towards NRF.

Objective

This testcase scenario describes the performance and capacity of SCP with Model D. It provides the benchmarking results with latency in a network, and no rate limit is applied to the ingress and egress traffic.

The following table describes test bed configurations:

Table 4-18 Input Parameter Details

Input Parameter Details Configuration Values
Duration of Test 12 Hours
SCP Version Tag 22.4.0
Cluster Test Bed 1 - CNE on Bare Metal. For more information, see Cluster Details
Topology Topology 2. For information about topology, see Test Topology 2 for SCP Model D Benchmarking

Testcase Parameters

The following table describes the testcase parameters and their values:

Table 4-19 Testcase Parameters

Input Parameter Details Configuration Values

Maximum SCP system wide traffic rate (in MPS)

 120K MPS
Network deployment diagram Topology 2. For information about topology, see Test Topology 2 for SCP Model D Benchmarking
Mode of Network deployment (Model-C or Model-D) Model D
Number of NFs deployed in the network which SCP is supposed to learn (number of NF Profiles)
  • Number of NF instances: 152 profiles as described in Table 3-3.
  • NF Services per NF instance:
    • UDM profile has 4 service types, such as nudm-uecm, nudm-sdm, nudm-ee, and nudm-ueau; each service type has two instances. 1 UDM profile as 8 service instances.
    • AUSF profile has 1 services type (nausf-auth), and each service type has two instances. 1 AUSF profile has 2 service instances.
    • 5G-EIR profile has 1 services type (n5g-eir-eic), each service type has two instances. 1 5G-EIR profile has 2 service instances.
    • AMF profile has 2 services types (namf-comm, namf-loc), each service type has two instances. 1 AMF profile has 4 service instances.
  • IP/FQDN per service: Each service instance has a single unique IP endpoint within a service type, which is repeated across multiple service types within an NF profile.
NF Status Information
  • Add or Modify or Delete 10 notification every 15 min
  • Profile notification updates were run every 15 minutes along with traffic run
  • Notifications could come with the following updates:
    • The priority of NF services has changed.
    • The capacity of the NF services has changed.
    • The priority and capacity of NF services have changed.
    • The load of NF has changed.
    • Service instances are removed from the profiles.
    • Service instances are removed from profiles.
NF Profile - Priority, Capacity, Load value same in all services of same kind? (Yes, No) No
LAN latency in intra-SCP services and 5G NF communication (between SCP data and control plane services, SCP and other NFs ) in millisecond 150 milliseconds
WAN latency in SCP services and 5G NF communication (SCP to NFs in other regions) in millisecond 300 milliseconds
Number of SCP ingress IPs configured 8
How many connections per published IP/FQDN producers can handle? 96
Per Egress connection max traffic in MPS 450
How many connections consumer can initiate towards per SCP IP? 480
Per Ingress connection max traffic in MPS 1000
Average Request and Response message size
  • Average HTTP Request Packet Size: 1500 Bytes
  • Average HTTP Response Packet Size: 1500 Bytes
Percentage of alternate routed requests to NF due to any reason (2% to 5%) 2%
Configured audit interval and audit mode
  • Configured Audit Interval: 3600 seconds
  • Configured Audit Mode: nnrf-mgmt
Number of NRFs and NRF Sets deployed in the network
  • Number of NRFs in an NFSet: 2
  • Number of NRF NFSets: 3
Response time (latency) from NRF (NRF processing time) 150 milliseconds
Delegated Discovery Traffic Information
  • Model D Cache: Enabled
  • enforceReqSpecificSvcDiscovery: Enabled
  • Delegated discovery traffic rate (% of delegated discovery request per interface wise): 20%
  • Provide the list of discovery parameters for every 3GPP interface
  • ValidityPeriod value in discovery response (cache TTL):
    • 600 seconds (10% of Delegated Discovery traffic)
    • 1 second (10% of Delegated Discovery traffic)
NF Discovery response size and Info
  • Largest number of NF profiles returned in discovery response: 66
  • Largest number of NF services in each NF profile in discovery response: 4
Egress and Ingress Configurations NA
Mediation Configurations NA
Mediation Trigger point configuration NA
Secured HTTPs connection - % of message on HTTPs? NA
DNS SRV configuration and response time NA
Roaming traffic details NA
Pods deployed
  • Control plane pods:
    • Notification:1
    • Subscription:1
    • Audit:1
    • Configuration:1
    • Alternate Resolution:1
  • Data plane pods:
    • Worker: 24
    • NRF Proxy: 8
    • NRF Auth : 0
    • Cache:3
    • Mediation:0
SCP Worker Pod Profile 12 vCPU & 16 GB Memory
Oracle Communications Network Analytics Data Director Configurations NA
LCI Configurations NA
Processing latency(processing time) per producer NF Upstream Network Latency: 150 milliseconds
OAuth Traffic Rate NA
OCI Configurations NA

Result and Observation

The following table provides observation data for the performance test that can be used for benchmark testing to increase the traffic rate:

Table 4-20 Result and Observation

Parameter Values
MPS Achieved 120K MPS
Average per scp-worker pod MPS 5.2K MPS
Success rate ~99.8%
Number of Discovery requests sent to NRF by SCP 4.8K MPS
Total Number of delegated discovery requests processed by Model D Cache 8.1K MPS
Average SCP processing time (Request and Response) Less than 25 milliseconds for both Request and Response processing

SCP Microservices and their Utilization

The following table describes SCP microservices and their utilization:

Table 4-21 SCP Microservices and their Utilization

SCP Microservices CPU Memory
Max Avg Max Avg
scp-worker 7.55 4.1 5.3 GB 5.2 GB
scp-nrfproxy 5.93 3.8 4.3 GB 3.7 GB
scpc-notification 0.278 0.194 1.67 GB 1.63 GB
scpc-audit 0.00826 0.00356 726 MB 724 MB
scpc-configuration 0.0302 0.0263 753 MB 731 MB
scpc-subscription 0.0338 0.0202 555 MB 528 MB
scp-cache 0.0124 0.00956 782 MB 775 MB

Observed Values of cnDBTier Services

The following table provides information about observed values of cnDBTier services:

Table 4-22 Observed Values of cnDBTier Services

cnDBTier Services Value
Memory usage of data nodes 9.51%
CPU usage of data nodes 0.229%
Write operations per second 10.3 seconds
Read operations per second 146 seconds
Transaction rates on data nodes 12.3

For example, a customer network can achieve the following capabilities:

  • The percentage (%) of Delegated Discovery traffic to Network Repository Function (NRF) is 20% of the total traffic per site.
  • Redundancy model of maximum 2 SCP sites in a region being offline.
  • Mediation: 5% traffic and 4 trigger points per site.
  • 2.8M Messages Per Second (MPS) network wide SCP traffic with currently deployed features on 15 HP 28 core servers per site. For example, 210 additional worker nodes. The network supports 24 out of 30 active SCP instances, each SCP instance with 120K MPS.

4.4.4 Model D - Testcase Scenario 3

The Model D test is based on the network latency of 150 milliseconds with 20% delegated and non-delegated discovery requests towards NRF.

Objective

This testcase scenario describes the performance and capacity of SCP with Model D. It provides the benchmarking results with latency in a network, and no rate limit is applied on the Ingress and Egress traffic.

The following table describes test bed configurations:

Table 4-23 Input Parameter Details

Input Parameter Details Configuration Values
Duration of Test 8 Hours
SCP Version Tag 22.4.0
Cluster Test Bed 1 - CNE on Bare Metal. For more information, see Cluster Details
Topology Topology 2. For information about topology, see Test Topology 2 for SCP Model D Benchmarking

Testcase Parameters

The following table describes the testcase parameters and their values:

Table 4-24 Testcase Parameters

Input Parameter Details Configuration Values

Maximum SCP system wide traffic rate (in MPS)

 120K MPS
Network deployment diagram Topology 2. For information about topology, see Test Topology 2 for SCP Model D Benchmarking
Mode of Network deployment (Model-C or Model-D) Model D
Number of NFs deployed in the network which SCP is supposed to learn (number of NF Profiles)
  • Number of NF instances: 152 profiles as described in Table 3-3.
  • NF Services per NF instance:
    • UDM profile has 4 service types such as nudm-uecm, nudm-sdm, nudm-ee, and nudm-ueau, each service type has two instances. 1 UDM profile as 8 service instances.
    • AUSF profile has 1 services type (nausf-auth), each service type has two instances. 1 AUSF profile has 2 service instances.
    • 5G-EIR profile has 1 services type (n5g-eir-eic), each service type has two instances. 1 5G-EIR profile has 2 service instances.
    • AMF profile has 2 services type (namf-comm, namf-loc), each service type has two instances. 1 AMF profile has 4 service instances.
  • IP/FQDN per service: Each service instance has a single unique IP endpoint within a service type, which is repeated across multiple service types within an NF profile.
NF Status Information
  • Add or Modify or Delete 10 notification every 15 min
  • Profile notification updates were run every 15 minutes along with traffic run
  • Notifications could come with the following updates:
    • The priority of NF services has changed.
    • The capacity of the NF services has changed.
    • The priority and capacity of NF services have changed.
    • The load of NF has changed.
    • Service instances are removed from the profiles.
    • Service instances are removed from profiles.
NF Profile - Priority, Capacity, Load value same in all services of same kind? (Yes, No) No
LAN latency in intra-SCP services and 5G NF communication (between SCP data and control plane services, SCP and other NFs ) in millisecond 150 milliseconds
WAN latency in SCP services and 5G NF communication (SCP to NFs in other regions) in millisecond 300 milliseconds
Number of SCP ingress IPs configured 1
How many connections per published IP/FQDN producers can handle? 96
Per Egress connection max traffic in MPS 450
How many connections consumer can initiate towards per SCP IP? 456
Per Ingress connection max traffic in MPS 1000
Average Request and Response message size
  • Average HTTP Request Packet Size: 1500 Bytes
  • Average HTTP Response Packet Size: 1500 Bytes
Percentage of alternate routed requests to NF due to any reason (2% to 5%) 2%
Configured audit interval and audit mode
  • Configured Audit Interval: 3600 seconds
  • Configured Audit Mode: nnrf-mgmt
Number of NRFs and NRF Sets deployed in the network
  • Number of NRFs in an NFSet: 2
  • Number of NRF NFSets: 3
Response time (latency) from NRF (NRF processing time) 150 milliseconds
Delegated Discovery Traffic Information
  • Model D Cache: Enabled
  • enforceReqSpecificSvcDiscovery: Disabled
  • Delegated discovery traffic rate (% of delegated discovery request per interface wise): 20%
  • Provide the list of discovery parameters for every 3GPP interface
  • ValidityPeriod value in discovery response (cache TTL):
    • 600 seconds (10% of Delegated Discovery traffic)
    • 1 second (10% of Delegated Discovery traffic)
NF Discovery response size and Info
  • Largest number of NF profiles returned in discovery response: 66
  • Largest number of NF services in each NF profile in discovery response: 4
Egress and Ingress Configurations NA
Mediation Configurations NA
Mediation Trigger point configuration NA
Secured HTTPs connection - % of message on HTTPs? NA
DNS SRV configuration and response time NA
Roaming traffic details NA
Pods deployed
  • Control plane pods:
    • Notification:1
    • Subscription:1
    • Audit:1
    • Configuration:1
    • Alternate Resolution:1
  • Data plane pods:
    • Worker: 24
    • NRF Proxy: 8
    • NRF Auth : 0
    • Cache:3
    • Mediation:0
SCP Worker Pod Profile 12 vCPU & 16 GB Memory
Oracle Communications Network Analytics Data Director Configurations NA
LCI Configurations NA
Processing latency(processing time) per producer NF Upstream Network Latency: 150 milliseconds
OAuth Traffic Rate NA
OCI Configurations NA

Result and Observation

The following table provides observation data for the performance test that can be used for benchmark testing to increase the traffic rate:

Table 4-25 Result and Observation

Parameter Values
MPS Achieved 120K MPS
Average per scp-worker pod MPS ~5.8 K MPS
Success rate ~99.1%
Number of Discovery requests sent to NRF by SCP 3.7K MPS
Total Number of delegated discovery requests processed by Model D Cache 8.3K MPS

Average SCP processing time (Request and Response)

Less than 25 milliseconds for both Request and Response processing

SCP Microservices and their Utilization

The following table describes SCP microservices and their utilization:

Table 4-26 SCP Microservices and their Utilization

SCP Microservices CPU Memory
Max Avg Max Avg
scp-worker 7.54 4.1 9.8 GB 9.6 GB
scp-nrfproxy 6.2 4.8 4.8 GB 3.5 GB
scpc-notification 0.260 0.234 1.50 GB 1.49 GB
scpc-audit 0.00762 0.00173 597 MB 594 MB
scpc-configuration 0.00602 0.00161 539 MB 538 MB
scpc-subscription 0.0554 0.0456 518 MB 512 MB
scp-cache 0.0131 0.00914 825 MB 824 MB
scp-load-manager 0.0346 0.0268 718 MB 715 MB

Observed Values of cnDBTier Services

The following table provides information about observed values of cnDBTier services:

Table 4-27 Observed Values of cnDBTier Services

cnDBTier Services Value
Memory usage of data nodes 9.62%
CPU usage of data nodes 0.4%
Write operations per second 10.2 seconds
Read operations per second 145 seconds
Transaction rates on data nodes 17.1

4.4.5 Model D - Testcase Scenario 4

The Model D test is based on the network latency of 150 milliseconds with 20% delegated and non-delegated discovery requests towards NRF.

Objective

This testcase scenario describes the performance and capacity of SCP with Model D. It provides the benchmarking results with latency in a network, and no rate limit is applied on the ingress and egress traffic.

The following table describes test bed configurations:

Table 4-28 Input Parameter Details

Input Parameter Details Configuration Values
Duration of Test 12 Hours
SCP Version Tag 22.4.0
Cluster Test Bed 1 - CNE on Bare Metal. For more information, see Cluster Details
Topology Topology 2. For information about topology, see Test Topology 2 for SCP Model D Benchmarking

Testcase Parameters

The following table describes the testcase parameters and their values:

Table 4-29 Testcase Parameters

Input Parameter Details Configuration Values

Maximum SCP system wide traffic rate (in MPS)

 120K MPS
Network deployment diagram Topology 2. For information about topology, see Test Topology 2 for SCP Model D Benchmarking
Mode of Network deployment (Model-C or Model-D) Model D
Number of NFs deployed in the network which SCP is supposed to learn (number of NF Profiles)
  • Number of NF instances: 152 profiles as described in Table 3-3.
  • NF Services per NF instance:
    • UDM profile has 4 service types such as nudm-uecm, nudm-sdm, nudm-ee, and nudm-ueau, each service type has two instances. 1 UDM profile as 8 service instances.
    • AUSF profile has 1 services type (nausf-auth), each service type has two instances. 1 AUSF profile has 2 service instances.
    • 5G-EIR profile has 1 services type (n5g-eir-eic), each service type has two instances. 1 5G-EIR profile has 2 service instances.
    • AMF profile has 2 services type (namf-comm, namf-loc), each service type has two instances. 1 AMF profile has 4 service instances.
  • IP/FQDN per service: Each service instance has a single unique IP endpoint within a service type, which is repeated across multiple service types within an NF profile.
NF Status Information
  • Add or Modify or Delete 10 notification every 15 min
  • Profile notification updates were run every 15 minutes along with traffic run
  • Notifications could come with the following updates:
    • The priority of NF services has changed.
    • The capacity of the NF services has changed.
    • The priority and capacity of NF services have changed.
    • The load of NF has changed.
    • Service instances are removed from the profiles.
    • Service instances are removed from profiles.
NF Profile - Priority, Capacity, Load value same in all services of same kind? (Yes, No) No
LAN latency in intra-SCP services and 5G NF communication (between SCP data and control plane services, SCP and other NFs ) in millisecond 150 milliseconds
WAN latency in SCP services and 5G NF communication (SCP to NFs in other regions) in millisecond 300 milliseconds
Number of SCP ingress IPs configured 8
How many connections per published IP/FQDN producers can handle? 96
Per Egress connection max traffic in MPS 400
How many connections consumer can initiate towards per SCP IP? 432
Per Ingress connection max traffic in MPS 1000
Average Request and Response message size
  • Average HTTP Request Packet Size: 1500 Bytes
  • Average HTTP Response Packet Size: 1500 Bytes
Percentage of alternate routed requests to NF due to any reason (2% to 5%) 2%
Configured audit interval and audit mode
  • Configured Audit Interval: 3600 seconds
  • Configured Audit Mode: nnrf-mgmt
Number of NRFs and NRF Sets deployed in the network
  • Number of NRFs in an NFSet: 2
  • Number of NRF NFSets: 3
Response time (latency) from NRF (NRF processing time) 150 milliseconds
Delegated Discovery Traffic Information
  • Model D Cache: Enabled
  • enforceReqSpecificSvcDiscovery: Disabled
  • Delegated discovery traffic rate (% of delegated discovery request per interface wise): 20%
  • Provide the list of discovery parameters for every 3GPP interface
  • ValidityPeriod value in discovery response (cache TTL):
    • 600 seconds (10% of Delegated Discovery traffic)
    • 1 second (10% of Delegated Discovery traffic)
NF Discovery response size and Info
  • Largest number of NF profiles returned in discovery response: 66
  • Largest number of NF services in each NF profile in discovery response: 4
Egress and Ingress Configurations NA
Mediation Configurations NA
Mediation Trigger point configuration NA
Secured HTTPs connection - % of message on HTTPs? NA
DNS SRV configuration and response time NA
Roaming traffic details NA
Pods deployed
  • Control plane pods:
    • Notification:1
    • Subscription:1
    • Audit:1
    • Configuration:1
    • Alternate Resolution:1
  • Data plane pods:
    • Worker: 24
    • NRF Proxy: 8
    • NRF Auth : 0
    • Cache: 3
    • Mediation: 0
SCP Worker Pod Profile 12 vCPU & 16 GB Memory
Oracle Communications Network Analytics Data Director Configurations NA
LCI Configurations NA
Processing latency(processing time) per producer NF Upstream Network Latency: 150 milliseconds
OAuth Traffic Rate NA
OCI Configurations NA

Result and Observation

The following table provides observation data for the performance test that can be used for benchmark testing to increase the traffic rate:

Table 4-30 Result and Observation

Parameter Values
MPS Achieved 120K MPS
Average per scp-worker pod MPS ~5.2 K MPS
Success rate ~99.5%
Number of Discovery requests sent to NRF by SCP 2.5K MPS
Total Number of delegated discovery requests processed by Model D Cache 9.5K MPS
Average SCP processing time (Request and Response) Less than 25 milliseconds for both Request and Response processing

SCP Microservices and their Utilization

The following table describes SCP microservices and their utilization:

Table 4-31 SCP Microservices and their Utilization

SCP Microservices CPU Memory
Max Avg Max Avg
scp-worker 6.56 3.5 9.8 GB 9.6 GB
scp-nrfproxy 4.9 3.5 4.8 GB 3.6
scpc-notification 0.267 0.222 1.44 GB 1.43 GB
scpc-audit 0.0152 0.00185 583 MB 581 MB
scpc-configuration 0.0138 0.00130 632 MB 630 MB
scpc-subscription 0.0572 0.0375 467 MB 456 MB
scp-cache 0.0146 0.00822 841 MB 840 MB
scp-load-manager 0.0374 0.0263 758 MB 747 MB

Observed Values of cnDBTier Services

The following table provides information about observed values of cnDBTier services:

Table 4-32 Observed Values of cnDBTier Services

cnDBTier Services Value
Memory usage of data nodes 7.38%
CPU usage of data nodes 0.357%
Write operations per second 11.1 seconds
Read operations per second 124 seconds
Transaction rates on data nodes 15.2

4.4.6 Model D - Testcase Scenario 5

The Model D test is based on a network latency of 150 milliseconds with 20% delegated and non-delegated discovery requests toward NRF.

Objective

This testcase scenario describes the performance and capacity of SCP on Model D. It provides results with latency in a network, and no rate limit is applied to the ingress and egress traffic.

The following table describes test bed configurations:

Table 4-33 Input Parameter Details

Input Parameter Details Configuration Values
Duration of Test 12 Hours
SCP Version Tag 22.4.1
Cluster Test Bed 1 - CNE on Bare Metal. For more information, see Cluster Details
Topology Topology 1. For information about topology, see Test Topology 1 for SCP Model D Benchmarking

Testcase Parameters

The following table describes the testcase parameters and their values:

Table 4-34 Testcase Parameters

Input Parameter Details Configuration Values

Maximum SCP system wide traffic rate (in MPS)

 186K MPS
Network deployment diagram Topology 1. For information about topology, see Test Topology 1 for SCP Model D Benchmarking
Mode of Network deployment (Model-C or Model-D) Model D
Number of NFs deployed in the network which SCP is supposed to learn (number of NF Profiles)
  • Number of NF instances: 152 profiles as described in Table 3-3.
  • NF Services per NF instance:
    • UDM profile has 4 service types such as nudm-uecm, nudm-sdm, nudm-ee, and nudm-ueau, each service type has two instances. 1 UDM profile as 8 service instances.
    • AUSF profile has 1 services type (nausf-auth), each service type has two instances. 1 AUSF profile has 2 service instances.
    • 5G-EIR profile has 1 services type (n5g-eir-eic), each service type has two instances. 1 5G-EIR profile has 2 service instances.
    • AMF profile has 2 services type (namf-comm, namf-loc), each service type has two instances. 1 AMF profile has 4 service instances.
  • IP/FQDN per service: Each service instance has a single unique IP endpoint within a service type, which is repeated across multiple service types within an NF profile.
NF Status Information
  • Add or Modify or Delete 10 notification every 15 min
  • Profile notification updates were run every 15 minutes along with traffic run
  • Notifications could come with the following updates:
    • The priority of NF services has changed.
    • The capacity of the NF services has changed.
    • The priority and capacity of NF services have changed.
    • The load of NF has changed.
    • Service instances are removed from the profiles.
    • Service instances are removed from profiles.
NF Profile - Priority, Capacity, Load value same in all services of same kind? (Yes, No) No
LAN latency in intra-SCP services and 5G NF communication (between SCP data and control plane services, SCP and other NFs ) in millisecond 150 milliseconds
WAN latency in SCP services and 5G NF communication (SCP to NFs in other regions) in millisecond 300 milliseconds
Number of SCP ingress IPs configured 8
How many connections per published IP/FQDN producers can handle? 148
Per Egress connection max traffic in MPS 500
How many consumers can initiate towards per SCP IP? 740
Per Ingress connection max traffic in MPS 1000
Average Request and Response message size
  • Average HTTP Request Packet Size: 1500 Bytes
  • Average HTTP Response Packet Size: 1500 Bytes
Percentage of alternate routed requests to NF due to any reason (2% to 5%) 2%
Configured audit interval and audit mode
  • Configured Audit Interval: 3600 seconds
  • Configured Audit Mode: nnrf-mgmt
Number of NRFs and NRF Sets deployed in the network
  • Number of NRFs in an NFSet: 2
  • Number of NRF NFSets: 3
Response time (latency) from NRF (NRF processing time) 150 milliseconds
Delegated Discovery Traffic Information
  • Model D Cache: Enabled
  • enforceReqSpecificSvcDiscovery: Enabled
  • Delegated discovery traffic rate (% of delegated discovery request per interface wise): 20%
  • Provide the list of discovery parameters for every 3GPP interface
  • ValidityPeriod value in discovery response (cache TTL):
    • 600 seconds (10% of Delegated Discovery traffic)
    • 1 second (10% of Delegated Discovery traffic)
NF Discovery response size and Info
  • Largest number of NF profiles returned in discovery response: 66
  • Largest number of NF services in each NF profile in discovery response: 4
Egress and Ingress Configurations NA
Mediation Configurations NA
Mediation Trigger point configuration NA
Secured HTTPs connection - % of message on HTTPs? NA
DNS SRV configuration and response time NA
Roaming traffic details NA
Pods deployed
  • Control plane pods:
    • Notification:1
    • Subscription:1
    • Audit:1
    • Configuration:1
    • Alternate Resolution:1
  • Data plane pods:
    • Worker: 37
    • NRF Proxy: 16
    • NRF Auth : 0
    • Cache: 3
    • Mediation: 0
SCP Worker Pod Profile 12 vCPU & 16 GB Memory
Oracle Communications Network Analytics Data Director Configurations NA
LCI Configurations NA
Processing latency(processing time) per producer NF Upstream Network Latency: 150 milliseconds
OAuth Traffic Rate NA
OCI Configurations NA

Result and Observation

The following table provides observation data for the performance test that can be used for testing to increase the traffic rate:

Table 4-35 Result and Observation

Parameter Values
MPS Achieved 186K MPS
Average per scp-worker pod MPS 5K MPS
Success rate ~100%
Number of Discovery requests sent to NRF by SCP 5.5K
Total Number of delegated discovery requests processed by Model D Cache 14 K
Average SCP processing time (Request and Response) Less than 25 milliseconds for both Request and Response processing

SCP Microservices and their Utilization

The following table describes SCP microservices and their utilization:

Table 4-36 SCP Microservices and their Utilization

SCP Microservices CPU Memory
Max Avg Max Avg
scp-worker 8.9 4.0 5.32 GB 5.22 GB
scp-nrfproxy 4.0 2.3 4.88 GB 4.76 GB
scpc-notification 0.41 0.39 2.02 GB 2.02 GB
scpc-audit 0.0056 0.0042 543 MB 543 MB
scpc-configuration 0.0395 0.0271 879 MB 877 MB
scpc-subscription 0.0309 0.0250 615 MB 610 MB
scp-cache 0.0117 0.00968 937 MB 936 MB

Observed Values of cnDBTier Services

The following table provides information about the observed values of cnDBTier services:

Table 4-37 Observed Values of cnDBTier Services

cnDBTier Services Value
Memory usage of data nodes 15.1%
CPU usage of data nodes 0.4%
Write operations per second 11.5 seconds
Read operations per second 144 seconds
Transaction rates on data nodes 16.5

4.4.7 Model D - Testcase Scenario 6

This is a Model D test based on the network latency of 150 milliseconds with no rate limit applied.

Objective

This testcase scenario describes the performance and capacity of SCP with the 186K MPS Model D deployment model and the following configurations:
  • OAuth parameters and OAuth2.0 feature enabled
  • OAuth Cache enabled
  • Model D Cache disabled
  • enforceReqSpecificSvcDiscovery parameter enabled
The following table describes test bed configurations:

Table 4-38 Input Parameter Details

Input Parameter Details Configuration Values
Duration of Test 12 Hours
SCP Version Tag 23.4.0
Cluster Test Bed 4 - CNE on Bare Metal. For more information, see Cluster Details
Topology Topology 1. For information about topology, see Test Topology 1 for SCP Model D Benchmarking

Testcase Parameters

The following table describes the testcase parameters and their values:

Table 4-39 Testcase Parameters

Input Parameter Details Configuration Values

Maximum SCP system wide traffic rate (in MPS)

 186K MPS
Network deployment diagram Topology 1. For information about topology, see Test Topology 1 for SCP Model D Benchmarking
Mode of Network deployment (Model-C or Model-D) Model C (80%) and Model D (20%)
Number of NFs deployed in the network that SCP is supposed to learn (number of NF profiles)
  • Number of NF instances: 176 profiles as described in Table 3-3.
  • NF Services per NF instance:
    • SMF profile has two service types, such as nsmf-pdusession and nsmf-event-exposure. Each service type has one instance.
    • PCF profile has five service types, such as npcf-am-policy-control, npcf-smpolicycontrol, npcf-policyauthorization, npcf-bdtpolicycontrol, npcf-ue-policy-control. Each service type has one instance.
    • UDM profile has five service types, such as nudm-ueau, nudm-uecm, nudm-sdm, nudm-ee, and nudm-pp. Each service type has one instance.
    • UDR profile has two service types, such as nudr-dr and nudr-group-id-map. Each service type has one instance.
    • CHF profile has two service types, such as nchf-spendinglimitcontrol and nchf-convergedcharging. Each service type has one instance.
    • AUSF profile has three service types, such as nausf-auth, nausf-sorprotection, and nausf-upuprotection. Each service type has one instance.
    • BSF profile has one service type, such as nbsf-management. Each service type has one instance.
  • IP/FQDN per service: Each service instance has a single unique IP endpoint within a service type, which is repeated across multiple service types within an NF profile.
NF Status Information
  • Add, modify, or delete 10 notifications every 15 minutes.
  • Profile notification updates were run every 15 minutes, along with traffic runs.
  • Notifications could come with the following updates:
    • The priority of NF services has changed.
    • The capacity of the NF services has changed.
    • The priority and capacity of NF services have changed.
    • The load of NF has changed.
    • Service instances are removed from the profiles.
    • Service instances are removed from profiles.
NF Profile - Priority, Capacity, Load value same in all services of same kind? (Yes, No) No
LAN latency in intra-SCP services and 5G NF communication (between SCP data and control plane services, SCP and other NFs) in milliseconds 150 milliseconds
WAN latency in SCP services and 5G NF communication (SCP to NFs in other regions) in milliseconds 150 milliseconds
Number of SCP ingress IPs configured 1
How many connections per published IP/FQDN producers can handle? 200
Per Egress connection max traffic in MPS 400
How many connections consumer can initiate towards per SCP IP? 800
Per Ingress connection, max traffic in MPS 1000
Percentage of alternate routed requests to NF due to any reason (2% to 5%) 2%
Configured audit interval and audit mode
  • Configured Audit Interval: 3600 seconds
  • Configured Audit Mode: nnrf-mgmt
Number of NRFs and NRF sets deployed in the network
  • Number of NRFs in an NFSet: 2
  • Number of NRF NFSets: 3
Response time (latency) from NRF (NRF processing time) 150 milliseconds
Delegated Discovery Traffic Information
  • Model D Cache: Disabled
  • enforceReqSpecificSvcDiscovery: Enabled
  • Delegated discovery traffic rate (% of delegated discovery request per interface wise): 20%
  • Provide a list of discovery parameters for every 3GPP interface.
  • ValidityPeriod value in discovery response (cache TTL): NA
NF Discovery response size and Info
  • Largest number of NF profiles returned in the discovery response: 6
  • Largest number of NF services in each NF profile in the discovery response: 5
Egress and Ingress Configurations NA
Mediation Configurations NA
Mediation Trigger point configuration NA
Secured HTTPs connection - % of message on HTTPs? NA
DNS SRV configuration and response time NA
Roaming traffic details NA
Pods deployed
  • Control plane pods:
    • Notification:1
    • Subscription:1
    • Audit:1
    • Configuration:1
    • Alternate Resolution:1
  • Data plane pods:
    • Worker: 50
    • NRF Proxy: 21
    • NRF Auth : 4
    • Cache: 3
    • Mediation: 1
SCP Worker Pod Profile 8 vCPU and 12 Gi Memory
Oracle Communications Network Analytics Data Director Configurations NA
LCI Configurations NA
Processing latency(processing time) per producer NF Upstream Network Latency: 150 milliseconds
OAuth Traffic Rate 40K MPS
OCI Configurations NA

Result and Observation

The following table provides observation data for the performance test that can be used for testing to increase the traffic rate:

Table 4-40 Result and Observation

Parameter Values
MPS Achieved 186K MPS
Average per scp-worker pod MPS 3730 MPS
Success rate ~100%
Average SCP processing time (Request and Response) Less than 25 milliseconds for both Request and Response processing

SCP Microservices and their Utilization

The following table describes SCP microservices and their utilization:

Table 4-41 SCP Microservices and their Utilization

SCP Microservices CPU Memory
Max Avg Max Avg
scp-worker 4.72 4.36 4.69 GB 4.51 GB
scp-nrfproxy 2.01 1.58 2.63 GB 2.61 GB
scpc-notification 0.640 0.621 1.87 GB 1.85 GB
scpc-audit 0.0106 0.00521 586 MB 584 MB
scpc-configuration 0.0632 0.0471 785 MB 778 MB
scpc-subscription 0.0304 0.0254 481 MB 478 MB
scp-cache 0.0199 0.0144 2.98 GB 2.92 GB
scp-nrfproxyoauth 2.26 1.97 3.08 GB 3.06 GB
scp-mediation 0.000644 0.000583 374 MB 374 MB
scp-loadmanager 0.0422 0.0309 844 MB 837 MB

Observed Values of cnDBTier Services

The following table provides information about the observed values of cnDBTier services:

Table 4-42 Observed Values of cnDBTier Services

cnDBTier Services Value
Memory usage of data nodes 0.58%
CPU usage of data nodes 0.87%
Write operations per second 2K
Read operations per second 100 seconds
Transaction rates on data nodes 2.50

4.4.8 Model D - Testcase Scenario 7

This is a Model D test based on the network latency of 150 milliseconds with no rate limit applied.

Objective

This testcase scenario describes the performance and capacity of SCP with the 186K MPS Model D deployment model and the following configurations:
  • OAuth parameters and OAuth2.0 feature enabled
  • OAuth Cache disabled
  • Model D Cache disabled
  • enforceReqSpecificSvcDiscovery parameter enabled
The following table describes test bed configurations:

Table 4-43 Input Parameter Details

Input Parameter Details Configuration Values
Duration of Test 12 Hours
SCP Version Tag 23.4.0
Cluster Test Bed 4 - CNE on Bare Metal. For more information, see Cluster Details
Topology Topology 1. For information about topology, see Test Topology 1 for SCP Model D Benchmarking

Testcase Parameters

The following table describes the testcase parameters and their values:

Table 4-44 Testcase Parameters

Input Parameter Details Configuration Values

Maximum SCP system wide traffic rate (in MPS)

 186K MPS
Network deployment diagram Topology 1. For information about topology, see Test Topology 1 for SCP Model D Benchmarking
Mode of Network deployment (Model-C or Model-D) Model C (80%) and Model D (20%)
Number of NFs deployed in the network which SCP is supposed to learn (number of NF Profiles)
  • Number of NF instances: 176 profiles as described in Table 3-3.
  • NF Services per NF instance:
    • SMF profile has two service types, such as nsmf-pdusession and nsmf-event-exposure. Each service type has one instance.
    • PCF profile has five service types, such as npcf-am-policy-control, npcf-smpolicycontrol, npcf-policyauthorization, npcf-bdtpolicycontrol, npcf-ue-policy-control. Each service type has one instance.
    • UDM profile has five service types, such as nudm-ueau, nudm-uecm, nudm-sdm, nudm-ee, and nudm-pp. Each service type has one instance.
    • UDR profile has two service types, such as nudr-dr and nudr-group-id-map. Each service type has one instance.
    • CHF profile has two service types, such as nchf-spendinglimitcontrol and nchf-convergedcharging. Each service type has one instance.
    • AUSF profile has three service types, such as nausf-auth, nausf-sorprotection, and nausf-upuprotection. Each service type has one instance.
    • BSF profile has one service type, such as nbsf-management. Each service type has one instance.
  • IP/FQDN per service: Each service instance has a single unique IP endpoint within a service type, which is repeated across multiple service types within an NF profile.
NF Status Information
  • Add, modify, or delete 10 notifications every 15 minutes.
  • Profile notification updates were run every 15 minutes, along with traffic runs.
  • Notifications could come with the following updates:
    • The priority of NF services has changed.
    • The capacity of the NF services has changed.
    • The priority and capacity of NF services have changed.
    • The load of NF has changed.
    • Service instances are removed from the profiles.
    • Service instances are removed from profiles.
NF Profile - Priority, Capacity, Load value same in all services of same kind? (Yes, No) No
LAN latency in intra-SCP services and 5G NF communication (between SCP data and control plane services, SCP and other NFs ) in millisecond 150 milliseconds
WAN latency in SCP services and 5G NF communication (SCP to NFs in other regions) in millisecond 150 milliseconds
Number of SCP ingress IPs configured 1
How many connections per published IP/FQDN producers can handle? 200
Per Egress connection max traffic in MPS 400
How many connections consumer can initiate towards per SCP IP? 800
Per Ingress connection max traffic in MPS 1000
Percentage of alternate routed requests to NF due to any reason (2% to 5%) 2%
Configured audit interval and audit mode
  • Configured Audit Interval: 3600 seconds
  • Configured Audit Mode: nnrf-mgmt
Number of NRFs and NRF Sets deployed in the network
  • Number of NRFs in an NFSet: 2
  • Number of NRF NFSets: 3
Response time (latency) from NRF (NRF processing time) 150 milliseconds
Delegated Discovery Traffic Information
  • Model D Cache: Disabled
  • enforceReqSpecificSvcDiscovery: Enabled
  • Delegated discovery traffic rate (% of delegated discovery request per interface wise): 20%
  • Provide the list of discovery parameters for every 3GPP interface
  • ValidityPeriod value in discovery response (cache TTL): NA
NF Discovery response size and Info
  • Largest number of NF profiles returned in the discovery response: 6
  • Largest number of NF services in each NF profile in the discovery response: 5
Egress and Ingress Rate Limit Configurations NA
Mediation Configurations NA
Mediation Trigger point configuration NA
Secured HTTPs connection - % of message on HTTPs? NA
DNS SRV configuration and response time NA
Roaming traffic details NA
Pods deployed
  • Control plane pods:
    • Notification:1
    • Subscription:1
    • Audit:1
    • Configuration:1
    • Alternate Resolution:1
  • Data plane pods:
    • Worker: 50
    • NRF Proxy: 21
    • NRF Auth : 4
    • Cache: 3
    • Mediation: 1
SCP Worker Pod Profile 8 vCPU and 12 Gi Memory
Oracle Communications Network Analytics Data Director Configurations NA
LCI Configurations NA
Processing latency(processing time) per producer NF Upstream Network Latency: 150 milliseconds
OAuth Traffic Rate 40K MPS
OCI Configurations NA

Result and Observation

The following table provides observation data for the performance test that can be used for testing to increase the traffic rate:

Table 4-45 Result and Observation

Parameter Values
MPS Achieved 186K MPS
Average per scp-worker pod MPS 3790 MPS
Success rate ~100%
Average SCP processing time (Request and Response) Less than 25 milliseconds for both Request and Response processing

SCP Microservices and their Utilization

The following table describes SCP microservices and their utilization:

Table 4-46 SCP Microservices and their Utilization

SCP Microservices CPU Memory
Max Avg Max Avg
scp-worker 5.38 4.85 4.02 GB 3.50 GB
scp-nrfproxy 2.06 1.81 2.56 GB 2.43 GB
scpc-notification 0.589 0.560 1.82 GB 1.74 GB
scpc-audit 0.0133 0.00536 580 MB 576 MB
scpc-configuration 0.0562 0.0429 763 MB 758 MB
scpc-subscription 0.0355 0.0256 468 MB 462 MB
scp-cache 0.0199 0.0144 1.03 GB 1.02 GB
scp-nrfproxyoauth 4.81 4.41 2.84 GB 2.25 GB
scp-mediation 0.00101 0.000585 374 MB 374 MB
scp-loadmanager 0.0408 0.0298 831 MB 825 MB

Observed Values of cnDBTier Services

The following table provides information about the observed values of cnDBTier services:

Table 4-47 Observed Values of cnDBTier Services

cnDBTier Services Value
Memory usage of data nodes 0.58%
CPU usage of data nodes 0.92%
Write operations per second 2K
Read operations per second 100 seconds
Transaction rates on data nodes 2.50