Configuring the URR IDs

Following are the steps to achieve the configurable URR IDs:

  • Configuration template outside of Charging action to allow URR-Id mapping with "Rating Group" and "Service-ID".

  • If a separate RG is configured for Gy, then that RG is applied for Gy bucket. If no separate RG is configured for Gy, then the same Content-id applicable for all interfaces.

  • "Service-ID" would be optional for URR-ID mapping.

  • URR-ID should be unique (this need to be ensured through show configuration error or separate script to validate. Another option would be to check during config time itself, provided this should not lead to bigger configuration loading time). The actual URR ID value on N4 interface will have additional bits along with the config URR ID value.

  • For UPF, current logic for URR-ID generation need to be updated to take value from configuration. There are no changes for URR usage/generation logic/call-flow except UPF receiving config URR-ID from configuration rather than PFD message.

  • Same configuration values are required at SMF as well. Configuration mistake of SMF and UPF having different URR-ID for same mapping will be avoided once common configuration point to SMF and UPF is available/enabled.

To configure URR-IDs, perform the following steps:


configure 
   active-charging service service_name 
      urr-list list_name 
         rating-group group_number { service-identifier service_number | urr-id id_range } 
         end 
Note
  • urr-list list_name: Configures the active charging service URR list. list_name must be an alphanumeric string of 1 to 63 characters.

  • rating-group group_number : Specifies the rating ID used in prepaid charging. group_number must be an integer in the range of 0 to 2147483647.

  • service-identifier service_number : Specifies the number given to the service.

  • urr-id id_range : Specifies the URR identifier for rating/service group. id_range must be an integer in the range of 1-134217727.