Sbi Error Handling
In Service Based Nodal/Node, the SBI Error Handling allows you to configure re-transmission / retry, as well as reroute / redirect when a 503 message is received.
Per 3GPP TS 29.500 v 16.3.0
The SBI Error Handling tab is displayed next to NF Producer/Consumer tabs associated with the Message Editor service types.
|
Message Flow Service Name |
SBI Node Tab |
SBI Nodal Tabs |
|
Nudm |
Nudm |
Namf, AMF-UDM, SMF-UDM, AUSF-UDM, SMSF-UDM |
|
Nausf |
Nausf, AUSF-UDM |
Nudm |
|
Npcf |
Npcf, PCF-AMF |
Namf, AMF-PCF, SMF-PCF, PCF-BSF |
|
Nnssf |
Nnssf |
Namf, AMF-NSSF |
|
Nchf |
Nchf |
PCF-CHF, SMF-CHF, SMSF-CHF |
|
Nnrf |
Nnrf |
Namf, Nsmf, Nausf, Nnssf, Nudm, Npcf, Nsmsf, Nbsf, UPF |
|
Nlmf |
Nlmf |
Namf, AMF-LMF |
|
|
GMLC-AMF |
|
|
Nsmsf |
Nsmsf, SMSF-AMF Nsmsf, SMSF-UDM |
Namf, AMF-SMSF |
|
Nnef |
|
Namf |
| Nnwdaf | AMF-NWDAF | |
|
Nudr |
|
Nudm, UDM-UDR, PCF-UDR, NEF-UDR, NRF-SLF |
|
Message Name |
Message Name |
Error Handling
In Service Based Nodal/Node, the SBI Error Handling allows you to configure re-transmission / retry when a 503 message is received. Not all of the Response messages are defined in Message Flows, and not all of them can be configured with return status code 503 (with or without Negative Testing license). So this validation requirement only applies to messages in Message Flows that can be configured with status code 503 (and future codes expected to be added). As an example, if a Request message in any SBI Error Handling tab has been configured with 503 Retry, its corresponding Response message is not allowed to set 503 as the expected Status Code. This validation is performed at the OK button and in Tcl validation.
|
NOTE: Tcl variables are constructed using this method :
Examples : N15NpcfErrHandleStatusCodeEn_311, N15NpcfErrHandle503RetryMaxCount_801 |
|
The SBI Error Handling message editor feature is provisioned on a per-message basis and will only display definitions for one message at a time, based on the row selected in the table. Select a Message supporting Error Handling in the table. The table will display the appropriate Message code and Message Name per supported interface tab.
In this example, all supported messages for the AMF-PCF interface in the Service Based Nodal test case are available to select to Enable Error Handling.
|
|
Select All Deselect All |
Click on Select All and all the messages in the Messages Supporting Error Handling table will be selected for Error Handling. Click on Deselect All to deselect all the messages in the Messages Supporting Error Handling table. |
|
503 Retry |
Select to enable Error handling. Currently message type 503 is supported. Always enabled to perform a 503 message retry. Tcl Variable : ErrHandleStatusCodeEn |
|
Max Retry Count |
Enter the Maximum number of retries. Range : 1 to 10 Default : 10 Tcl Variable : ErrHandle503RetryMaxCount |
|
Retry Interval (ms) |
Enter the Retry Interval in Milliseconds. Range : 1000 to 4294967295 Default : 1000 Tcl Variable : ErrHandle503RetryTimeMs |
|
503 Retry |
Select to enable Alternate Routing. Currently message type 503 is supported. Always enabled to perform a 503 message retry. Tcl Variable : AltRouteStatusCodeEn |
|
Max Retry Count |
Enter the maximum number of alternate routing attempts during a alternate routing cycle in the range from 1 to 10. Tcl Variable : AltRoute503RetryMaxCount |
|
Retry Interval (ms) |
Enter the Retry Interval in Milliseconds. Range : 1000 to 4294967295 Default : 1000 Tcl Variable : AltRoute503RetryTimeMs |
|
Enable Fallback to Higher Priority Destination |
Select to enable fallback to a higher priority destination. If enabled, higher priority destination that had been failed will be reused after the Retry Interval. Tcl Variable : AltRoute503FallBackEn |