Asynchronous Usage Reporting Rule Generation in User Plane Functions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems face challenges in generating usage reporting rules (URRs) without time or volume reporting triggers, leading to limitations in usage reporting for charging services, which can result in network overload and increased CPU processing, especially when operators do not require timely reports.
Innovation Solution
The implementation of the AsynchronousReportNotRequired (ARNR) feature allows the generation of URRs without reporting triggers by selecting a user plane function capable of handling such rules, enabling usage reporting even when triggers are unavailable, thereby reducing network congestion and CPU overhead.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If usage reporting rules are generated with reporting triggers, then usage data can be reported timely, but network overload and increased CPU processing occur
Solution Approach 1:
The patent changes the parameter of reporting trigger requirements by allowing usage reporting rules to be generated without time or volume reporting triggers. This parameter change enables the system to report usage data flexibly without the overhead of continuous trigger monitoring, thereby reducing network load while maintaining reporting reliability through alternative reporting mechanisms.
2Object-generated harmful factors
If usage reporting rules are generated without reporting triggers, then network overload is reduced, but usage reporting capability is limited
Solution Approach 1:
The patent introduces an intermediary mechanism where the network device can request usage data from the wireless device even without predefined reporting triggers. This intermediary request-response mechanism allows the system to obtain usage data on demand, maintaining reporting capability while avoiding the continuous overhead of trigger-based reporting systems.
3Reliability
If multiple user plane functions are available, then service quality can be optimized, but device complexity increases
Solution Approach 1:
The patent applies local quality by allowing different user plane functions to have different capabilities regarding ARNR support. The network device selectively interacts with user plane functions based on their specific capabilities, matching the appropriate function to the service requirements. This localized capability-based selection optimizes service quality without requiring all functions to handle all scenarios, thereby managing complexity.
Data Source
AI summary
Systems and methods are provided for utilizing an asynchronous report feature when a time or volume reporting trigger is unavailable. The systems and method can include receiving node level capabilities from at least one of a plurality of user plane functions, receiving an asynchronous report from the at least one of the plurality of user plane functions, determining an absence of a reporting trigger based on charging information associated with a policy control function and trigger information associated with a charging function, selecting a user plane function from the plurality of user plane functions based on the asynchronous report, and generating a usage reporting rule without the reporting trigger to be provided to the user plane function from the plurality of user plane functions.