Charging Profile

The Charging Profile supports dynamically updating the configuration based on the values that you pass during the runtime. The refresh operation of the values takes place considering the following scenarios:

  • Configuration reflects in the next encounter to access: If the values are updated while an operation is in-progress, the SMF ignores the new values and continues to use the old values. For example, Limits in Charg-Profile and CC triggers.

  • Configuration reflects only on a new session: If the configuration is specific to a session and the session has already considered the values, then the SMF does not consider the new values. For example, PduContext (DB entry). This case indicates that any update to the configuration does not impact the sessions that are already created. For instance, Charging Method in Profile or Charg-Profile in Charging Characteristics.

  • Configuration reflects instantly: Configurations immediately consider the dynamic values whenever they are updated. If SMF has already used a configuration and it is later updated, then it uses the latest values.

If a session is created using a Charging Profile, which later gets deleted from the Ops Center, the session might attempt to access the configuration structure of the deleted profile. In such cases, the Smf-Service pod maintains a default profile mapped to the sessions whose profiles are missing.

The Charging Profile is responsible for handling the SMF charging parameters.

The following table lists the configuration parameters with the dynamic configuration change and its impact on the existing sessions.

Charging Profile Parameters

Configuration Parameters

Dynamic Change

Impact on Existing Sessions

limit rating-group duration

Allowed

New values are used during the new URR creation or the subsequent URR update for the existing sessions

Note

The dynamic configuration does not initiate a URR update.

max-charging-condition

Allowed

No impact

max-deferred-urr

Allowed

No impact

metering-method

Allowed

New values are used during the new URR creation for the existing sessions

method

Allowed

No impact

reporting-level

Allowed

No impact

requested-service-unit time

Allowed

No impact

tight-interworking-mode

Allowed

No impact

triggers session

Allowed

No impact

Request Quota

Allowed

No impact