SMF Error Handling

SMF handles the HTTP error codes towards PCF through the following validations:

  • SMF handles the RuleStatus enumeration in the RuleReport data structure. This data structure works on the following guidelines:

    • Validate the installed or activated Policy and Charging Control (PCC) rule for a PDU session. If the validation fails, the RuleStatus enumeration shows the configuration as "inactive".

    • Validate the updated PCC rule in a PDU session. If the validation fails, the RuleStatus enumeration shows the configuration as "active".

  • SMF handles the RuleStatus enumeration in the SessRuleReport data structure. This data structure works on the following guidelines:

    • Validate that an installed or activated Session Rule exists for PDU session. If the validation fails, then the SessionRuleStatus attribute shows the configuration as "inactive".

    • Validate that the updated Session Rule exists after activation or installation in a PDU session. If the validation fails, then the SessRuleStatus attribute shows the configuration as "active".

  • SMF handles the cause by using the FailureCause enumeration in ProblemDetails when a PCC rule fails due to validation.

    • Use PCC_RULE_EVENT for PCF to retry connection with SMF. You can view the error details in the "InvalidParams" attribute.

  • SMF handles the cause by using the FailureCause enumeration in ProblemDetails when a SessionRule fails due to validation.

    • Use RULE_PERMANENT_ERROR for PCF to retry connection with SMF. You can view the error details in the “InvalidParams” attribute.

  • SMF handles SessionRuleFailureCode in the SessionRuleReport data structure, which works on the following guideline:

    • Use only UNSUCC_QOS_VAL as the supported value for this release.

  • SMF handles SessionRuleFailureCode in the SessionRuleReport data structure, which works on the following guideline:

    • Use UNSUCC_QOS_VAL as the supported value.

  • SMF supports the ProblemDetails JSON object to show error details in the HTTP response body. With this object, the SMF service includes a "Content-Type" header field configured to "application/problem+json".