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 using N11, N7, N10, N36, N28, and other interfaces:

Table 4-9 Topology 2 Traffic Distribution

NF-C NF-P Interface Reference Percentage (%) of Messages
SMF PCF N7 60
SMF UDM N10 5
PCF UDR N36 1
PCF CHF N28 1
SMF CHF N40 10
NRF SLF - 3
PCF BSF Nbsf 2
AMF UDM N8 7.5
AMF AUSF N12 7.5
AMF PCF N15 3
NRF SCP Notifications

Type of Notifications (Notification call model):

  • Priority, Capacity: 70%
  • Suspend: 10%
  • Deregistration: 5%
  • API version changes: 3%
  • Update of IpEndPoint: 2%
  • SUPI range updates: 2%
  • Service Instance changes: 1%
  • Other types: 8%

Frequency of Notifications:

  • Bulk Notifications (where all NF instances update at once): Once a month
  • NF load update: once every 2 seconds
  • NF priority, capacity change: once every 10 seconds
  • NF suspend: once every 15 seconds
  • NF instance update (IP endpoint, API version, service instance): once every 20 seconds

Table 4-10 Number of NF

NF Name NF Count
AMF 150
SMF 150
PCF 50
UDM 40
AUSF 40
UDR 10
BSF 10
CHF 20
SLF 10
NRF 3 Stubs
SCP 2 SCP triplets in one region (1 real SCP and rest all Stubs)
Total 480 (excluding NRF and SCP)

Topology 2 Routing Configuration

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

Table 4-11 Routing Configuration

NF Service Deployment Response Timeout
PCF Npcf_SMPolicyControl SITE_WIDE 3s
UDR Nudr_dm SITE_WIDE 3s
CHF Nchf_SpendingLimitControl SITE_WIDE 3s
UDM Nudm_sdm SITE_WIDE 3s
UDM Nudm_uecm SITE_WIDE 3s
PCF Npcf_AMPolicyControl SITE_WIDE 3s
PCF Npcf_UEPolicyControl SITE_WIDE 3s
AUSF Nausf_UEAuthentication SITE_WIDE 3s
BSF Nbsf_management SITE_WIDE 3s
UDR Nudr_udrService SITE_WIDE 3s

Topology 2 NF Profiles

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

Table 4-12 NF Profiles

NF-C NF-P Reference Producer NF Service Discovery Parameter
SMF PCF N7 Npcf_SMPolicyControl
  • 3gpp-Sbi-Discovery-requester-nf-type: SMF
  • 3gpp-Sbi-Discovery-target-nf-type: PCF
  • 3gpp-Sbi-Discovery-preferred-snssais: <S-NSSAI>
  • 3gpp-Sbi-Discovery-dnn=<DNN>
  • 3gpp-Sbi-Discovery-preferred-locality: <Locality of SMF>
  • 3gpp-Sbi-Discovery-preferred-api-versions
SMF UDM N10

Nudm_sdm,

Nudm_uecm
  • 3gpp-Sbi-Discovery-requester-nf-type: SMF
  • 3gpp-Sbi-Discovery-target-nf-type: UDM
  • 3gpp-Sbi-Discovery-preferred-locality: <Locality of SMF>
  • 3gpp-Sbi-Discovery-preferred-api-versions
  • 3gpp-Sbi-Discovery- supi: <SUPI>
  • [3gpp-Sbi-Discovery-group-id-list =<UDM Group ID>]

Note: SMF receives UDM Group Id from AMF, SMF will not receive UDM Groupd ID from MME.

PCF UDR N36 Nudr_dm
  • 3gpp-Sbi-Discovery-requester-nf-type: PCF
  • 3gpp-Sbi-Discovery-target-nf-type: UDR
  • 3gpp-Sbi-Discovery-preferred-locality: <Locality of PCF>
  • 3gpp-Sbi-Discovery-supi:<supi>
  • 3gpp-Sbi-Discovery-data-set:<data set>
  • 3gpp-Sbi-Discovery-preferred-api-versions
PCF CHF N28 Nchf_SpendingLimitControl
  • 3gpp-Sbi-Discovery-requester-nf-type: PCF
  • 3gpp-Sbi-Discovery-target-nf-type: CHF
  • 3gpp-Sbi-Discovery-preferred-locality: <Locality of PCF>
  • 3gpp-Sbi-Discovery-preferred-api-versions
SMF CHF N40 --
  • 3gpp-Sbi-Discovery-requester-nf-type: SMF
  • 3gpp-Sbi-Discovery-target-nf-type: CHF
  • 3gpp-Sbi-Discovery-preferred-locality: <Locality of SMF>
  • 3gpp-Sbi-Discovery- supi: <SUPI>
  • 3gpp-Sbi-Discovery-preferred-api-versions

Note: NRF will perform SLF lookup for SUPI to CHF Group Id translation

PCF BSF Nbsf Nbsf_management
  • 3gpp-Sbi-Discovery-requester-nf-type: PCF
  • 3gpp-Sbi-Discovery-target-nf-type: BSF
  • 3gpp-Sbi-Discovery-preferred-locality: <Locality of PCF>
  • 3gpp-Sbi-Discovery- ue-ipv4-address or 3gpp-Sbi-Discovery- ue-ipv6-prefix (only one of these headers is applicable)
  • 3gpp-Sbi-Discovery-ip-domain (Only applicable for IPv4 address)
  • 3gpp-Sbi-Discovery-preferred-api-versions
  • 3gpp-Sbi-Discovery-dnn: <DNN>
  • 3gpp-Sbi-Discovery-snssais: <S-NSSAI>
AMF UDM N8

Nudm_sdm,

Nudm_uecm

Common discovery parameters:

  • 3gpp-Sbi-Discovery-requester-nf-type: AMF
  • 3gpp-Sbi-Discovery-target-nf-type: UDM
  • 3gpp-Sbi-Discovery-preferred-locality: <Locality of AMF>
  • 3gpp-Sbi-Discovery-preferred-api-versions
  • 3gpp-Sbi-Discovery- supi: <SUPI>
  • 3gpp-Sbi-Discovery-group-id-list =<UDM Group ID>
AMF AUSF N12 Nausf_UEAuthentication

Common discovery parameters:

  • 3gpp-Sbi-Discovery-requester-nf-type: AMF
  • 3gpp-Sbi-Discovery-target-nf-type: AUSF
  • 3gpp-Sbi-Discovery-preferred-locality: <Locality of AMF>
  • 3gpp-Sbi-Discovery-preferred-api-versions
  • 3gpp-Sbi-Discovery-routing-indicator: <Routing Indicator>
  • 3gpp-Sbi-Discovery-supi: <SUPI>
  • 3gpp-Sbi-Discovery-group-id-list =<AUSF Group ID>
AMF PCF N15

Npcf_AMPolicyControl,

Npcf_UEPolicyControl

Scenario 1

AMF will include the following discovery headers to SCP for PCF discovery at AM Policy Association establishment time:

  • 3gpp-Sbi-Discovery-requester-nf-type: AMF
  • 3gpp-Sbi-Discovery-target-nf-type: PCF
  • 3gpp-Sbi-Discovery-preferred-snssais: <S-NSSAI>
  • 3gpp-Sbi-Discovery-preferred-locality: <Locality of AMF>
  • 3gpp-Sbi-Discovery-service-names={npcf-am-policy-control, npcf-ue-policy-control}
  • 3gpp-Sbi-Discovery-preferred-api-versions

Scenario 2

AMF will include the following discovery headers to SCP for PCF discovery at UE Policy Association establishment time:

  • 3gpp-Sbi-Discovery-requester-nf-type: AMF
  • 3gpp-Sbi-Discovery-target-nf-type: PCF
  • 3gpp-Sbi-Discovery-preferred-target-nf-instance-id: <PCF instance id >
  • 3gpp-Sbi-Discovery-preferred-api-versions

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-13 Benchmark Testcase Summary

Benchmark Testcase Number Description
Model D - Testcase Scenario 1 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 2 The Model D test is based on the network latency of 50 milliseconds at the rate of 400K MPS without features enabled in the TLS enabled BareMetal CNE setup.
Model D - Testcase Scenario 3 The Model D test is based on the network latency of 50 milliseconds at the rate of 400K MPS with the features enabled in the TLS enabled BareMetal CNE setup.
Model D - Testcase Scenario 4 The Model D test is based on the network latency of 150 milliseconds at the rate of 400K MPS with the features enabled in the TLS enabled vCNE setup.

4.4.2 Model D - Testcase Scenario 1

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-14 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-15 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
  • Data plane pods:
    • Worker: 50
    • NRF Proxy: 21
    • NRF OAuth: 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
Number of entries expected in CCA certificate NA
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-16 Result and Observation

Parameter Values
Test Duration 12 Hours
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-17 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-18 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
Transaction rates on data nodes 2.50

4.4.3 Model D - Testcase Scenario 2

The Model D test is based on the network latency of 50 milliseconds at the rate of 400K MPS without features enabled in the TLS enabled BareMetal CNE setup.

Objective

This testcase scenario describes the performance and capacity of SCP with 400K MPS Model D deployment model and the following configurations:
  • Mediation Trigger point configuration
  • Model D Cache enabled
The following table describes test bed configurations:

Table 4-19 Input Parameter Details

Input Parameter Details Configuration Values
Duration of Test 72 Hours
SCP Version Tag 25.1.200
Cluster Test Bed 4 - CNE on BareMetal. 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-20 Testcase Parameters

Input Parameter Details Configuration Values

Maximum SCP system wide traffic rate (in MPS)

 400K 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 Profiles: 480
  • 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 one instance. 1 UDM profile has 4 service instances.
    • AUSF profile has 1 service types such as nausf-auth, each service type has two instances. 1 AUSF profile has 1 service instance.
    • PCF profile has 5 services type (npcf-bdtpolicycontrol, npcf-policyauthorization, npcf-ue-policy-control, npcf-am-policy-control, npcf-smpolicycontrol), each service type has one instance. 1 PCF profile has 5 service instances.
    • BSF profile has 1 services type (nbsf-management), each service type has one instance. 1 BSF profile has 1 service instance.
    • CHF profile has 2 service types (nchf-spendinglimitcontrol,nchf-convergedcharging), each service type has one instance. 1 CHF profile has 2 service instances.
    • SMF profile has 2 service types (nsmf-pdusession,nsmf-event-exposure), each service type has one instances.1 SMF profile has 2 service instances.
    • SLF profile has 1 services type (nudr-group-id-map), each service type has one instance. 1 SLF profile has 1 service instance.
    • AMF profile has 2 services type (namf-comm, namf-loc), each service type has one instances. 1 AMF profile has 2 service instances.
    • UDR profile has 1 services type (nudr-dr), each service type has one instance. 1 UDR profile has 1 service instance.
  • IP/FQDN per service: Each service instance has a 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 notifications every 15 minutes
  • 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.
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 2
How many connections per published IP/FQDN producers can handle? 485
Per Egress connection max traffic in MPS 1000
Per Ingress connection max traffic in MPS 1000
Average Request and Response message size
  • Average HTTP Request Packet Size: 4500 Bytes
  • Average HTTP Response Packet Size: 5000 Bytes
How many consumers can initiate towards per SCP IP? 640
Percentage of alternate routed requests to NF due to any reason (2% to 5%) 2%
Configured audit interval and audit mode
  • Configured Audit Interval: 300 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):
    • 4 seconds (10% of Delegated Discovery traffic)
    • 10 seconds (10% of Delegated Discovery traffic)
NF Discovery response size and Info 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 Number of Mediation Trigger Points: 367
Secured HTTPs connection - % of message on HTTPs? 100
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: 55
    • NRF Proxy: 7
    • NRF OAuth: 0
    • Cache: 3
    • Mediation: 2
    • Load-manager: 3
SCP Worker Pod Profile 12 vCPU and 24 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
Number of entries expected in CCA certificate NA
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-21 Result and Observation

Parameter Values
Test Duration 72 Hours
MPS Achieved 400K MPS
Average per scp-worker pod MPS 7K 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-22 SCP Microservices and their Utilization

SCP Microservices CPU Memory
Max Avg Max Avg
scp-worker 7.374 7.136 7.23 GB 7.22 GB
scpc-notification 1.187 1.142 1.68 GB 1.68 GB
scpc-audit 0.018 0.012 541 MB 541 MB
scpc-configuration 0.024 0.018 861 MB 857 MB
scpc-subscription 0.008 0.006 515 MB 515 MB
scp-cache 0.01 0.01 552 MB 551 MB
scp-nrfpproxy 3.998 3.911 2.80 GB 2.80 GB
scp-nrfproxyoauth 0.008 0.007 453 MB 452 MB
scp-mediation 0.029 0.031 1.57 GB 1.57 GB
scp-loadmanager 0.023 0.021 969 MB 969 MB

Observed Values of cnDBTier Services

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

Table 4-23 Observed Values of cnDBTier Services

cnDBTier Services Value
Memory usage of data nodes 3.9%
CPU usage of data nodes 0.5%
Write operations per second 13.1
Read operations per second 520
Transaction rates on data nodes 30.2

4.4.4 Model D - Testcase Scenario 3

The Model D test is based on the network latency of 50 milliseconds at the rate of 400K MPS with the features enabled in the TLS enabled BareMetal CNE setup.

Objective

This testcase scenario describes the performance and capacity of SCP with 400K MPS Model D deployment model and the following features enabled:
  • LCI
  • OCI
  • Mediation Trigger Points
  • Support for HTTPS
  • Outlier Detection
  • Circuit Breaking
  • Alternate Routing based on NFSets
  • Pod Overload Control
  • Enhanced 5G SBI Message Failure Handling
  • Egress Congestion Control Support at SCP
  • Message Priority Assignment and Override
  • Enhanced NF Status Processing (Mode 1)
The following table describes test bed configurations:

Table 4-24 Input Parameter Details

Input Parameter Details Configuration Values
Duration of Test 72 Hours
SCP Version Tag 25.1.200
Cluster Test Bed 4 - 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-25 Testcase Parameters

Input Parameter Details Configuration Values

Maximum SCP system wide traffic rate (in MPS)

 400K 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 Profiles: 480
  • 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 one instance. 1 UDM profile has 4 service instances.
    • AUSF profile has 1 service types such as nausf-auth, each service type has two instances. 1 AUSF profile has 1 service instance.
    • PCF profile has 5 services type (npcf-bdtpolicycontrol, npcf-policyauthorization, npcf-ue-policy-control, npcf-am-policy-control, npcf-smpolicycontrol), each service type has one instance. 1 PCF profile has 5 service instances.
    • BSF profile has 1 services type (nbsf-management), each service type has one instance. 1 BSF profile has 1 service instance.
    • CHF profile has 2 service types (nchf-spendinglimitcontrol,nchf-convergedcharging), each service type has one instance. 1 CHF profile has 2 service instances.
    • SMF profile has 2 service types (nsmf-pdusession,nsmf-event-exposure), each service type has one instances.1 SMF profile has 2 service instances.
    • SLF profile has 1 services type (nudr-group-id-map), each service type has one instance. 1 SLF profile has 1 service instance.
    • AMF profile has 2 services type (namf-comm, namf-loc), each service type has one instances. 1 AMF profile has 2 service instances.
    • UDR profile has 1 services type (nudr-dr), each service type has one instance. 1 UDR profile has 1 service instance.
  • IP/FQDN per service: Each service instance has a 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 notifications every 15 minutes
  • 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.
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 2
How many connections per published IP/FQDN producers can handle? 485
Per Egress connection max traffic in MPS 1000
Per Ingress connection max traffic in MPS 1000
Average Request and Response message size
  • Average HTTP Request Packet Size: 4500 Bytes
  • Average HTTP Response Packet Size: 5000 Bytes
How many consumers can initiate towards per SCP IP? 640
Percentage of alternate routed requests to NF due to any reason (2% to 5%) 2%
Configured audit interval and audit mode
  • Configured Audit Interval: 300 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):
    • 4 seconds (10% of Delegated Discovery traffic)
    • 10 seconds (10% of Delegated Discovery traffic)
NF Discovery response size and Info Largest number of NF services in each NF profile in discovery response: 4
Egress and Ingress Configurations NA
Mediation Configurations
  • Traffic rate at mediation service (% of traffic requiring mediation): 12%
  • Number of rules configured at mediation: 630
  • Number of groups: 50
  • Number of rules within a group: 12
  • Distribution among message mediation actions in mediation rules configuration
    • % (number) Header manipulation 70%
    • % (number) JSON IE manipulation 30%
Mediation Trigger point configuration Number of Mediation Trigger Points: 367
Secured HTTPs connection - % of message on HTTPs? 100
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: 55
    • NRF Proxy: 15
    • NRF OAuth: 0
    • Cache: 3
    • Mediation: 2
    • Load-manager: 3
SCP Worker Pod Profile 12 vCPU and 24 GB Memory
Oracle Communications Network Analytics Data Director Configurations NA
LCI Configurations
  • SCP LCI Conveyance: Enabled
  • Frequency of LCI header received with changed values: 5 seconds
  • Configured minimum peer LCI change: 5
  • Number of NF/NFService Instances reporting LCI: 480
Processing latency(processing time) per producer NF Upstream Network Latency: 150 milliseconds
Number of entries expected in CCA certificate NA
OAuth Traffic Rate NA
OCI Configurations
  • SCP OCI Conveyance is enabled
  • Frequency of OCI header received with changed values: 15 seconds
  • Number of NF/NFService Instances reporting OCI: 70

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-26 Result and Observation

Parameter Values
Test Duration 72 Hours
MPS Achieved 400K MPS
Average per scp-worker pod MPS 7K 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-27 SCP Microservices and their Utilization

SCP Microservices CPU Memory
Max Avg Max Avg
scp-worker 7.796 7.619 7.24 GB 7.24 GB
scpc-notification 1.268 1.193 1.68 GB 1.67 GB
scpc-audit 0.013 0.009 576 MB 576 MB
scpc-configuration 0.02 0.017 757 MB 757 MB
scpc-subscription 0.027 0.02 508 MB 508 MB
scp-cache 0.016 0.014 571 MB 570 MB
scp-nrfpproxy 2.351 2.239 4.33 GB 4.33 GB
scp-mediation 5.832 5.657 1.83 GB 1.78 GB
scp-loadmanager 0.133 0.12 523 MB 522 MB
scp-alternate-resolution 0.009 0.008 500 MB 499 MB

Observed Values of cnDBTier Services

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

Table 4-28 Observed Values of cnDBTier Services

cnDBTier Services Value
Memory usage of data nodes 4.9%
CPU usage of data nodes 0.8%
Write operations per second 14.1
Read operations per second 560
Transaction rates on data nodes 31.6

4.4.5 Model D - Testcase Scenario 4

The Model D test is based on the network latency of 150 milliseconds at the rate of 400K MPS with the features enabled in the TLS enabled vCNE setup.

Objective

This testcase scenario describes the performance and capacity of SCP with 400K MPS Model D deployment model and the following features enabled:

  • LCI
  • OCI
  • Mediation Trigger Points
  • Support for HTTPS
  • Outlier Detection
  • Circuit Breaking
  • Alternate Routing based on NFSets
  • Pod Overload Control
  • Enhanced 5G SBI Message Failure Handling
  • Egress Congestion Control Support at SCP
  • Message Priority Assignment and Override
  • Enhanced NF Status Processing (Mode 1)
The following table describes test bed configurations:

Table 4-29 Input Parameter Details

Input Parameter Details Configuration Values
Duration of Test 12 Hrs
SCP Version Tag 25.1.200
Cluster Test Bed 5 - 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-30 Testcase Parameters

Input Parameter Details Configuration Values

Maximum SCP system wide traffic rate (in MPS)

 400K 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 Profiles: 480
  • 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 one instance. 1 UDM profile has 4 service instances.
    • AUSF profile has 1 service types such as nausf-auth, each service type has two instances. 1 AUSF profile has 1 service instance.
    • PCF profile has 5 services type (npcf-bdtpolicycontrol, npcf-policyauthorization, npcf-ue-policy-control, npcf-am-policy-control, npcf-smpolicycontrol), each service type has one instance. 1 PCF profile has 5 service instances.
    • BSF profile has 1 services type (nbsf-management), each service type has one instance. 1 BSF profile has 1 service instance.
    • CHF profile has 2 service types (nchf-spendinglimitcontrol,nchf-convergedcharging), each service type has one instance. 1 CHF profile has 2 service instances.
    • SMF profile has 2 service types (nsmf-pdusession,nsmf-event-exposure), each service type has one instances.1 SMF profile has 2 service instances.
    • SLF profile has 1 services type (nudr-group-id-map), each service type has one instance. 1 SLF profile has 1 service instance.
    • AMF profile has 2 services type (namf-comm, namf-loc), each service type has one instances. 1 AMF profile has 2 service instances.
    • UDR profile has 1 services type (nudr-dr), each service type has one instance. 1 UDR profile has 1 service instance.
  • IP/FQDN per service: Each service instance has a 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 notifications every 15 minutes
  • 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.
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? 490
Per Egress connection max traffic in MPS 1000
Per Ingress connection max traffic in MPS 1000
Average Request and Response message size
  • Average HTTP Request Packet Size: 4500 Bytes
  • Average HTTP Response Packet Size: 5000 Bytes
How many consumers can initiate towards per SCP IP? 655
Percentage of alternate routed requests to NF due to any reason (2% to 5%) 2%
Configured audit interval and audit mode
  • Configured Audit Interval: 300 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):
    • 4 seconds (10% of Delegated Discovery traffic)
    • 10 seconds (10% of Delegated Discovery traffic)
NF Discovery response size and Info Largest number of NF services in each NF profile in discovery response: 6
Egress and Ingress Rate Limit Configurations NA
Mediation Configurations
  • Traffic rate at mediation service (% of traffic requiring mediation): 12%
  • Number of rules configured at mediation: 630
  • Number of groups: 50
  • Number of rules within a group: 12
  • Distribution among message mediation actions in mediation rules configuration
    • % (number) Header manipulation 70%
    • % (number) JSON IE manipulation 30%
Mediation Trigger point configuration Number of Mediation Trigger Points: 367
Secured HTTPs connection - % of message on HTTPs? 100
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: 55
    • NRF Proxy: 15
    • NRF OAuth: 0
    • Cache: 3
    • Mediation: 2
    • Load-manager: 3
SCP Worker Pod Profile 12 vCPU and 24 GB Memory
Oracle Communications Network Analytics Data Director Configurations NA
LCI Configurations
  • SCP LCI Conveyance: Enabled
  • Frequency of LCI header received with changed values: 5 seconds
  • Configured minimum peer LCI change: 5
  • Number of NF/NFService Instances reporting LCI: 480
Processing latency(processing time) per producer NF Upstream Network Latency: 150 milliseconds
Number of entries expected in CCA certificate NA
OAuth Traffic Rate NA
OCI Configurations
  • SCP OCI Conveyance is enabled
  • Frequency of OCI header received with changed values: 15 seconds
  • Number of NF/NFService Instances reporting OCI: 70

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-31 Result and Observation

Parameter Values
Test Duration 12 Hours
MPS Achieved 400K MPS
Average per scp-worker pod MPS 7K 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-32 SCP Microservices and their Utilization

SCP Microservices CPU Memory
Max Avg Max Avg
scp-worker 7.801 7.501 7.37 GB 7.31 GB
scpc-notification 0.958 0.939 1.66 GB 1.65 GB
scpc-audit 0.013 0.011 530 MB 530 MB
scpc-configuration 0.024 0.024 743 MB 743 MB
scpc-subscription 0.029 0.027 606 MB 605 MB
scp-cache 0.017 0.016 498 MB 498 MB
scp-nrfpproxy 2.391 2.275 2.25 GB 2.25 GB
scp-mediation 3.624 3.286 1.24 GB 1.24 GB
scp-loadmanager 0.184 0.172 1.33 GB 1.33 GB
scp-alternate-resolution 0.010 0.009 550 MB 460 MB

Observed Values of cnDBTier Services

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

Table 4-33 Observed Values of cnDBTier Services

cnDBTier Services Value
Memory usage of data nodes 5.2%
CPU usage of data nodes 0.7%
Write operations per second 13.1
Read operations per second 520
Transaction rates on data nodes 35.6