Error Processing Elements

The problem_details, session_keep_alive, and policy_notification_error_handling elements in mtx_config.xml can be configured to keep or delete a session.

problem_details Element

The problem_details element corresponds to possible ProblemDetails.title JSON fields mapped to Mtx5GSpendingLimitNotifyResponse.ResultText by SBA Gateway.

There can be multiple problem_details elements under a single session_keep_alive element:

<policy_notification_error_handling id="413">
   <session_keep_alive id="false">
      <problem_details id="1">Specific Problem Detail</problem_details>
      <problem_details id="2">Specific Problem Detail</problem_details>
      <problem_details id="3">Specific Problem Detail</problem_details>
   </session_keep_alive>
</policy_notification_error_handling>

The problem_details id attribute must be used for the XML parser to distinguish the entries. The attribute has no other significance.

The * entry matches each particular policy_notification_error_handling ID. For example:

<policy_notification_error_handling id="413">
   <session_keep_alive id="true">
      <problem_details id="0">*</problem_details>
   </session_keep_alive>
   <session_keep_alive id="false">
      <problem_details id="1">Specific Problem Detail</problem_details>
      <problem_details id="2">Specific Problem Detail</problem_details>
      <problem_details id="3">Specific Problem Detail</problem_details>
   </session_keep_alive>
</policy_notification_error_handling>

For 413, if Mtx5GSpendingLimitNotifyResponse.ResultText does not match, the session is retained.

If the error-specific wild card is absent, the global default (policy_notification_error_handling ID of 0) is consulted:

<policy_notification_error_handling id="0">
   <session_keep_alive id="false">
      <problem_details id="0">*</problem_details>
   </session_keep_alive>
</policy_notification_error_handling>

The session is shut down by default.

session_keep_alive Element

The mid-tier element, session_keep_alive, has an ID attribute that determines 5G policy session retention behavior on error:

  • true – keep session.
  • false – stop session by performing shutdown procedures.

This field is Boolean, and the XSD restricts the usage to at most two entries, for example:

<policy_notification_error_handling id="413">
   <session_keep_alive id="true">
      <problem_details id="0">*</problem_details>
   </session_keep_alive>
   <session_keep_alive id="false">
      <problem_details id="0">Specific Problem Detail</problem_details>
   </session_keep_alive>
</policy_notification_error_handling>

policy_notification_error_handling Element

The policy_notification_error_handling element has an id attribute that corresponds to Mtx5GSpendingLimitNotifyResponse. Error Code Mapping describes how the result error codes are handled:

Table 1. Error Code Mapping
Error Codes Description of Handling
0 Default when no specific mapping exists.
4xx-5xx Common HTTP error codes untranslated by SBA Gateway:
  • Translated error codes: MTX (from SBA Gateway internal error 0).
  • An error code 0 indicates failure in SBA-GW but success in Mtx5GSpendingLimitNotifyResponse).
10 ErrCode.BAD_DATA from HTTP 400.
11 ErrCode.NOT_FOUND from HTTP 404.
25 ErrCode.EXCEPTION_CAUGHT from SBA Gateway internal error 0.