Differentiated Charging via Component Traffic Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional communication network charging mechanisms lack the ability to differentiate between various components of application traffic, such as advertising and service content, leading to inefficient charging practices and inability to apply specific charging policies for dynamic traffic components.
Innovation Solution
The implementation of a method within the communication network that tracks and reports usage information for each component of application traffic separately, allowing for differentiated charging by generating charging reports that distinguish between different components of traffic associated with the same application identifier, using Session Management Function (SMF), User Plane Function (UPF), and Charging Function (CHF) to enable precise charging based on usage reports.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional charging mechanisms track usage based on application identifiers only, then charging implementation is simple, but charging differentiation capability is insufficient
Solution Approach 1:
The patent segments traffic components by introducing component identifiers that distinguish different types of traffic (e.g., service content vs. advertising) within the same application. The SMF receives usage reports containing both application identifiers and component identifiers, enabling separate tracking and charging for each component type while maintaining overall system structure.
Solution Approach 2:
The patent adds a new dimension to usage tracking by incorporating component identifiers alongside existing application identifiers. This creates a multi-dimensional charging framework where traffic is classified not only by application but also by component type, enabling differentiated charging policies without replacing the existing identification system.
2Measurement precision
If usage tracking is performed at application level only, then reporting overhead is low, but billing accuracy for different traffic components is insufficient
Solution Approach 1:
The usage reporting mechanism is segmented to include component-level metrics. The UPF generates usage reports that contain breakdowns of data volume, packet count, and other metrics by component identifier, allowing the SMF and CHF to process charges for each component type separately while maintaining efficient reporting structures.
Solution Approach 2:
Different reporting granularities are applied to different components based on charging requirements. The system enables selective detailed reporting for components requiring differentiated charging (such as advertising content) while maintaining aggregated reporting for components with uniform charging policies, optimizing the balance between accuracy and overhead.
3Ease of operation
If all traffic components are charged uniformly, then charging policy implementation is simple, but user satisfaction for differentiated services is reduced
Solution Approach 1:
The charging framework is designed to be universal, supporting both uniform and differentiated charging policies through the same infrastructure. The SMF and CHF can apply charging rules based on component identifiers when differentiation is required, while defaulting to application-level charging when uniform treatment is appropriate, making the system adaptable to various business models.
Solution Approach 2:
The charging policy system is made dynamic, allowing operators to configure different charging strategies for different component types. The CHF receives usage reports with component identifiers and can dynamically apply appropriate charging rules, enabling flexibility in implementing promotional offers, zero-rating for specific content types, or premium charging for ancillary services without changing the underlying system architecture.
Data Source
AI summary
A communication network (10) tracking usage information for each of two or more components of traffic associated with the same application identifier provides a basis for differentiating charging with respect to the two or more components. For example, traffic carried by a communication network (10) for a social media application running on a User Equipment (UE) (12) may be identified by a corresponding application identifier. However, the so-identified traffic may include multiple components, such as traffic providing the social-media service(s) and traffic constituting advertising or other ancillary or supplementary content. Tracking and reporting the network usage associated with respective components, i.e., at a granularity finer than that provided by the overall application or traffic flow identifier, provides an advantageous basis for differentiated charging as between the respective components.