UPF Charging Reports Using PDR-URR Mapping for Clear Rule Identification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing charging mechanisms in communication networks face inefficiencies due to the need for 1:1 mapping between pre-defined rules and usage reporting rules (URRs) in control and user planes, leading to increased configuration complexity and ambiguity in determining online or offline charging methods.

Innovation Solution

Incorporating a Predefined Rule Name and/or PDR ID in the Usage Report to enable the control plane function to identify the associated policy and charging control rule, allowing for efficient handling of usage reports.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If 1:1 mapping between pre-defined rules and usage reporting rules is implemented, then charging mechanism reliability is improved, but configuration complexity increases

Engineering Contradiction:
Improvecharging mechanism reliabilityVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a mapping relationship between PDR IDs and URR IDs as an intermediary mechanism. Instead of direct 1:1 mapping between pre-defined rules and charging rules, the system uses PDR ID to URR ID mapping tables that enable flexible association while maintaining reliable charging tracking. This intermediary layer resolves the contradiction by providing reliable charging mechanisms through structured mapping while allowing flexible configuration without strict 1:1 constraints.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If pre-defined PDRs are configured with associated URRs in user plane function, then charging accuracy is improved, but ambiguity in determining online or offline charging methods increases

Engineering Contradiction:
Improvecharging accuracyVSAvoidcharging method determination ambiguity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments the charging determination process into distinct components: PDR configuration in user plane function, URR association, and charging method determination in control plane function. By separating these functions and using explicit mapping relationships, the system achieves accurate charging measurement while eliminating ambiguity in charging method determination. Each segment handles a specific aspect, making the overall system more manageable and less ambiguous.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If multiple pre-defined PDRs are activated for a PDU session, then service coverage is improved, but signaling overhead increases

Engineering Contradiction:
Improveservice coverageVSAvoidsignaling overhead
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent merges multiple PDR configurations into a unified mapping framework. Instead of handling each PDR-URR association independently with separate signaling, the system combines multiple mappings into structured tables that can be efficiently managed. This merging approach maintains comprehensive service coverage through multiple active PDRs while reducing signaling overhead by consolidating the representation of multiple relationships into organized data structures.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20250350909A1Method and apparatus for charging
Publication Date: 2025.11.13 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20250350909A1 patent drawing
  • US20250350909A1 patent drawing
  • US20250350909A1 patent drawing

AI summary

Embodiments of the present disclosure provide method and apparatus for charging. A method performed by a user plane function entity comprises receiving a first message from a control plane function entity. The first message comprises one or more information elements referencing one or more pre-defined packet detection rules (PDRs) configured in the user plane function entity. The one or more pre-defined PDRs specify one or more predefined usage reporting rules (URRs). The method further comprises activating the one or more predefined PDRs. The method further comprises generating a usage report for at least one of the one or more predefined URRs. The usage report comprises information for describing received user traffic which is related to the at least one of the one or more predefined URRs. The method further comprises sending a second message comprising the usage report to the control plane function entity.