Configuring SCP Model D Fallback

To configure the SCP Model D fallback, use the following sample configuration:

config 
   profile nf-client-failure nf-type scp  
      profile failure-handling failure_handling_name 
      service name type npcf-smpolicycontrol  
         responsetimeout response_timeout_value 
         message type { PcfSmpolicycontrolCreate } 
         status-code httpv2 status_code 
         retry retry_value 
         action [ retry-and-fallback | retry-and-continue | continue | terminate { nfaction terminate } | retry-and-terminate { nfaction terminate } ] 
      exit 
   exit 

NOTES:

  • profile nf-client-failure nf-type scp : Specify the NF type as SCP that is required after the NF client failure.

  • service name type npcf-smpolicycontrol : Specify the service name type as npcf-smpolicycontrol.

  • responsetimeout response_timeout_value : Specify the response timeout value in seconds.

  • message type { PcfSmpolicycontrolCreate } : Specify the message type as PcfSmpolicycontrolCreate .

  • status-code httpv2 status_code : Specify the status code of the service. The status_code must be an integer in the range of 0–599.

  • retry retry_value : Specify the number of retry attempts to the different available endpoints. The retry_value must be an integer in the range of 1–10.

  • action [ retry-and-fallback | retry-and-continue | continue | terminate { nfaction terminate } | retry-and-terminate { nfaction terminate } ] : Specify the action as retry and fallback, retry-and-continue, continue, terminate, or retry and terminate for fallback from SCP Model D to Model A. The NF failure action used if the server header indicates that the action is from the NF peer. Action is used if the failure is from the SCP.

    Note
    • After a fallback, the subsequent messages for the same resource use the peer selected as part of fallback. For example, in case a fallback to SCP Model A happens during N10 registration, the SMF sends the subsequent N10 deregistration to the UDM selected as part of fallback.

    • Currently, the action [ retry-and-fallback ] is recommended only for the SCP NF client failure handling template.