3GPP Scout / Updates / Spec change

Spec changeSA #113TS 32.290

TS 32.290 V20.0.0 adds termination as an example response to inter-CHF timeouts

Published 2026-10-16Updated 2026-10-163GPP TSG SA #113

At a glance

After a consumer charging function (CHF) request to a producer CHF times out without an alternative producer CHF, termination is now an example under operator agreement.

What changed

Technical Specification (TS) 32.290 version 20.0.0 changes failure-handling clause 5.5.1.3. Inter-CHF means communication between charging functions, here a consumer CHF contacting a producer CHF. The network function (NF) acts as the charging trigger function (CTF) whose request the consumer CHF receives. When its request to the producer CHF times out without an alternative producer CHF, the consumer CHF decides handling "based on operator agreement". The clause gives continuation and indicated termination as examples. Version 19.5.0 said the consumer CHF may continue and store charging information for settlement.

Source: 3GPP TS 32.290 V20.0.0, clause 5.5.1.3. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/32_series/32.290/32290-k00.zip

One example allows the consumer CHF to continue with the CTF and store charging information for settlement, meaning later reconciliation. Where usage quotas are managed, it can also "suspend quota management" under clause 5.3.2.5. Version 19.5.0 did not mention suspending quota management. Another example lets the consumer CHF "indicate termination of the charging session" with the CTF.

Source: 3GPP TS 32.290 V20.0.0, clause 5.5.1.3. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/32_series/32.290/32290-k00.zip

Version 20.0.0 also adds inter-CHF text to clauses 5.5.1.2 and 5.5.2. In failure-handling clause 5.5.1.2, charging information from initial, update and termination requests will be sent to the producer CHF. Clause 5.5.2 says a retried update or termination request should include an identifier for the producer CHF's charging data resource. At SA #113, five Huawei change requests in SP-260838 entered version 20.0.0 under roaming charging work item RoamRE_Ph2-CH.

Sources

  1. 3GPP TS 32.290 V20.0.0, clause 5.5.1.3. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/32_series/32.290/32290-k00.zip
  2. 3GPP TS 32.290 V19.5.0, clause 5.5.1.3. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/32_series/32.290/32290-j50.zip
  3. 3GPP TS 32.290 V20.0.0, clause 5.5.1.2. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/32_series/32.290/32290-k00.zip
  4. 3GPP TS 32.290 V20.0.0, clause 5.5.2. © 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). Official text: https://www.3gpp.org/ftp/Specs/archive/32_series/32.290/32290-k00.zip
  5. CR 0254 (S5-263716, Huawei): Rel-20 CR TS 32.290 CTF detected failure, approved in SP-260838 at SA #113. Source: 3GPP CR database.
  6. CR 0255 (S5-263717, Huawei): Rel-20 CR TS 32.290 Handling of charging sessions when a failure is detected, approved in SP-260838 at SA #113. Source: 3GPP CR database.
  7. CR 0256 (S5-263718, Huawei): Rel-20 CR TS 32.290 Handling of stored charging data requests in CTF and V-CHF, approved in SP-260838 at SA #113. Source: 3GPP CR database.
  8. CR 0257 (S5-263719, Huawei): Rel-20 CR TS 32.290 Handling of V-CHF receives abnormal message, approved in SP-260838 at SA #113. Source: 3GPP CR database.
  9. CR 0258 (S5-263720, Huawei): Rel-20 CR TS 32.290 Handling of H-CHF receives abnormal message, approved in SP-260838 at SA #113. Source: 3GPP CR database.

How this page was made

Written with AI assistance from two versions of the specification indexed by 3GPP Scout and the 3GPP CR database. An AI model (GPT-6 Sol) drafted each sentence and named the source it rests on. Code checked every quote word for word against the stored source text, and the live check fetched each TDoc again before publishing. A second AI model from another company (Claude Opus 5.5) reviewed the page against the same sources. The 3GPP documents themselves govern.